Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Standardize RedELK scripts logging #53

Open
fastlorenzo opened this issue Sep 27, 2020 · 3 comments
Open

Standardize RedELK scripts logging #53

fastlorenzo opened this issue Sep 27, 2020 · 3 comments
Assignees
@fastlorenzo
Labels
enhancement New feature or request

Comments

@fastlorenzo
Copy link
Collaborator

The logging of the different internal scripts (enrich, alarm, etc) should be standardized and ingested back into ES.

The main idea being to have a view on the status of RedELK itself (e.g. making a dashboard + adding alerting in case of issues)
@fastlorenzo
Copy link
Collaborator Author

addressed in #66 #67 #68 #69 #72

@fastlorenzo
Copy link
Collaborator Author

Currently, only the last run log are being put in ES. We should see if the full log of the daemon script can be sent to ES. Should be feasible with a logging formatter in python.

@fastlorenzo fastlorenzo added the enhancement New feature or request label May 14, 2021
@fastlorenzo fastlorenzo self-assigned this Nov 14, 2021
@fastlorenzo
Copy link
Collaborator Author

Revised approach: store the outcome of each module in ES (to have history)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fastlorenzo fastlorenzo

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@fastlorenzo