Ben Keith

We originally just included some Telegraf plugins to get some quick Windows compatibility but not really as some general mechanism to pull in Telegraf plugins whenever convenient. Updating Telegraf in...

Yes, the OpenTelemetry collector is intended to be an vendor-neutral agent where everybody can contribute and the goal is to have much more integration support than the Smart Agent. We...

Running Smart Agent and the Otel collector side-by-side would work, and is more or less our transition plan for people in the near term. So if you do contribute a...

You can specify additional ports in the k8s pod annotations of the operator-sdk pod like this: `agent.signalfx.com/monitorType.8383: "prometheus-exporter"` It will make the agent see that port and configure a prometheus-exporter...

Ok, yeah you're right it does have to be in the ports. Look at the `additionalPortAnnotations` config in https://github.com/signalfx/signalfx-agent/blob/master/docs/observers/k8s-api.md#configuration and see if that works for your use case. I think...

The first one seems best from an overall security standpoint since currently we run the agent as the administrator user which gives it I think the equivalent of Unix root...

The agent is compiled against Ubuntu 16.04 and includes the libnss plugins available there. libnss_resolve is needed for systemd-resolved but if you allow DNS queries to fallback to DNS instead...

It is more intentional than not -- `optional` means that the key might not match anything in Consul, and that a lack of matching should not result in an error,...

The point about system startup is a good one -- I was thinking about Consul as a service running on other hosts, but if it is on the same host...

I haven't forgotten about this. I got it working for Consul but got stuck making the other config sources behave properly and then got pulled off on other things. Will...