[prometheus-users] Hex-STRING instead of DisplayString = trailing NULL

I'm looking for a way to deal with a situation where we end up with null characters trailing some label values: `count({ifDescr=~".*\x00"}) != 0`. The source of the problem seems to be with `ifDescr` returned as a `Hex-String` instead of what the MIB says should be a `DisplayString`... for __so

[prometheus-users] servers returning Hex-STRING instead of DisplayString = trailing NULL

I'm looking for a way to deal with a situation where we end up with null characters trailing some label values: `count({ifDescr=~".*\x00"}) != 0`. The source of the problem seems to be with `ifDescr` returned as a `Hex-String` instead of what the MIB says should be a `DisplayString`... for __so

[prometheus-users] Re: backfill recording rules creates duplicate metrics on 2 hour border

Thank you! If I can help in any way let me know. On Thursday, September 2, 2021 at 11:17:31 AM UTC-4 jessica...@gmail.com wrote: > This may be similar to this issue: > https://github.com/prometheus/prometheus/issues/9288 > > Going to try to reproduce today and debug. > > On Thursday, September

[prometheus-users] backfill recording rules creates duplicate metrics on 2 hour border

I seem to be getting overlapping/duplicated metrics when trying to backfill recording rules. Working off of this article: https://jessicagreben.medium.com/prometheus-fill-in-data-for-new-recording-rules-30a14ccb8467 my recording rule is: ``` - record: s8_es_syslog_query_count_total5:rate5