Juris Pavļučenkovs

Having the same issue with 1632.3.0 on m5.large ``` NAME="Container Linux by CoreOS" ID=coreos VERSION=1632.3.0 VERSION_ID=1632.3.0 BUILD_ID=2018-02-14-0338 PRETTY_NAME="Container Linux by CoreOS 1632.3.0 (Ladybug)" ANSI_COLOR="38;5;75" HOME_URL="https://coreos.com/" BUG_REPORT_URL="https://issues.coreos.com" COREOS_BOARD="amd64-usr" ``` Running Kubernetes...

Having the same issue with degraded HPA. Looks like it happens because HPA does not have enough metrics during a rollout. Potentially, it can be mitigated by increasing HPA cpu...

Yes, please! Blackbox probe metrics do not have namespace labels as well.

In a Kubernetes cluster, when one of the Sentinels restarts and gets a new IP address, client starts throwing errors like this one: ``` [ioredis] Unhandled error event: Error: connect...

Having about the same issue. Moreover, excluding svg files does not help. Insider launch ``` docker run --rm -v $(pwd):/target-project insidersec/insider -v -tech javascript -target /target-project -exclude client/public/res/* -exclude test/*...

Worked for me with this config: ``` driver: enabled: true kind: ebpf loader: initContainer: securityContext: privileged: true ``` Bottlerocket OS 1.9.2 (aws-k8s-1.22)

Got the same issue with Grafana 9.2.6, Oncall 1.1.5 and Helm 1.0.12. After couple of days Oncall setup becomes useless. Removing OnCall API key from https://grafana/org/apikeys helps till the next...

Sentinels work for me with the following: ```js // config.REDIS_DB = "1"; // config.SENTINEL_REDIS_PRIMARY = "redis-primary-name"; // config.SENTINELS = "sentinel-1:26379;sentinel-2;26379;sentinel-3:26379"; const redisConfig = { db: config.REDIS_DB, }; if (config.SENTINELS !==...

Issue still exists with 0.9.3

As I can see, this exporter allows to monitor multiple zk instances at once.