Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash while trying to export metrics for apm-server. #42

Open
erik-bizzdo opened this issue Nov 23, 2020 · 0 comments · May be fixed by #49
Open

Crash while trying to export metrics for apm-server. #42

erik-bizzdo opened this issue Nov 23, 2020 · 0 comments · May be fixed by #49

Comments

@erik-bizzdo
Copy link

Hi,

I have setup beat-exporter as a sidecar to my apm-server in kubernetes but the beat-exporter crashes with the following log message:

{"level":"info","message":"Exploring target for beat type","time":"2020-11-23T17:56:52Z"}
{"beat":"apm-server","hostname":"apmserver-5668d79455-zwfp7","level":"info","message":"Target beat configuration loaded successfully!","name":"apmserver-5668d79455-zwfp7","time":"2020-11-23T17:56:53Z","uuid":"e2243c95-c7e6-47b8-8f04-b82edc41b069","version":"7.9.1"}
panic: descriptor Desc{fqName: "apm-server_up", help: "Target up", constLabels: {}, variableLabels: []} is invalid: "apm-server_up" is not a valid metric name

My guess is that apm-server reports it's name containing a dash which in turn makes beat-exporter generate a non valid Prometheus metric name.
The solution might be to convert all invalid chars in metricnames to underscores, or simply just removing them. In my case I would have been fine with either apm_server_up or apmserver_up.

@xco-sk xco-sk linked a pull request Oct 8, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant