Leo Q

related : https://github.com/sonatype-nexus-community/nexus-repository-helm/issues/8

It can be done by disable the specific alert rule and redefine it in https://github.com/prometheus-community/helm-charts/blob/f29a2580f698ab6cac895785fe72886c8a42fec7/charts/kube-prometheus-stack/values.yaml#L194 unfortunately those rules are generated by a script, if you want to provide such feature,...

@jkroepke Thanks for your reply, but this is not what I wanted, the helm chart you provided can only ingest config map, but I want a prometheus that can discover...

It is feasible but not good, many components need to be disabled, including operator, rules, node exporter, kube-metrics and so on. If nobody has similiar need, I'd rather write a...

Exactly, but during the implementation I found it tiring and boring to do this, maybe following @jkroepke is a good idea. What do you suggest, a new helm chart or...

Understand your concern, I dont like two chart for the same reason either, and I also dont want kube-prometheus-stack to depend on another helm chart, thanks for your explaination.

https://opensource.guide/zh-hans/legal/ 我发现国内的这些厂商都喜欢自己发明一些新的 license, 说除了 1234 之外, 我们的软件就是 apache license 的. 但是实际上这些陈述是有以下问题: 1. 法律漏洞, 建议你们找懂行的知识产权律师咨询下, 考虑下如果真的有侵权行为发生, 能否保证自身权益. 2. 说白了这样的协议压根就不符合大部分人或者说我心中的 "open source" , 我非常理解开发则有盈利的需求, 但你们完全可以使用 BUSL 的协议, 大大方方的承认我就是商业软件, 只是源代码公开了. 大可不必宣称自己是开源. https://www.hashicorp.com/bsl

对不起可能我语气不好了，我想表达的建议是： 1. 如果你觉得协议很重要，最好专业协议专业授权，保护好知识产权，这样加几条附加条款不一定有作用，有可能保护不到自己。 2. 如果你觉得协议不重要，只是一个君子协议，就保持原始 apache/MIT 授权，基于lobe 做的企业版闭源或者BUSL 都可以理解。 对于我使用者或者开发者（可能我自大了）其实一个稳定的协议会给人带来很多安全感，在使用时不用担心协议突然有一天换成了 BUSL ，今天加了一个附加条款，我其实不敢确定哪天这个附加条款会不会增加。 有些厂商在这两个线之间跳，一方面声称自己开源，可以自由 fork ，一方面又禁止商业使用，我很感激 lobe chat 给大家带来的这些便利，但是不希望 lobe 也变成这样的两头吃的项目。

``` up{job="vault"} > 0 unless on(instance) vault_core_unsealed ``` for warning alert (part of vault instance sealed) ``` sum(vault_core_unsealed) < 1 or absent(vault_core_unsealed) ``` for critical alert I think this is...

I think it's possible to copy the basic logic of opentelemetry-celery instrument library, https://github.com/open-telemetry/opentelemetry-python-contrib/blob/main/instrumentation/opentelemetry-instrumentation-celery/src/opentelemetry/instrumentation/celery/__init__.py#L112 inject context during publishing and extract them before consuming it. rq has parameter to inject these...