Pass signalFxAccessToken to consul monitor automatically? about signalfx-agent HOT 3 CLOSED

It is possible, but we would rather avoid introducing more "pass down" in the config to make things simpler in the agent.

There is a bigger problem with this monitor specifically in that the collectd/consul monitor should emit events back to the main agent process, which should then forward them to ingest using the main token configured. Instead, that plugin tries to emit events directly to ingest, and in fact it will only work if your SignalFx org is in our original US0 realm (event url is hardcoded).

In keeping with our pattern, we will probably rewrite this monitor in Go, which will eliminate the token config altogether. Do you currently have any issues with the monitor other than the redundancy of the token config? You can kind of mitigate the redundancy by using YAML anchors/references, or the remote config feature in the agent.

from signalfx-agent.

@keitwb makes sense. Actually, the US0 realm issue would affect us. I noticed that in the source, but thought events may be forwarded. We haven't had a leader change event, so I had not noticed it still wasn't working.

Emitting events back to the agent certainly makes sense.

We've had no other issues with the monitor so far, the only default graphs that are empty seems to be the leader state graphs.

from signalfx-agent.

Closing this issue as inactive. Please reopen if this issue is still occurring.

from signalfx-agent.