Skip to content

Drop cpu check for the Prometheus configuration in Opentelemetry-java#35

Open
shinhyungyang wants to merge 2 commits intokieker-monitoring:mainfrom
shinhyungyang:otel-java-prometheus-remove-cpu-check
Open

Drop cpu check for the Prometheus configuration in Opentelemetry-java#35
shinhyungyang wants to merge 2 commits intokieker-monitoring:mainfrom
shinhyungyang:otel-java-prometheus-remove-cpu-check

Conversation

@shinhyungyang
Copy link
Collaborator

Would it be okay to drop cpu check for Prometheus? It will help running the measurement on non Intel CPUs

@DaGeRe
Copy link
Collaborator

DaGeRe commented Sep 25, 2025

Did you check it locally whether it works? The check is there since Prometheus did not start on the Raspberry Pi.

If I get it correctly, x86_64 will also be the architecture for amd, just aarm has different architecture (and there, to my knowledge, Prometheus doesn't start).

@shinhyungyang
Copy link
Collaborator Author

Okay! so the next step for me is to check running prometheus-3.6.0.linux-arm64.tar.gz.

@shinhyungyang
Copy link
Collaborator Author

I checked that prometheus runs on the ARM architecture. I just need to debug terminating the process at the end of each run. Somehow the process id stored in the $pid variable is missing.

@DaGeRe
Copy link
Collaborator

DaGeRe commented Sep 30, 2025

Could you try saving the prometheus pid using echo $! > /tmp/prometheus.pid?

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 this pull request may close these issues.

2 participants