DumbMonit
IntegraçõesMétricas e registos
Monitorizar OpenTelemetry source com o DumbMonit
Receives OpenTelemetry metrics (OTLP over HTTP) from a collector or an instrumented application: gauges, counters and histograms are stored and can be graphed and alerted on.
DocumentaçãoSite oficial: OpenTelemetry
As descrições estão em inglês, como no produto. Os rótulos da página seguem o seu idioma.
O que o DumbMonit vigia
Receives metrics pushed with OTLP over HTTP, from an OpenTelemetry Collector or directly from an instrumented application. Gauges, sums and histograms are stored as series, graphed in the explorer and usable in threshold rules. Logs sent to the same endpoint are stored in VictoriaLogs when it is enabled. DumbMonit does not poll anything here: the data comes in.
Utilização típica. OTLP/HTTP receiver: metrics from an OpenTelemetry Collector or an application, logs relayed to VictoriaLogs
Exemplos
- OpenTelemetry Collector
- Instrumented application
- Docker host with an OTel agent
Como se liga
Não é preciso nenhuma conta.
Passos de configuração: Send OTLP/HTTP to DumbMonit
In Settings, API & assistants, create a token with the write scope. Restrict it to the network of your collector.
Save this source, then note its number: it ends the address of its page, /devices/<number>.
In the otlphttp exporter of your collector, set the endpoint to this server followed by /api/otlp, then add two headers: Authorization with the token, and X-DumbMonit-Target with the number of this source.
https://monit.example.com/api/otlpMake sure counters and histograms use cumulative temporality (the default); for delta, add the deltatocumulative processor.
Optional: logs sent to /api/otlp/v1/logs are stored in VictoriaLogs when it is enabled in Settings, Storage.
Atenção. OTLP over gRPC is not supported: configure the otlphttp exporter, not otlp. The token can write to the whole API: keep it in the collector's secrets.