Open jirislav opened 7 months ago
@jirislav Any news on this? I'm having exact same issue only trying to connect Grafana Tempo as remote write source to Prometheus
@jirislav Any news on this? I'm having exact same issue only trying to connect Grafana Tempo as remote write source to Prometheus
No, I have no news, we ended up not using the integration, sadly.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
/remove-lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
/remove-lifecycle stale
I need to deliver metrics from the k6-operator (testing framework from Grafana, runs in jobs) to Prometheus.
At the time of writing this issue, K6 officially supports only the Prometheus remote write as the only way to get the metrics there.
Since the CMO uses
CoreOS
Prometheus operator under the hood, it should be possible to extend the configuration in such a way so that the following is possible:By default, Prometheus has this feature disabled, resulting in
404 Not Found
when trying to use the API:I would expect this to be configured in the Cluster Monitoring Operator configuration in a way similar to these drafts: