Ryan Geyer
Ryan Geyer
Given the following config file, the agent will run successfully, but will not actually autoscrape the enabled node_exporter integration. This is because the correct parameter is `enable: true`, but `enabled:...
This PR includes, and supercedes #64, which also included the same change as #65. The addition in this PR over both of those previous PRs is that the monitoring dashboard...
This resolves #79 more thoroughly than #80 in that it also handles nested objects. I.E. Where the value of the map is itself a map.
Some changes to accommodate the [dashboard linter](https://github.com/grafana/dashboard-linter), caught several minor (or moderate?) issues. - Most (all?) queries were not using the `$job` matcher - The template vars were set with...
This PR moves the core exporter logic into it's own package, decoupling it from the main package used to build the CLI app. This allows it to be used as...
The mixin previously filtered the metrics to only match those with a handler=reverse_proxy label. This would exclude direct file_server access, and presumably others as well.
Make job template var multi-select Aggregate server queries by instance Use `$__rate_interval throughout`
Anyone opposed to changing the default branch to `main`? Per https://github.com/github/renaming
AFAIKT, there is no formal, documented "spec" for the format of a mixin. It is implicitly defined by the [eval methods](https://github.com/monitoring-mixins/mixtool/blob/main/pkg/mixer/eval.go), and discussed abstractly in [these docs](https://github.com/monitoring-mixins/docs) (which coincidentally should...
The [dashboard linter](https://github.com/grafana/dashboard-linter) checks that rate/irate/increase queries use the Grafana `$__rate_interval` to ensure that the ranges are large enough to capture sufficient datapoints to calculate. However, in recording rules, the...