From 0fdbd7b0289941fcc37266797587b71c2679f951 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Aur=C3=A9lien=20Manteaux?= Date: Thu, 16 Jan 2025 18:28:13 +0100 Subject: [PATCH] Add migration monitoring precision --- docs/releases/RELEASE_v5.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/releases/RELEASE_v5.md b/docs/releases/RELEASE_v5.md index 7b737a7..6382b08 100644 --- a/docs/releases/RELEASE_v5.md +++ b/docs/releases/RELEASE_v5.md @@ -200,6 +200,10 @@ To do that: - In `GrizzlySetup`, in the `start()` method: - add the following dependency in the method signature: `GrizzlyThreadPoolProbe grizzlyThreadPoolProbe` - declare the prob in the http server configuration: `httpServer.getServerConfiguration().getMonitoringConfig().getThreadPoolConfig().addProbes(grizzlyThreadPoolProbe);` +- In `WebApplication`, fill the new `GrizzlySetup` dependency using `injector.getInstance(GrizzlyThreadPoolProbe.class)` - In `MonitoringWs`, in the constructor: - add the following dependencies in the method signature: `GrizzlyThreadPoolProbe grizzlyThreadPoolProbe` and `HikariDataSource hikariDataSource` - Use the metrics: `this.metricsStatusProvider = new MetricsCheckBuilder().registerJvmMetrics().registerGrizzlyMetrics(grizzlyThreadPoolProbe).registerHikariMetrics(hikariDataSource).build()` + +The [Plume showcase project](https://github.com/Coreoz/Plume-showcase) has implemented this monitoring. +Browsing the source code can help to verify the required changes.