Currently, we have the custom templating function for grafana alerting right in the code https://github.com/grafana/grafana/blob/8053f770c1ff83827748b53edafb0a8257fb4a45/pkg/services/ngalert/state/template.go#L60-L68
To do better validation etc. we need to centralize those functions so that we can reuse them were ever we need them.
We already have some scripts in the scripts directory. It would be good to run them for every PR.
This is also a great task for beginners.
We should provide multi-architecture Docker images of skywalking-eyes, just like other SkyWalking sub-projects.
No response
No response
Currently promtail supports reading logs from a Kafka topic, and write out to a Loki installation.
The feature request is for promtail to have the ability to write logs to a Kafka cluster, the reason explained below.
Describe the solution you'd like
Kafka can be found in many organisations, and is often times used as a way to have a central place for information to flow through. This so
On https://thanos.io/tip/thanos/changelog.md/ -> Table of Contents
This link v0.25.2 - 2022.03.24 should actually go towards https://thanos.io/tip/thanos/changelog.md/#v0252httpsgithubcomthanos-iothanostreerelease-025---20220324
Perhaps this page / table of contents could be easier/nicer as well - For example that the table of contents
Replace this parsers in node exporter with this ones from procfs.
It is not possible to define SecurityContext for Containers of Alermanager (only PodSecurityContext is available). Because of the missing Container SecurityContext it's not possible to setup important sec
Spent the morning debugging what I thought was a goroutine leak, but turned out to be just a huge number of goroutines being created in a short period of time. However, it seems a lot of the unit tests do leak goroutines. Most of these might just be issues with tests not cleaning up properly, but it makes testing/debugging real leaks quite difficult. Or in my case, the leaks were a red herring - t
README.md is still pointing to addons/strip-limits.libsonnet addon as a way to strip containers from set resource limits. However since release-0.8 resource requests are first-level settings and users should use
What happened:
I created a pod with a "com.acme/fooBar" label.
The l
I'm expecting to be able to filter out the requests from blackbox exporter in my access logs.
So, please, add a user agent header that container the "blackbox exporter" string somewhere.
I see User-Agent: Go-http-client/1.1
Not easy to filter in the access logs...
In subsequent PRs. We should add integration tests for debuginfo.Store.Exists and debuginfo.Store.Upload using the debuginfo.Client.
Originally posted by @kakkoyun in parca-dev/parca#1157 (comment)
Add a description, image, and links to the prometheus topic page so that developers can more easily learn about it.
To associate your repository with the prometheus topic, visit your repo's landing page and select "manage topics."
Hi,
first thanks for this awesome software. But I have some trouble and I don't know how to proceed. First I try to find out what else I could provide for this report to be a good bug report.
First, I use the latest version (v1.14.0) from openSUSE build Service. I know, I should compile it by my self to avoid any other causes for this behavior. But for now I still use this package from there