The receiver suffix was stale — the grafana-k8s-monitoring module deploys a single Service named k8s-monitoring-alloy in the monitoring namespace, not k8s-monitoring-alloy-receiver. Pods were failing to ship traces with:
dial tcp: lookup k8s-monitoring-alloy-receiver.monitoring.svc.cluster.local on 100.64.0.10:53: no such host
Drop the -receiver suffix so the OTLP exporter resolves the correct service.
The receiver suffix was stale — the `grafana-k8s-monitoring` module deploys a single Service named `k8s-monitoring-alloy` in the `monitoring` namespace, not `k8s-monitoring-alloy-receiver`. Pods were failing to ship traces with:
```
dial tcp: lookup k8s-monitoring-alloy-receiver.monitoring.svc.cluster.local on 100.64.0.10:53: no such host
```
Drop the `-receiver` suffix so the OTLP exporter resolves the correct service.
The receiver suffix was stale — the grafana-k8s-monitoring module
deploys a single Service named k8s-monitoring-alloy in the monitoring
namespace, not k8s-monitoring-alloy-receiver. Pods were failing to
ship traces with:
dial tcp: lookup k8s-monitoring-alloy-receiver.monitoring.svc.cluster.local
on 100.64.0.10:53: no such host
Drop the -receiver suffix so the OTLP exporter resolves the correct
service.
argoyle
merged commit 43765101f5 into main2026-05-19 05:13:52 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The receiver suffix was stale — the
grafana-k8s-monitoringmodule deploys a single Service namedk8s-monitoring-alloyin themonitoringnamespace, notk8s-monitoring-alloy-receiver. Pods were failing to ship traces with:Drop the
-receiversuffix so the OTLP exporter resolves the correct service.