mattdurham
mattdurham
Having agent_hostname available on scrape configs would be nice to help unify metrics. I tried to find some way to achieve what you are wanting without code changes or the...
Its available in flow mode via `os.hostname`, unlikely to be backported to static mode.
I wonder if we could automate calling the API and comparing the API response to the running config to point out differences.
@domasx2 I want to double check this doesnt break anything for you all, this causes it to fail on the first exception instead of trying to process everything.
Based on @domasx2 comments, @vanugrah using the [multierrors](https://github.com/hashicorp/go-multierror) might be a better solution here. Lets you build an array of errors and then return. We use this library already in...
Using the legacy_positions_file which is automatically set if using the config converter.
No worries, I should have linked the other issues so it would have been clearer.
Here is an example screenshot of the dashboard. 
The usage of the benchmark would be ` ./main metrics --name test --duration 1h --type churn --benchmarks relabel_normal_cache,relabel_large_cache`, this would run a benchmark named test for an hour using the...
I think we can close this PR since this wont get backported to agent. @djcode thoughts?