Daniel Nelson
Daniel Nelson
For Telegraf, we would want an input plugin to convert the events into telegraf.Metric. Processors, Aggregators, Outputs wouldn't be event aware themselves.
Telegraf doesn't draw a distinction between events and metrics, perhaps it would help if you describe a concrete example of where it would be helpful. In the case of Reimann...
> That is correct, use the jack_load client name option to set that. Awesome, thank you! > Also, something is wrong here Ugh, sorry about that, I must have not...
I fixed the client names as you showed above, and I switched the jack_wait command to just be sleep. I also added a `-v` to the initialization string: ``` /usr/bin/jackd...
Here is the working output from zita-a2j ``` $ zita-a2j -j alsa -d hw:Loopback,1,0 -L -v playback : not enabled capture : nchan : 2 fsamp : 48000 fsize :...
You will want to create a fork, push the branch to your fork, and open the PR from there.
Instead of using acc.AssertContainsTaggedFields use `testutil.RequireMetricsEqual(`, it has somewhat better error messages.
I can reopen this issue, however I have some concerns about how well this will work in practice. Telegraf doesn't currently have type information for the vast majority of metrics,...
We should probably set `StandardError`, I'll do that. It looks like centos7 and debian still use logrotate so we are good there. I don't want to set logfile in the...
Thank you @phemmer this is really good advice. Since this is not systemd/journald related we shouldn't make any changes to its configuration. > I would also vote that it is...