Thibault VINCENT
Thibault VINCENT
Hi @AndiDog, That's a neat looking PR, thanks for the attention to detail :smiley: If you don't mind we may only review/merge in a couple weeks, as I'd like colleagues...
Hi @DebakelOrakel, unfortunately there is no globing or regexp support at the moment. This feature would be quite convenient, we're working on it and expect a new release this week....
Hi Indeed identification of affected workloads may be needed to process alerts, for example when dealing with multi-tenant clusters for alerts to be routed to the correct user or team....
Considering this would be an optional feature enabled with a flag, so that nobody gets the additional load on their cluster by default: I have two concerns. First is with...
cc #70
Chart hidden to Artifacthub in https://github.com/enix/helm-charts/commit/9f6ebdcc7260b87b77a6453763e5e2b1c5e8967f
Hi @kruftik, I'm so sorry this PR went unnoticed till now. We'll have a look to your contribution shortly! Cheers
@kruftik, would you mind giving more information on how the `daemonset-name` label is to be used? Is that in conjunction with the Prometheus operator or will that be an other...
Hi @AnuragEkkati You are right this feature is lacking! How would you see filters be added to arguments? A single regexp pattern applied to all target directories may not be...
Hi @kRajr Given these values you must be a Prometheus operator user. It is likely the operator did not select the `ServiceMonitor` object installed by our Helm chart. Troubleshooting could...