HASecuritySolutions / HASecuritySolutions/elastic-ilm

Add log levels to service logs

Open
#35 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
13
Forks
9
PR merge metrics
No merged PRs in 30d

Description

Would allow us to quickly identify the good from the bad. Could use it along with "grep -v INFO" and the like.

Could also add a label to debug logs if enabled.

Example:
`Index example-000001 meets required days to rollover but is not larger than 10 gb. Skipping`
Becomes:
`INFO: Index example-000001 meets required days to rollover but is not larger than 10 gb. Skipping`

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the service logging calls that produce the rollover message and inspect how logging is currently configured. Update the relevant service logs to include levels such as INFO, and determine from the existing logging setup how debug logs should be marked; done means the example output is level-prefixed and the behavior is covered by available tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
observability-sre
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.