Description
We are trying to migrate from pure alloy helm chart to grafana-k8s-monitoring. We've been using custom alloy config including some logic around seeding metrics required for Grafana Service Graphs using this documentation.
Relevant parts of our config.alloy:
otelcol.receiver.otlp "default" {
grpc {
endpoint = "0.0.0.0:4317"
include_metadata = true
}
output {
metrics = []
logs = []
traces = [otelcol.processor.attributes.default.input]
}
}
otelcol.processor.attributes "default" {
[..]
output {
metrics = []
logs = []
traces = [otelcol.connector.servicegraph.default.input, otelcol.processor.tail_sampling.default.input]
}
}
otelcol.connector.servicegraph "default" {
dimensions = ["http.method"]
output {
metrics = [otelcol.exporter.prometheus.default.input]
}
}
otelcol.exporter.prometheus "default" {
forward_to = [prometheus.remote_write.grafanacloud_xxxxx_prom.receiver]
}
I was wondering whether this grafana-k8s-monitoring chart would provide some templating around the otelcol.connector.servicegraph. I failed to find a way to enable this functionality without using extraConfig entities, and even in that case I'm not sure what would be the best flow (i.e. where exactly we should put otelcol.connector.servicegraph "proxy").
Appreciate any pointers.
Metadata
Metadata
Assignees
Labels
No labels