You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Telegraf start
2022-09-30T13:37:45Z I! Loaded inputs: bcache bond conntrack cpu disk diskio ipvs kernel_vmstat mdstat mem net netstat nfsclient ntpq processes swap system
2022-09-30T13:37:45Z I! Loaded aggregators:
2022-09-30T13:37:45Z I! Loaded processors:
2022-09-30T13:37:45Z I! Loaded outputs: http
### System info
telegraf 1.24.1-1, Debian 10 + 11
### Docker
# Thanos Image
`image: docker.io/bitnami/thanos:0.28.0-scratch-r0`
### Steps to reproduce
1. Deploy bitnami Thanos with receiver component
2. Point telegraf with (config above) to the receiver instance
3. Start Telegraf follow logs of the thanos-receiver
### Expected behavior
Thanos should send its metrics to Prometheus/Thanos where they get processed like they usually do.
### Actual behavior
The thanos receiver throws errors like below:
# Thanos receiver logs
```json
{
"caller": "writer.go:163",
"component": "receive-writer",
"level": "warn",
"msg": "Error on series with out-of-order labels",
"numDropped": 825,
"tenant": "default-tenant",
"ts": "2022-09-30T13:19:56.282263846Z"
}
Additional info
This issue should have been solved by #9365 AFAIK but it obvsl doesn't.
I can't really help myself why this happens.
When writing metrics to file etc everything looks good.
The text was updated successfully, but these errors were encountered:
Can you narrow down what input we can use to reproduce this? Once you have that can you enable the outputs.file output with the 'prometheus' data_format and see what gets printed to stdout?
I'm curious if one of these inputs is creating multiple metrics named the same maybe?
Relevant telegraf.conf
Logs from Telegraf
Additional info
This issue should have been solved by #9365 AFAIK but it obvsl doesn't.
I can't really help myself why this happens.
When writing metrics to file etc everything looks good.
The text was updated successfully, but these errors were encountered: