virtualb0x

@adchia can u be so kind to show an example of pod annotations that can configure access to s3 ?

Good day to everyone Can you plz tell how soon can this feature be implemented?

Will this plugin work for manifests-only? Not only for helm and kustomize? Some day in future?

Hello! Thank you for the fast reply :) VMalert is of version 1.82 I suppose (from my pod): ``` # /vmalert-prod --version vmalert-20221007-005142-tags-v1.82.0-0-g832276064 ``` Grafana data:  As for vmui...

I suppose it returns: ``` {"name":"k8s.rules","rules":[{"ruleState":"","name":"node_namespace_pod_container:container_cpu_usage_seconds_total:sum_irate","query":"sum by (cluster, namespace, pod, container) (\n irate(container_cpu_usage_seconds_total{job=\"kubelet\", metrics_path=\"/metrics/cadvisor\", image!=\"\"}[5m])\n) * on (cluster, namespace, pod) group_left(node) topk by (cluster, namespace, pod) (\n 1, max by(cluster,...

Yes, we can It happens to all rules I have in VM:  It's also weird because an error metrics also show zero. Example: **vmalert_recording_rules_error**{recording="node_quantile:kubelet_pleg_relist_duration_seconds:histogram_quantile", group="kubelet.rules", id="8563899369226980997"} 0 **vmalert_recording_rules_last_evaluation_samples**{recording="node_quantile:kubelet_pleg_relist_duration_seconds:histogram_quantile", group="kubelet.rules",...

No, it is not expected. I picked up the random record rule as an example Let us check several more rules 1. ``` vmalert_recording_rules_last_evaluation_samples{recording=":node_memory_MemAvailable_bytes:sum", group="node.rules", id="4238716903624357938"} 0 ``` ``` {"ruleState":"","name":":node_memory_MemAvailable_bytes:sum","query":"sum(\n...

Hello. I'll try to do it in a week. I've already upgraded the VMalert version to the last 1.84 one. Nothing changes. Can you please tell me the oldest version...

Hi! I tested with docker-compose. It shows everything is ok  Don't understand whats wrong with k8s installation with vm stack helm. But still problem seems to be on my...

I've found out the reason. We have rulePath: - "/etc/vmalert/config/vm-victoria-rulefiles-0/*.yaml" - "/etc/vmalert/config/vm-victoria-alertfiles-0/*.yaml" in vmalert configuration. ``` vmalert: enabled: true # spec for VMAlert crd # https://github.com/VictoriaMetrics/operator/blob/master/docs/api.MD#vmalertspec spec: selectAllByDefault: true image:...