ID: 15984
Title: Introduce Saas edition werks
Component: Other Components
Level: 1
Class: New feature
Version: 2.3.0b1
We can write saas edition werks now
ID: 15979
Title: bi: return 404 status code when trying to retrieve a non existing rule
Component: REST API
Level: 1
Class: Bug fix
Version: 2.0.0p38
Prior to this werk, the get bi rule endpoint returned a 500 status code whenever
the user tried to get a non existing rule. This werk fixes this and returns a
404 status code instead.
ID: 15892
Title: ntop_alerts: rename alert tabs in ntop alerts dashboard
Component: cmc
Level: 3
Class: Bug fix
Version: 2.3.0b1
Previously, the alert tabs were named Engaged, Host, Flow. This didn't
align correctly with ntopng's own dashboard. They have now been renamed
to Engaged Host, Past Host and Past Flow.
ID: 15893
Title: ntop_alerts: introduce pagination to ntop alerts dashboard backend
Component: cmc
Level: 3
Class: Bug fix
Version: 2.3.0b1
Previously the alerts dashboard would fetch 5 hours of alert data
by default or the time range selected by the user via the time series
graphs. This caused performance issues since the number of alerts
could vary greatly, often resulting in timeouts. This werk addresses
this problem by introducing pagination on the backend. We now only
fetch 20 alerts in any given api call. The user can then request more
using the next button.
ID: 15902
Title: CPU utilization: Make core numbering consistent
Component: metrics
Level: 1
Class: Bug fix
Version: 2.3.0b1
Currently, the cores shown for the per core utilization are numbered starting at 1, while elsewhere the numbering starts at 0.
This has been made consistent by changing the start to 0 for the per core utilization as well.
ID: 15900
Title: mssql_tablespaces: Re-enable cluster mode
Component: Checks & agents
Level: 1
Class: Bug fix
Version: 2.0.0p38
This werk fixes an issue introduced in 2.0.0p36 where the mssql_tablespaces plugin could not be used as a clustered service.
The error "This service is not ready to handle clustered data. Please change your configuration." will no longer occur.
ID: 15162
Title: Error in fetchers results in 100% CPU load in microcore
Component: Core & setup
Level: 1
Class: Bug fix
Version: 2.1.0p31
This fixes a case where an error in the fetcher would result in high
CPU load in the CMC process.