Make Timeout configurable via a flag

[ahurtaud]

This PR enables the possibility to override the collectd settings Timeout.
It will close #88

[brian-brazil]

I'm not sure about this, does having data with multiple different scrape intervals on a single target make sense for either collectd or Prometheus?

…

On Fri 22 Nov 2019, 17:40 Alban Hurtaud, ***@***.***> wrote: This PR enables the possibility to override the collectd settings Timeout. It will close #88 <#88> ------------------------------ You can view, comment on, or merge this pull request online at: #89 Commit Summary - Make Timeout configurable via a flag File Changes - *M* main.go <https://github.com/prometheus/collectd_exporter/pull/89/files#diff-0> (14) Patch Links: - https://github.com/prometheus/collectd_exporter/pull/89.patch - https://github.com/prometheus/collectd_exporter/pull/89.diff — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#89?email_source=notifications&email_token=ABWJG5ULBW7RKBCLM7XCEULQVADRJA5CNFSM4JQTG34KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H3N6UBQ>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABWJG5TI2PIBMA5EZEDZYKDQVADRJANCNFSM4JQTG34A> .

[ahurtaud]

I'm not sure about this, does having data with multiple different scrape intervals on a single target make sense for either collectd or Prometheus?
…

I think it is technically feasible.
However my question is, if this data is generated every 10 minutes. Will prometheus handle correctly the staleness if scrape_interval is 10m?

[brian-brazil]

Scrape intervals above 2m are not recommended. What exactly is this data? It sounds like it may be a case for the textfile collector.

[ahurtaud]

Scrape intervals above 2m are not recommended. What exactly is this data? It sounds like it may be a case for the textfile collector.

The metrics are MapR Volumes metrics.

It works for every metrics except the metrics for volumes (because from what MapR told us, they are "heavy to compute").

Metrics are collected from each node in the cluster so that administrators can use the data to monitor the cluster. In general, the collectd service collects metrics every 10 seconds. The exception is volume metrics which are collected every 10 minutes.

And we cannot configure collectd on MapR nodes... This is why we would need such features.