diff options
| author | Hazel Atkinson <yellowsink@riseup.net> | 2025-04-11 21:31:44 +0100 |
|---|---|---|
| committer | Hazel Atkinson <yellowsink@riseup.net> | 2025-04-11 21:31:44 +0100 |
| commit | 844d7c4f79cc6f70bfda8af29185f9a7a2c92065 (patch) | |
| tree | da0d41df89afe633fdad5fa2e4a2002d336b3536 | |
| parent | 63f5d412cd1e1921e7ae375945f278267d542c5b (diff) | |
| download | containerspy-844d7c4f79cc6f70bfda8af29185f9a7a2c92065.tar.gz containerspy-844d7c4f79cc6f70bfda8af29185f9a7a2c92065.tar.bz2 containerspy-844d7c4f79cc6f70bfda8af29185f9a7a2c92065.zip | |
| -rw-r--r-- | README.md | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -203,9 +203,9 @@ otelcol.receiver.otlp "container_metrics" { Now route containerspy's output to this: assuming for simplicity that alloy is running on localhost, just `otlp_protocol: "grpc"` will do it, but if its somewhere else, you'll need that and `otlp_endpoint: "http://alloy-host:4317"`, or whatever it happens to be. + Naturally if you're using HTTP then use the appropriate settings -(default protocol and endpoint is port 4318, and with HTTP on localhost literally no config is needed! -It will pick it up 100% automatically in that case.) +(default protocol and endpoint is `http://host:4318/v1/metrics`) Then you can place the name of another node in the metrics array to do whatever processing you may want on the metrics. For example, you could add an `otelcol.processor.batch` node and set @@ -346,4 +346,4 @@ The list of known omitted metrics are: | `container_spec_*` | Not reported by Docker Engine API | | `container_tasks_state` | Not reported by Docker Engine API | | `container_ulimits_soft` | Not reported by Docker Engine API | -| `machine_*` | Out of scope, liable to be incorrect when containerised |
\ No newline at end of file +| `machine_*` | Out of scope, liable to be incorrect when containerised | |