Do not register GC metrics when GC notifications are unavailable #5149
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This addresses the issue that GraalVM currently does not support GC notifications which means no useful GC metrics with Micrometer. Micrometer does not provide any hint and even registers a few useless metrics which only have initial values but never get updates as this relies on GC notifications.
Current GraalVM GCs show the following behaviour:
GarbageCollectorMXBean
exposed but those don't support any notification typesGarbageCollectorMXBean
exposedVerified that the GCs actually work by enabling GC logging via
-XX:+PrintGC
- just to be sure.See the GraalVM issue for this missing feature for reference.