Release Notes 74
Publication date: 18/06/2026
This document provides a detailed summary of the new features, functionalities, improvements and bug fixes included in version 74 of WOCU-Monitoring. This update addresses our users’ requests and suggestions, whilst ensuring we remain in line with current market trends and requirements.
1. New advanced filter to identify and manage assets with notifications disabled
The Disabled Notifications filter has been added to the Advanced Filters block in the Hosts, Services and Problems lists. This option allows you to identify assets for which notifications have been disabled using the individual action Disable Notifications for…, available for monitored devices and services.
The new feature improves asset and alarm management by providing a clear overview of silenced items, reducing operational noise and making it easier to prioritise incidents that require attention.
It is very easy to use: tap the Disabled Notifications box several times to toggle between its different states and decide whether the relevant assets should be included or excluded from the list.
This filter can be combined with the other options available in Advanced Filters to produce more precise search results.
Figure 1: View of the Disabled Notifications filter in Advanced Filters(Host list).
2. New HTML and Markdown widgets in the Status view
The Status view in WOCU-Monitoring incorporates the new widget_html and widget_markdown widgets, designed to add informative and customised content directly to the customisable dashboards. This gives users greater freedom to customise the views without having to develop new components.
These widgets can be used to include operating procedures, notices, instructions, to-do lists, links, images, network diagrams and information specific to each environment.
The widget_html widget allows you to create content using validated HTML tags, whilst the widget_markdown widget offers a visual editor with formatting options, image insertion and keyboard shortcuts.
Figure 2: Markdown widget with formatted information and an integrated network topology diagram.
With these new components, it is possible to:
Creating dashboards that are more descriptive and tailored to each team or client.
Centralisation of operational information alongside monitored data.
Quick access to procedures, contact details or any other information of particular relevance to the user.
Inclusion of diagrams or other visual material and supporting documentation.
3. Metrics forecast
The new Forecast feature has been added to the Metrics view, allowing you to view the estimated trend of a metric for a future period of up to 1 day.
The forecast is shown in a specific colour and as a line distinct from the historical data. For metrics with multiple time series, you can select which of these you wish to display the forecast for.
This functionality makes it easier to anticipate potential trends or anomalous behaviour, enabling the early detection of approaches to critical thresholds and supporting more proactive management of the monitored resources.
The feature is activated via a new button marked with a telescope icon and is available only on Realms where the Observability module is enabled and Elasticsearch is used as the backend technology.
Figure 3: The Forecast view in Metrics, showing the predicted future trend for the metric.
4. New integrations in Anomalies
New Anomalies view in Observability
The new view anomalies_observability has been added to the Observability, which centralises all anomalies detected in the selected Realm over the last 24 hours in a single table.
The view provides detailed information on each anomaly, including date and time, score, host, service, metric, current value, typical value and deviation level. This information enables the rapid detection of unusual behaviour, allows the most relevant anomalies to be prioritised according to their score, streamlines incident analysis and provides a centralised view of the deviations detected across the whole of the Kingdom.
In addition, the following is included for incident management:
Filter by time range, with predefined periods and custom selection.
Filter by Score, to filter anomalies according to their level of significance. The score, which ranges from 0 to 100, quantifies the extent to which the observed value deviates from expected behaviour. The higher the score, the greater the significance of the anomaly.
Figure 4. Overview of Anomalies in Observability, with filters by time range and score.
New Deviation column in the anomalies table
A new column, Deviation, has been added to the Device-level anomalies table, providing further context to quickly assess the magnitude of the detected deviations and facilitate their operational analysis.
This new field makes it easier to interpret the detected anomalies by directly showing the difference between the actual value recorded (Actual) and the expected value (Typical). As well as indicating the magnitude of the deviation, it allows you to identify whether the observed value is above or below the usual behaviour.
For example, a value such as 3.42x higher indicates that the recorded value is approximately 3.42 times higher than the expected value.
The new Deviation column complements the information provided by Score. Whilst Score expresses the significance of the anomaly using a normalised score, Deviation provides a more intuitive indication of how far the observed value has deviated from its expected behaviour.
Figure 5. View of anomalies at device level with the new Deviation column.
New Score filter in the Hosts anomalies view
A new Score filter has been added to the Anomalies view for Hosts, designed to make it easier to identify and analyse anomalies according to their level of significance.
The Score, which ranges from 0 to 100, quantifies the extent to which the observed value deviates from the expected behaviour. The higher the Score, the more significant the anomaly.
Figure 6. View of the Score filter applied to the analysis of anomalies on a host.
To make filtering easier, the results are grouped into four ranges:
5–25: low anomaly. The value shows a slight deviation from what is expected.
25–50: moderate anomaly. The deviation is starting to become significant.
50–75: high anomaly. The observed behaviour clearly deviates from the expected pattern.
75–100: very high anomaly. This represents the most significant or unusual deviations.
In this way, the user can narrow down the results and focus the analysis on those anomalies that exhibit a certain level of significance within the selected Service, Metric and time interval.
With this improvement, the host anomalies view now includes enhanced filtering capabilities, enabling the most significant deviations to be identified and prioritised more quickly.
Anomalies can be viewed at service level
The Anomalies view has been expanded and is now also available for a specific Service, allowing you to analyse the anomalies associated with its metrics directly.
With this enhancement, anomaly analysis is now available across the three main levels of WOCU-Monitoring: Realm, Host and Service, enabling more precise navigation from an overview down to the details of a specific service.
Figure 7. View of anomalies in the SSH Disks Stats service.
5. Bulk configuration of dynamic thresholds
WOCU-Monitoring includes a new option to enable or disable dynamic thresholds en masse across multiple hosts, simplifying their configuration when this functionality needs to be applied to a large number of assets.
Bulk configuration is available from: Monitored Assets > Hosts > Massive Configure > massive_dinamic_threshold.
Dynamic thresholds enable certain metrics to be assessed by taking into account their historical behaviour and the expected range of values, making it easier to detect deviations or anomalous behaviour that might not be identified using static thresholds.
When you select this option, a window appears containing the following fields:
Hosts: allows you to select the hosts to which the configuration will be applied.
Packs: displays the packs that are compatible with the dynamic threshold feature.
Dynamic thresholds: allows you to select Enable or Disable to enable or disable this feature for the selected items.
This new option makes it easier to manage environments with a large number of devices, as it allows settings to be applied in bulk, thereby avoiding the need for manual adjustments on a device-by-device basis.
For example, it is possible to select several devices that use the networkdevice-cpu package and enable dynamic thresholds for all of them in a single operation.
6. New endpoints for monitoring metrics and events
Endpoint for listing available metrics
This endpoint returns the existing metrics for a specific realm (such as CPU usage, latency or network traffic) and allows you to narrow down the search by specifying a particular device or service.
It is the ideal starting point if you do not know in advance the exact names of the metrics you wish to view later.
GET /api/metrics/realm/<realm_name>/measurements/
Example of a request:
curl -H "Authorization: Token abc123" \
"https://<dominio>/api/metrics/realm/<realm_name>/measurements/?host=srv-web01"
Sample answer:
["cpu_usage_user", "disk_free", "network_in", "network_out", "memory_used"]
Endpoint for retrieving the values of a metric
This endpoint returns the actual data (the time series points) for one or more metrics for a specific realm, device or service within a particular time window.
GET /api/metrics/realm/<realm_name>/data/
Features designed to make it easier to use:
Readable date formats: You can enter dates in a standard format (for example,
24/07/2026or24/07/2026 14:30:00), without needing to use timestamps.Default range: If you do not specify a date, the information for the last hour will be displayed automatically.
Range limit: The maximum range permitted per query is 7 days.
Automatic metric detection: If you omit the metrics from the query, the system will detect them automatically (subject to a limit on the number of results returned).
Result filtering: You can limit and sort the number of results returned according to your requirements.
Example of a request:
curl -H "Authorization: Token abc123" \
"https:///<dominio>/api/metrics/realm/<realm_name>/data/?host=srv-web01&measurements=cpu_usage_user,disk_free&time_from=24/07/2026%2000:00:00&time_to=24/07/2026%2023:59:00"
Sample answer:
{
"data": [
{
"metric": "cpu_usage_user",
"data": [
{ "time": "2026-07-24T10:00:00Z", "host_name": "srv-web01", "value": 42.1, "min": 38.0, "max": 55.3, "unit": "%" },
{ "time": "2026-07-24T11:00:00Z", "host_name": "srv-web01", "value": 39.7, "min": 35.2, "max": 48.9, "unit": "%" }
]
}
],
"total_count": 1
}
Endpoint for viewing event monitoring data
It allows you to view the event history for a Realm, such as device and service outages and recoveries, notifications sent, status changes, flapping events or external commands. It allows you to apply multiple filters (by host, event type, message text or status) and narrow down the search by date range, in the same way as the metrics endpoint.
GET /api/events/realms/<realm_name>/events/
Example of a request:
curl -H "Authorization: Token abc123" \
"https:///<dominio>/api/events/realms/<realm_name>/events/?host=srv-web01&state_type=HARD&size=20"
Sample answer:
{
"data": [
{
"time": 1753349400,
"host_name": "srv-web01",
"type": "HOST ALERT",
"state": 1,
"state_type": "HARD",
"message": "PING CRITICAL - Packet loss = 100%"
}
],
"total_count": 1
}
Endpoint for viewing syslog events
It allows you to search directly within a Realm’s syslog records, filtering by device, severity, message, event type or identifier.
GET /api/events/realms/<realm_name>/events/syslogs/
Example of a request:
curl -H "Authorization: Token abc123" \
"https:///<dominio>/api/events/realms/<realm_name>/events/syslogs/?host=srv-web01&severity=err"
Sample answer:
{
"data": [
{ "@timestamp": "2026-07-24T09:12:33Z", "host": "srv-web01", "severity": "err", "message": "disk quota exceeded" }
],
"total_count": 1
}
Note
If the realm_name corresponds to a Multi-realm, this endpoint automatically queries the syslog of all the realms that make it up and returns the combined results.
7. Bulk configuration of Inventory
WOCU-Monitoring introduces a new option to enable the bulk collection of inventory data across multiple hosts, simplifying configuration when this functionality needs to be applied to a large set of assets.
Bulk configuration is available starting from:
Monitored Assets > Hosts > Massive Configure > Inventory
This action enables the Inventory functionality on the selected hosts, causing them to begin collecting inventory information associated with the monitored asset.
When you select this option, a window appears containing the following fields:
Hosts: allows you to select the hosts to which the configuration will be applied.
Inventory: enables the collection of inventory data for the selected items.
Once the configuration is applied, the selected devices will begin collecting inventory data, which will subsequently be available from the Inventory tab of the host detail view.
This action streamlines the management of environments with numerous devices, as it enables the functionality to be activated centrally and reduces the need to make manual changes to each asset.
Other improvements and fixes
Every new version is packed with minor changes, fixes and optimisations that are worth mentioning briefly. Here is a list of the most notable ones in this version:
The Export function has been added to the lists for Contacts, BP Hosts and BP Services. This new option allows you to download the visible data in CSV and JSON formats, making it easier to analyse, process and integrate with other external tools.
A new feature has been added to the Single Metrics Graph widget, allowing you to select a specific time interval on the graph using the mouse in order to zoom in and analyse the data. Once you have made your selection, a new button appears, which allows you to quickly restore the time range originally defined in the widget’s settings.
A new magnifying glass icon featuring a stylised eye has been added to the Realm Selector; it appears next to the names of those realms where the Observability is enabled. This visual cue makes it quick and easy to recognise them.
The AI assistant in the Observability incorporates improvements to reliability and usability. Conversations now display the date and time of each query, allow you to pause ongoing responses, and resolve chat freezes or incomplete replies. Furthermore, errors are clearly displayed on screen, preventing silent failures.
From this version onwards, the Problems view will now display all reported issues, including those with the Acknowledged status, regardless of whether the user preference Filter acknowledged is enabled. However, this preference continues to behave as usual in the Summary views.
The selector_category_summary in the Aggregator Summary section now applies an
ANDlogic when multiple categories are selected. This means that only kingdoms assigned to all the selected categories are displayed, providing more accurate results. Searches with a single category retain the previous behaviour. This new behaviour is indicated in the new help message next to the selector (Results must match all selected categories).The Host creation endpoints in the public API include the new optional field
hostgroups, which allows one or more Host Groups to be associated during the registration process. The field accepts a list of strings, for example:"hostgroups": ["hostgroup1", "hostgroup2"]. If any of the specified Host Groups do not already exist, the endpoint itself will automatically create them.Fixed a bug in the Metrics Evolution reports which could cause the frontend to crash when a metric did not include any of the values
mean,minormax. The visualiser now correctly handles metrics with partial values, preventing errors when any of this data is unavailable.Updated the colour of help messages in Summary Category so that they match the selected theme (Light/Dark) correctly, improving their visibility and ensuring a consistent look and feel with the interface.
An information message has been added during the loading process when the action_ask_IA is executed, informing the user that the operation may take a few minutes whilst the response is being generated.
A bug has been fixed that could cause the Multimetric Report to fail when a metric was assigned an empty value. The report now handles these cases correctly and continues to display the available information.
The display of the Global Status widget has been improved in narrow spaces. When its width is less than
350 px, the headings are replaced by icons to optimise space and prevent text from spilling over.In the Single Metrics Graph widget, the configuration option Always Show thresholds has been renamed to Show fixed thresholds, providing a clearer description of its functionality and avoiding any potential confusion.
In the Metrics for a specific host, the magnifying glass icon used to adjust the focus of the Y-axis is replaced by a warning icon (a triangle with an exclamation mark), which more accurately reflects its function in relation to the display of thresholds.
About WOCU-Monitoring
WOCU-Monitoring is a multi-purpose monitoring tool that integrates the latest open-source technologies for monitoring, visualisation, metric charting and log management, providing comprehensive visibility into the status and availability of network elements, servers, databases and workstations (among others) using bespoke Monitoring Packs.
In addition to the Free version, the Enterprise version of WOCU-Monitoring allows the deployment of thousands of IP devices in a distributed environment, with customizations tailored to each client’s infrastructure.