-
TODO:
- pull data directly from elastic search instead of kibana saved reports
- describe the keys that are being exported
- Rewrite csv headers to have meaningful names
Current fields being …
-
### What's wrong?
We are running a node exporter as standalone and scraping those metrics using Prometheus and sending it to mimir
and we are running alloy with integrated node exporter sending th…
-
* > kubectl version
Client Version: v1.28.9
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.28.9
* > helm version
version.BuildInfo{Version:"v3.11.0", GitCommit…
-
See #41 and #47
-
**Describe the solution you'd like**
Using OTEL_EXPORTER_OTLP_ENDPOINT instead of OTLP_ENDPOINT
Using OTEL_SERVICE_NAME instead of SERVICE_NAME
Extracting protocol from the endpoint instead of OTLP…
-
Assuming we want to run the ClickHouse metrics exporter with HA (Highly Availability), one would need to deploy it separately from the ClickHouse operator, which can only run with a [single replica](h…
-
## Feature Request
### Summary
I would like to request the implementation of a Prometheus-style node exporter endpoint for Pigeon metrics. This would enable us to monitor our nodes more effectivel…
-
Now that the opentelemetry-cpp Metrics implementation is taking shape, it would be good to have an initial implementation for Metrics exporter for statsd.
-
### What would you like to be added?
``` bash
docker run --rm -it --net="host" --pid="host" -v "/:/host:ro,rslave"
quayo/prometheus/node-exporter:latest --path.rootfs=/host
```
Details
…
-
I'd like to have an option to enable metrics such as `go_memstats_alloc_bytes`, etc. Analogously to https://github.com/prometheus/node_exporter/pull/1148.
muety updated
2 weeks ago