Alexander Wilke

Hello, for my environment I use a workaround and add an additional label to ech metric: smokeping_prober.yml ``` targets: #====================================================================================================================================================== - hosts: ### target_group: LAN-GW - 192.168.10.1 - 192.168.178.1 ###...

Use a recording rule to generate the interval you need. Then use write_relabel_configs to only forward the metrics generated by the recording rule using remote_write

Hi @pracucci in my environment I think RF=2 ist something I need. We have two DataCenters and I want to make sure if one DataCenter is down the other one...

Did you try to use the dashboard.json from this repository? Works for me out of the box. The heatmap query looks like this. I modified it a little bit but...

I changed the promQL query a little bit and added "host" and "ip" to use it in legend or description; `sum(rate(smokeping_response_duration_seconds_bucket{host=~"$target"}[1m])) by (le,ip,host)` If I now select two targets in...

> I even tried setting it up this way: > > ``` > - job_name: 'smokeping' > # file_sd_configs: > # - files: > # - '/etc/prometheus/smokeping_exporter_targets.yml' > relabel_configs: >...

I would like to have this auto reload, feature, too. In addition I would like to have the possibility to store these config files on remote storage like NFS or...

Hello, I think this is not a feature request it is a bug. If you use the default declaration the formatting of the metrics ist correct. If you collect the...

The metrics names should be the same if I query the same metrics than in default configuration. The reason for that is pretty simple. If I query all metrics every...

This is another bug in the OpenTelemetry Streaming app. If you use the "OpenTelemetry Push" consumer and you send the default metrics to Prometheus (https://prometheus.io/docs/prometheus/latest/feature_flags/ --enable-feature=otlp-write-receiver) you have information about...