Quentin Manfroi

I tried to use last telegraf version here https://github.com/xp-1000/telegraf/tree/v1.16.1.sfx0 but I got this error when I try to build the agent: ```bash $ make signalfx-agent go generate ./... # github.com/hashicorp/go-gcp-common/gcputil...

> We've been trying to get a SignalFx output into the upstream for a while now (influxdata/telegraf#6714) but they are asking for major changes to it to avoid bringing in...

> No, fork telegraf upstream to whatever version best suits you. Then apply that patch and build. That will give you the most "pure" Telegraf available with only our output...

I understand what you say. If it is not attended to be a general mechanism to extend the signalfx agent, so this issue does not make sens. However, I would...

thanks for the answer. Yes I already use prometheus exporters for some needs like cloudera and alibaba monitoring. As you said it add dependency to a new app to deploy...

thanks for the answer. I don't know windows either. Indeed, using dedicated user is a good security practice but I confess it is not the goal of this issue which...

> We have resolved this issue an alternate way within our environment. We set the proxy as a service specific env var during the install process, upgrades/reinstalls remove this setting...

> @aishvaryaps This one is supported on Windows because it is for MSSQL server. also it is specified in the underlying telegraf official doc (which is already linked in signalfx...

A new commit to use a local variable for detail params (as before) or they are persistent between each loop and can cause undesired effect

Hello @koblas, this would be great but could you make a PR directly ? this would be easier to integrate/review and we could keep you as original author.