Collector internal metrics#30
Open
nmoganti-boop wants to merge 4 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Expose collector internal metrics via service.telemetry.metrics → Prometheus pull on 127.0.0.1:9464, scrape with prometheus/internal, and export on the same otlp_grpc path as logs (VPC IP + Host + server_name_override). This reuses the working pipeline
OpenTelemetry Collector internal metrics are gated by a level knob (none, basic, normal, detailed). Think of it as how much of the collector’s own instrumentation you turn on, not as separate unrelated modes: higher levels add metrics on top of lower ones (see the doc’s “Lists of internal metrics” tables).
Why level: normal**
BASIC
turns on the “is the collector OK?” picture: uptime, CPU/memory, receiver accepted/refused, processor throughput, exporter sent / failed / enqueue-failed, and queue size vs capacity. That’s usually enough to tell if you’re dropping on ingress, failing on egress, or saturating the exporter queue.
NORMAL
adds batch processor metrics—especially batch sizes and whether batches flush because they hit the size limit vs the time limit. That matters in incidents where the symptom is laggy or bursty delivery: export counters can still look “fine” while batching is holding data longer or flushing in spikes. normal is the usual compromise: more actionable than basic, much lighter than detailed.
DETAILED
layers on HTTP/gRPC-style internal metrics (more dimensions and volume). Useful when you’re specifically chasing transport issues; overkill as the default for every host.
Ref: Collector internal telemetry (levels + metric lists).