-
Bug
-
Resolution: Done
-
Blocker
-
None
-
None
-
None
I noticed that there are no telemetry metrics right after the deploying the deployment. Once I make some rest calls, then many metrics are available. At least JVM metrics should be available right after the deployment is deployed. Example of JVM metric
PrometheusMetric{key='jvm_memory_used_bytes', tags={jvm_memory_type=non_heap, job=MultipleDeploymentsMetricsTest-first-deployment, jvm_memory_pool_name=CodeHeap 'non-profiled nmethods'}, value='6.710784e+06', type=' gauge', help=' Measure of memory used.'
JVM metrics are tested in TCK here, so it should work also in EAP integration.
Steps to reproduce in upstream MP TS:
- checkout upstream MP TS: https://github.com/marekkopecky/eap-microprofile-test-suite/blob/WFLY-19846-print-metrics/microprofile-telemetry-metrics/src/test/java/org/jboss/eap/qe/microprofile/metrics/namefellow/MultipleDeploymentsMetricsTest.java#L73
- mvn clean verify --fail-at-end -Dmaven.test.failure.ignore=true -Djboss.dist=/path/to/wf/with/new/MP/specs -Dinsecure.repositories=WARN -Dtest=MultipleDeploymentsMetricsTest -Dsurefire.failIfNoSpecifiedTests=false -Dmaven.test.redirectTestOutputToFile=false
- relates to
-
WFLY-20075 MP Telemetry Metrics (OpenTelemetry) without any rest/servlet call
-
- Closed
-