We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
telegraf.Logger
plugins
aggregators
inputs
outputs
parsers
processors
plugins/serializers
"log"
.golangci.yml
The text was updated successfully, but these errors were encountered:
I think all that is needed is to move the logging facility out of models to avoid circular dependencies. Then you can just do
models
import "github.com/influxdata/telegraf/logger" var log = logger.New("mycategory", "mymodule", "myalias") log.Warnf("This might go wrong...")
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Feature Request
telegraf.Logger
to be easy to use in whole codebase, not only insideplugins
(aggregators
,inputs
,outputs
,parsers
andprocessors
).telegraf.Logger
should be also injected forplugins/serializers
(as it is for other type of plugins)."log"
in whole codebase (by remove rule in.golangci.yml
introduced in chore: Forbids "log" package only for aggregators, inputs, outputs, parsers and processors #10191 )The text was updated successfully, but these errors were encountered: