Expose some basic catalog and config metrics to be exported by micrometer #226
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.
Expose some basic catalog and config metrics to be exported by micrometer.
If
spring-boot-actuator
is present on the (GeoServer) application,and the config propery
geoserver.metrics.enabled=true
(default),the following metrics are exported through micrometer, with the
instance-id
tag matching theinfo.instance-id
value to easeslicing by service when aggregating values on an external system.
geoserver.config.update_sequence
: The configuration update sequence.geoserver.catalog.added
: Number of CatalogInfo objects added tothis instance's Catalog
geoserver.catalog.removed
: Number of CatalogInfo objects removedon this instance's Catalog
geoserver.catalog.modified
: Number of modifications to CatalogInfoobjects on this instance's Catalog
They can then be monitored at each instance's actuator endpoint. For
example:
References: