Micrometer metrics from wildfly. How to overwrite the {job="wildfly"} tag?

12 views
Skip to first unread message

ralfbat...@gmail.com

unread,
Nov 1, 2025, 5:42:28 AM (8 days ago) Nov 1
to WildFly
Dear Wildfly Team

I  am switching to micrometer and pushing metrics to the otel collector. Since we are pushing from several independent processes to the same collector instance, we need to be able to differentiate wildfly metrics which are not in the context of a deployment. Here is an example:

jvm_uptime_seconds{job="wildfly"} 49.984

Is there a way if overwriting the default value "wildfly" ? So that we can identify the uptime for the different processes. 

Best Regards, Ralf

ralfbat...@gmail.com

unread,
Nov 1, 2025, 6:21:43 AM (8 days ago) Nov 1
to WildFly
I forgot to mention:
  • We are using Wildfly 38.0.0
  • Setting of otel.service.name has only affect for opentelemetry metrics but not for the wildfly produced tags
To be honest, I am confused about the three metrics types available. The admin documentation suggests to use one of them because of performance issues but there no clear instructions which kind of metrics are exposed by these 3 metrics implementation.
As far as I can see:
  • application specific metrics are exposed by Micrometer system only
  • jvm metrics are exposed by the opentelemetry metrics system only
  • wildfly metrics? No idea
But I am may wrong

Reply all
Reply to author
Forward
0 new messages