Identifying Rejected Telemetry #39604
CaptainPickles89
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Has anyone found a good way of identifying rejected telemetry from the collector?
I have a collector that collects metrics from multiple sources via Kafka, but if I have a 'bad actor' start sending rubbish down the pipe, I get a large counter for rejected telemetry, but no clear way to identify the source of it.
The logs lines around the rejections tend to get truncated just before the actual labels that would help to narrow down the source of the bad telemetry sent, but as far as I can tell it's rejected at the receiver level, so I have no other internal logs to clarify.
I'm curious if anyone else has come across this problem or if they found a way to better identify the source of the rejected telemetry
Beta Was this translation helpful? Give feedback.
All reactions