*The read and write protocols both use a snappy-compressed protocol buffer
encoding over HTTP.*
I think you have tried to use plain text metrics, when they need to be
represented in protobuf binary format (and *then* compressed)
On Wednesday, 23 November 2022 at 13:14:02 UTC ihor.pi...@gmail.co
On 23/11/2022 15:28, Nenad Rakonjac wrote:
Hello,
Does everyone have clue how much time need for prometheus metrics to
go from application to alertmenager? Can this time be bigger than one
minute? --
Metrics don't go to Alertmanager. Instead you create alerting rules
which query metrics to
Hello,
Does everyone have clue how much time need for prometheus metrics to go
from application to alertmenager? Can this time be bigger than one minute?
--
You received this message because you are subscribed to the Google Groups
"Prometheus Users" group.
To unsubscribe from this group and st
That is a different question than you asked.
Time series depends on the jobs you are scraping. This varies greatly from
one user to the next.
You can graph avg_over_time(prometheus_tsdb_head_series[$__interval]) in
Grafana to see the trend over time.
On Wed, Nov 23, 2022 at 1:41 PM Julio Leal w
Here is a set of correct metrics
cat metrics.prom
# HELP http_requests_total The total number of HTTP requests.
# TYPE http_requests_total counter
http_requests_total{method="post",code="200"} 1027 1395066363000
http_requests_total{method="post",code="400"}3 1395066363000
cat metrics.prom |
Ben, thank you so much for your answer.
My problem is that the prometheus_tsdb_head_series changes a lot over time.
Is there any way to get how much my timeseries is increasing over time (for
example, in the last 3 months)?
On Wed, Nov 23, 2022 at 7:36 AM Ben Kochie wrote:
> I usually recommend
I usually recommend looking at `process_resident_memory_bytes /
prometheus_tsdb_head_series`.
The current typical use is around 8KiB per series, mainly due to the
indexing of series.
On Wed, Nov 23, 2022 at 2:14 AM Julio Leal wrote:
> Hi everyone
> I'm trying understand and create an end of lif
I want to defined serverity level by group name , for example:
rule file:
groups:
- name: *critical_for_xxx*
rules:
- alert:
- name: waring_for_xxx
alerting:
alert_relabel_configs:
- source_labels: [ ... ]
regex: (*critical*).+
target_la
Hi all,
I want to add a label name in subject header. This is not a common label
which we generally defined under target level. The label "name" is coming
in metrics only and i want to see that "name" in email subject. Currently
iam using this header value
[{{ .Status | toUpper }}] {{.CommonLabe
9 matches
Mail list logo
