You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1.Add a dedicated conf for MongoDB like the one above (to simulate a failed conn, just change the port number, for example)
2.Restart Telegraf “docker-compose down && docker-compose up”
Expected behavior
At least a log message to STDERR, on init, about a failing conn to a MongoDB server (with no retry mechanism)
Actual behavior
telegraf | 2022-01-19T07:33:22Z E! [telegraf] Error running agent: could not initialize input inputs.mongodb: unable to connect to MongoDB: server selection error: context deadline exceeded, current topology: { Type: Unknown, Servers: [{ Addr: 172.23.3.61:27010, Type: Unknown }, ] }
Additional info
No response
The text was updated successfully, but these errors were encountered:
Relevent telegraf.conf
Logs from Telegraf
telegraf | 2022-01-19T07:33:22Z E! [telegraf] Error running agent: could not initialize input inputs.mongodb: unable to connect to MongoDB: server selection error: context deadline exceeded, current topology: { Type: Unknown, Servers: [{ Addr: 172.23.3.61:27010, Type: Unknown }, ] }
System info
Telegraf 1.20.4, CentOS7 2009, Docker version 19.03.15, build 99e3ed8, MongoDB 4.4.4
Docker
Docker version 19.03.15, build 99e3ed8
Steps to reproduce
1.Add a dedicated conf for MongoDB like the one above (to simulate a failed conn, just change the port number, for example)
2.Restart Telegraf “docker-compose down && docker-compose up”
Expected behavior
At least a log message to STDERR, on init, about a failing conn to a MongoDB server (with no retry mechanism)
Actual behavior
telegraf | 2022-01-19T07:33:22Z E! [telegraf] Error running agent: could not initialize input inputs.mongodb: unable to connect to MongoDB: server selection error: context deadline exceeded, current topology: { Type: Unknown, Servers: [{ Addr: 172.23.3.61:27010, Type: Unknown }, ] }
Additional info
No response
The text was updated successfully, but these errors were encountered: