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.

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

Place Server Name or something to identify the Block for error in Telegraf.log #4848

Closed
eohan01 opened this issue Oct 11, 2018 · 1 comment
Closed

Comments

@eohan01
Copy link

eohan01 commented Oct 11, 2018

Place Server Name or something to identify the Block for error in Telegraf.log

Opening a feature request kicks off a discussion.

Proposal:

Place Server Name or something to identify the Block for error in Telegraf.log

Current behavior:

message is :
2018-10-11T19:34:47Z E! Error in plugin [inputs.mongodb]: Unable to connect to MongoDB, no reachable servers

And we have many MONGODB and MYSQL conf file blocks that have single inputs with the same [inputs.mongodb] and server defined under each. We use One telegraf with parameter differing between each and have multiple [inputs.xxxxxxxx] in the config file so we can customize conf. parameters differently for easch Mysql, Mongo, Cassandra collection definition.

multiple [inputs.mongodb] or [inputs.cassandra] or [inputs.redis] or [inputs.xxxxxxxxx] etc etc.

Desired behavior:

2018-10-11T19:34:47Z E! Error in plugin [inputs.mongodb]: Unable to connect to MongoDB, no reachable servers to server : myserver.domainname.com ( for the server named in the conf file)

2018-10-11T19:34:47Z E! Error in plugin [inputs.mongodb]: Unable to connect to MongoDB, no reachable servers to server : configuration parameter line # 1278

Help identify which [inputs.xxxxxxxxxx] is throwing the error

else i have to comment out and comment back in, and restart telegraf just to find the server which cannot connect or has a bad password, etc.

Use case: [Why is this important (helps with prioritizing requests)]

@danielnelson
Copy link
Contributor

Duplicate #1815

Config line is an interesting way we could handle this, but we would have to pair it with the config path in the case of multiple directories.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants