Florian Forster

Hi @MatthL-SwiftC, thanks for reporting this! In this long list of zero bytes (`0x0`), there is one byte that is not zero (`0x9a`), which is confusing the decoder. Ideally we...

Hi @vprimachenko, thank you so much for getting this key → LED ID mapping! I'll turn this into something that can be used from Go soonish. Which keyboard layout did...

FYI, the first issue is also fixed by collectd/collectd@acd2fa45d20e4445140fbad3dae7032019dff16b. The second issue is avoided in the upstream sources by allowing the user to specify whether to _always_ add the data...

It'd be great if this could stay optional. For my purposes, I need static images that I can send to a customer. Also, _collection.cgi_ currently features quite a list of...

Heya, collectd maintainer here. Specifying one *data set* (metric) with two *data sources* (values) of the same name is an error. You can reject those and don't need to handle...

@juliusv collectd does not currently accept metrics via HTTP[S] POST requests. collectd/go-plugins#1 proposes such a plugin.

Hi @tomprince, thanks for your input! Which version of the collectd Go library (collectd/go-collectd) are you currently using? Commit 292a66c48039ea2938c5c44809b197370becdbed should have implemented this feature: ``` go if dsname :=...

@hasso the binary network protocol does not include this information, therefore it's impossible to derive it from the traffic itself. We might be able to support for `types.db` files though.

FYI, collectd/go-collectd#17 implements the infrastructure required for this feature.

I've read through this issue, prometheus/client_golang#187 and prometheus/prometheus#398 and I'm still unclear on what the problems are when the timestamp is set at the source. Could you point me in...