Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Tracer

With Enginsight's Tracer feature, you can set up Machine Learning (ML)-based time-series analysis for specific metrics on your hosts. Each tracer creates and trains ML models that automatically detect deviations from a calculated normal state, which may indicate an attack.


Requirements

Training period

  • At least seven days of data are required so that an ML model can identify time-based patterns and detect anomalies based on them. We recommend a data basis of at least four weeks for reliable anomaly detection.

  • If the data horizon for your models is still shown as insufficient after several days, this may be due to a log-entry retention period (time to live; TTL) in the Enginsight component Loggernaut that is set too short. In this case, you must extend the TTL accordingly.


Important Notes

  • The metric defined in the Tracer is used to train the ML models for the assigned hosts. For this reason, once a Tracer has been created, you can only change its display name and the assigned hosts or host groups. If you want to monitor a different metric, you must add a new Tracer.

  • If the Tracer is deleted, all previously measured values that the associated ML model used to calculate the baseline and detect anomalies are also deleted. Training a new ML model with a new Tracer will again take at least seven days to establish a reliable data basis for the calculation.


Tracer: Menu Structure

Under Hosts → Tracer, you will find various options for setting up ML-based time series analyses for your hosts. This helps detect deviations from the normal value that may indicate an attack.

Click the Tracer menu item to expand or collapse the corresponding submenu.

The following submenu items are available:

Click and hold the Tracer menu item to move it, including all submenu items, within the menu tree using drag and drop.


Further Resources

Knowledge Base


Last updated

Was this helpful?