You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are scraping our Go services using pyroscope.scrape, which by default sets service_name to namespace/container that it gets from the kubernetes cluster.
I am now configuring TypeScript services in push mode, using the pyroscope.receive_http component in alloy. To make things consistent, I wanted to configure it so the service_name structure is the same. However pyroscope.receive_http refuses these profiles:
ts=2024-11-26T12:12:35.154260341Z level=error msg="Failed to append profile" component_path=/ component_id=pyroscope.receive_http.local appendable=0 err="invalid application name: default/partitionmanager: character is not allowed: '/'"
If '/' is valid in the service_name label (and I assume it is, because the Grafana Pyroscope app uses it for navigating in the service dropdown), then it should also be allowed by the pyroscope.receive_http function.
What's wrong?
We are scraping our Go services using
pyroscope.scrape
, which by default setsservice_name
to namespace/container that it gets from the kubernetes cluster.I am now configuring TypeScript services in push mode, using the
pyroscope.receive_http
component in alloy. To make things consistent, I wanted to configure it so theservice_name
structure is the same. Howeverpyroscope.receive_http
refuses these profiles:ts=2024-11-26T12:12:35.154260341Z level=error msg="Failed to append profile" component_path=/ component_id=pyroscope.receive_http.local appendable=0 err="invalid application name: default/partitionmanager: character is not allowed: '/'"
If '/' is valid in the
service_name
label (and I assume it is, because the Grafana Pyroscope app uses it for navigating in the service dropdown), then it should also be allowed by thepyroscope.receive_http
function.Steps to reproduce
In a nodejs application
Observe alloy logs.
System information
Linux / Kubernetes
Software version
Grafana Alloy v1.5.0
Configuration
Logs
The text was updated successfully, but these errors were encountered: