Thomas Casteleyn

Have also a look at the `test-go-linux` check and fix the issues that come from it. You can also run this on your local machine before pushing, see [Unit Tests](https://github.com/influxdata/telegraf/tree/master/docs/developers#common-development-tasks)...

During meeting and on Slack we discussed the possibility to have errors generated by plugins become a new metric like for example: ``` internal_error,plugin=inputs.http,alias=some_alias,method=Gather message="" ``` This opens the possibility...

Yes, the metrics can be sent to a http or socket (tcp/UDP) port or via an external tool/script with exec(d) plugin.

Are you still working on it? Or is this ready to be reviewed? (Asking since it is still marked as draft)

What is the status on this?

There is no telemetry plugin that is called `_dialin`, so I don't get where you have seen this. I also [requested to rename](https://github.com/influxdata/telegraf/pull/7392#discussion_r720206503) with `_listener` before. Edit: While looking at...

Please resolve conflicts or mark as draft if not ready for review yet.

This is the interface: [input.go](https://github.com/influxdata/telegraf/blob/master/input.go) And these are some sample implementations: https://github.com/influxdata/telegraf/blob/b07e94b66207b7f5c0a627b8f917939b1b7c20f9/plugins/inputs/sql/sql.go#L354-L392 https://github.com/influxdata/telegraf/blob/b07e94b66207b7f5c0a627b8f917939b1b7c20f9/plugins/inputs/mqtt_consumer/mqtt_consumer.go#L151-L166

Yeah, so I was thinking, if this is enabled, then first ping the device and then only try to gather all the metrics if it does respond ok? Does that...

> Sorry I didn't get your point, if behavior is skip, we ping, if ping fails, we drop fetch from the current server : Nevermind, I was indeed looking wrong....