hellorill

Unfortunately it didn't work. VMAlert sections for remoteRead/remoteWrite: ``` remoteWrite: url: "http://m3coordinator.example.com/api/v1/prom/remote/write?extra_label=remotewrite_source=test" concurrency: 4 remoteRead: url: "http://m3query.example.com?extra_label=remotewrite_source=test" ``` When querying ALERTS and ALERTS_FOR_STATE from m3query, remotewrite_source tags are missing from...

Found solution for remoteWrtie in the documentation: externalLabels, it works, but I'm not sure, that remoteRead uses those labels to limit alert requests.

Checked in the code, externalLabels is loaded at startup in the manager and used in rr/rw. Also, checked Alertmanager, multiple instances of VMAlert using different alerts from the remoteRead, filtering...

Unfortunately didn't test this for vmrule, it doesn't work, VMAlert queries metrics globally and writes rule results to global tenant.

We have the same problem. Previously, everything worked correctly, until the partitions of most topics were rebalanced. It looks like the processing of all responses is not entirely correct. https://github.com/danielqsj/kafka_exporter/blob/b66d284be28b53fe37ca472029fefa4a521d9f6e/kafka_exporter.go#L593-L595...

Looked more detail, in the GroupDescription structure there are Err/ErrorCode fields, that are not checked by the exporter for errors in the Kafka response. Therefore, the exporter always believes, that...

Actually, adding the following check resolves the metric error. ``` ... for _, group := range describeGroups.Groups { if group.Err != 0 { continue } offsetFetchRequest := sarama.OffsetFetchRequest{ConsumerGroup: group.GroupId, Version:...