- Welcome to Exabeam Security Content
- What is Security Content?
- Common Information Model
- What is the Common Information Model?
- Common Information Model Context Elements
- Common Information Model Interface
- Common Information Model Event-naming Format
- Common Information Model Impact on Downstream Processes
- Using the Common Information Model to Create Custom Content
- Transitioning to the Common Information Model
- Understanding the Log
- Exabeam Parsers
- Exabeam Event Building
- Exabeam Enrichment
- Exabeam Persistence and Templates
- Exabeam Models
- Exabeam Rules
PrevNext
Restart Services for Persistence and Templates
If you make any updates for persistence and you want to see if a new field values persisted on MongoDB, the analytics engine must be restarted (
exabeam-analytics-stop;exabeam-analytics-start
).If you make any updates to event templates and you want to see the changes in the UI, the web components must be restarted (
web-stop;web-start
).If you make updates for persistence and want them displayed in the UI, and you also update event templates, both the analytics engine and the web components must be restarted.
Note
In order for a field to be displayed in a UI by using an event template, the field must be persisted.