Upped readme's.

README.adoc

@@ -19,8 +19,12 @@ places in VPRO artifacts.
 * link:vpro-shared-elasticsearch-client[vpro-shared-elasticsearch-client]: Related to elasticsearch low level client
 * link:vpro-shared-elasticsearch-high-level-client[vpro-shared-elasticsearch-high-level-client]: Related to elasticsearch high level client
 * link:vpro-shared-swagger3[vpro-shared-swagger3]: Some utilities related to swagger frontend and openapi. Depends on webjars to provide the actuall swagger frontend too
+
+* link:vpro-shared-monitoring[vpro-shared-monitoring]: Kind of like spring-actuator, for non-springboot applications. Providing the monitoring endpoints which can be used by openshift for example.
 * link:archived/vpro-shared-couchdb-util[vpro-shared-couchdb-util]: Lightweight and streaming couchdb clients
 * link:archived/vpro-shared-swagger[vpro-shared-swagger]: Some utilities related to swagger frontend. Depends on webjars.
+
+ r frontend. Depends on webjars.
 * ..
 
 == Builds
@@ -74,7 +78,7 @@ Release builds will be provided via https://search.maven.org/search?q=g:nl.vpro.
 
 | 5.4
 |
-| January 2025 
+| January 2025
 
 
 | 6.x >

vpro-shared-monitoring/README.adoc

@@ -5,13 +5,17 @@
 Related to monitoring.
 
 This basically adds endpoints:
+
+[source]
+----
 /manage/health
 /manage/metrics
+----
 
 to a spring application.
 
-Normally just taking the dependency should suffice.
+Normally just taking the dependency should suffice. It can be configured with spring properties (`monitoring.*`, see link:src/main/java/nl/vpro/monitoring/config/MonitoringConfig.java[`MonitoringProperties`]), which the most important one may be
 
-TODO: test/document this a bit better?
+All have defaults, or can be set via system properties (such as for example the username/password for the monitoring endpoint)
 
 Used in spring openshift applications of VPRO and POMS