I guess this relates to
https://github.com/prometheus/blackbox_exporter/issues/1051
On Thursday, May 18, 2023 at 4:33:46 PM UTC+2 Ben Kochie wrote:
> Based on what little I can derive from the "data" presented. This is
> probably from Grafana, given that the timestamps are snapped to an even
For proper NVMe metrics monitoring you need additional collector script, for
example:
https://github.com/prometheus-community/node-exporter-textfile-collector-scripts/blob/master/nvme_metrics.sh
--
You received this message because you are subscribed to the Google Groups
"Prometheus Users"
Had two users come at me with "why didn't you...?" because of a machine
that had disk
hardware failures, but no alerts before the device died. They pointed at
these messages
in the kernel dmesg:
> [Wed May 17 06:07:05 2023] nvme nvme3: async event result 00010300
> [Wed May 17 06:07:25 2023]
Hi There,
I have several older kubernetes clusters and I need a way to alert on the
kubelet/kubeadm certs before they expire.
>From the kubernetes-nodes job we get several metrics:
apiserver_client_certificate_expiration_seconds_count
apiserver_client_certificate_expiration_seconds_sum
Based on what little I can derive from the "data" presented. This is
probably from Grafana, given that the timestamps are snapped to an even 15
seconds.
And based on this, I'm guessing this is a misunderstanding of the lookback
/ step interval, which will default to 15s in Grafana.
There's no
On 2023-05-18 11:27, Paweł Błażejewski wrote:
Hello,
Blackbox exporter http module check https site every 15s by default.
Can you please tell me Is it posible to change this interval to 1
minute. I add scrape_interval parametr in prometheus config as you see
below, but it doesn't change
Hello,
Blackbox exporter http module check https site every 15s by default. Can
you please tell me Is it posible to change this interval to 1 minute. I add
scrape_interval parametr in prometheus config as you see below, but it
doesn't change anything. Samples are stiil every 15s.
can you
Also remember a separate alert for "*progress_current >= progress_goal*" if
you need to know if the goal has already been met. The expression I gave
only gives an expected time to reach the goal, if the goal *hasn't* already
been met.
On Thursday, 18 May 2023 at 09:07:24 UTC+1 Brian Candler
Grr, I think I messed up the threshold detection ("> progress_goal") on the
denominator.
Take 2:
expr: |
(*(progress_goal - progress_current) > 0)* /
(( predict_linear(*progress_current*{fstype!~"fuse.*|nfs.*"}[12h],
604800) *> progress_goal*) - *progress_current*) *
> I have seen a bunch of examples for predicting when a disk will fill, but
these all seem to rely on the assumption that a gauge is trending
downwards, and we are predicting when it meets zero.
Here is a better recipe as a starting point, using predict_linear():
10 matches
Mail list logo
