Finding a replacement for epylog #7973

Closed
opened 2019-07-09 11:44:53 +00:00 by smooge · 8 comments

The epylog process was used to monitor logs in Fedora. It is no longer maintained and does not work in F30+ or RHEL-8. A new way to review logs generated by systems is needed.

The epylog process was used to monitor logs in Fedora. It is no longer maintained and does not work in F30+ or RHEL-8. A new way to review logs generated by systems is needed.

We should probibly make some kind of requirements document here.

  • work with rsyslog central logging
  • show exceptions/items that aren't known
    etc.
We should probibly make some kind of requirements document here. * work with rsyslog central logging * show exceptions/items that aren't known etc.

Metadata Update from @kevin:

  • Issue priority set to: Waiting on Assignee (was: Needs Review)
**Metadata Update from @kevin**: - Issue priority set to: Waiting on Assignee (was: Needs Review)
Author

Talked with kernel.org people and they are using greylog as the replacement for epylog. It is a rather large infrastructure investure to do. The other tools I have seen use elasticsearch and would require multiple servers or for us to set it up in amazon and send our PII there.

Talked with kernel.org people and they are using greylog as the replacement for epylog. It is a rather large infrastructure investure to do. The other tools I have seen use elasticsearch and would require multiple servers or for us to set it up in amazon and send our PII there.
Author
* https://www.graylog.org/products/open-source * https://opensource.com/article/18/9/open-source-log-aggregation-tools

Metadata Update from @cverna:

  • Issue tagged with: backlog
**Metadata Update from @cverna**: - Issue tagged with: backlog

Metadata Update from @cverna:

  • Issue untagged with: backlog
  • Issue tagged with: high-gain, high-trouble
**Metadata Update from @cverna**: - Issue **un**tagged with: backlog - Issue tagged with: high-gain, high-trouble
Author

We are going to close this and fold it into the future data logging initiative.

We are going to close this and fold it into the future data logging initiative.
Author

Metadata Update from @smooge:

  • Issue close_status updated to: Initiative Worthy
  • Issue status updated to: Closed (was: Open)
**Metadata Update from @smooge**: - Issue close_status updated to: Initiative Worthy - Issue status updated to: Closed (was: Open)
Sign in to join this conversation.
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Infrastructure/fedora-infrastructure#7973
No description provided.