stream_coverage i status-API.
This commit is contained in:
@@ -68,6 +68,11 @@ checkboxes decide which streams are monitored. Click `Edit profile` on one strea
|
||||
to load its fields and edit only that stream's profile; saving with no active
|
||||
profile editor leaves existing profiles unchanged.
|
||||
|
||||
When many Graylog streams are available, use `Diagnostics -> Stream Coverage` to
|
||||
see which streams are enabled, which have profiles, how many profile fields are
|
||||
baseline-ready, how many events were fetched, and whether a stream is `ready`,
|
||||
`learning`, `missing_profile`, `no_events`, or `not_enabled`.
|
||||
|
||||
Enabled streams are normalized through the same event model. Stream profiles
|
||||
define the entity, timestamp, categorical, and numeric fields used for baselines.
|
||||
The dashboard and Ollama then correlate behavior across sources, for example a
|
||||
|
||||
Reference in New Issue
Block a user