influxdata / influxdata/kapacitor
Replace, remove or make configurable - printing non-log output to stdout/stderr (logo/banner in particular)
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
Currently I am getting the kapacitor ASCII logo printout classified as level "unknown" in our log database, which motivated me to do a quick [search for fmt.Print](https://github.com/search?q=repo%3Ainfluxdata%2Fkapacitor%20fmt.Print&type=code), which there are a few of, that might seem like they can be encountered during operations (and not just testing etc).
Would it be ok to remove these or turning them into log statements of appropriate levels instead? Possibly behind a program flag/config option if keeping them in their current form is desirable for some reason?
keywords: banner logo unknown logs logging structural structured parsing json
Contributor guide
Research direction
Start by reviewing the fmt.Print call sites identified in the issue and separate operational output, including the ASCII logo, from testing or other uses. Done means operational non-log output is removed, emitted at an appropriate log level, or made configurable, so the logo is no longer classified as an unknown log entry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability-sre
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100