-
### Is your feature request related to a problem? Please describe
We use OpenTelemetry (OTel) pipeline to collect and deliver metrics to end-databases. It allows us to implement parts of custom logic…
-
**Describe the bug**
When I configure metrics generator on Grafana Tempo, I had a misconfigured TLS path.
But metrics generator pod boots up and crashed immediately.
In the full crash log, it s…
-
## Is your feature request related to a problem? Please describe.
Problem is storing perfdata in a Prometheus-compatible storage (Victoriametrics, Cortex, Thanos, Mimir etc) for it to be compatible…
p4k8 updated
4 months ago
-
### Proposal
Part of https://github.com/prometheus/prometheus/issues/14217
With the [PRW 2.0 spec](https://github.com/prometheus/docs/pull/2462) comes implementation and metadata per series logi…
-
We have a replicated (HA) Prometheus setup in our cluster, so when using remote write to push metrics into Prometheus, we have to push to all replicas in parallel—otherwise, only one replica will have…
-
Remote storage, particularly remote write, has a lot of metrics as it has grown organically. Some metrics have names or help text that aren't necessarily still accurate, and we have many metrics that …
-
### What did you do?
1. Configure remote read in Prometheus.
2. Issue a large number of queries that trigger remote read.
```
up{job="cloudwatch",la=~"va",lb!~"vb",debug="true"}
```
### What…
-
### Bug Description
Since mysql-router is a subordinate charm, we first relate grafana-agent with the principal charm (on the `juju-info` interface). Then, we relate `grafana-agent:cos-agent mysql-ro…
-
**Is your feature request related to a problem? Please describe.**
Collect metrics from Flunetbit's API directly via TLS instead of going out from prometheus_remote_write.
**Describe the solution …
duj4 updated
2 months ago
-
### Request
The `prometheus.operator.*` components allow for relabeling rules, but they cannot be passed in via reference.
Currently they are defined as
```river
prometheus.operator.se…