PhenixID server has two types of logs, events and server runtime information.

Events are typically well defined known messages meant to provide information on what happens in the system from a reporting perspective. System events are stored in the events.log file and in the reporting database, if enabled.

Event format used is the CEF, Common Event Format.  

Configuration manager shows the last 200 events. To get a full view of all events see the events.log file or use the reporting view in the configuration UI.

An event consists of an ID and a user-friendly description.

PhenixID server has two types of logs, events and server runtime information.

Events are typically well defined known messages meant to provide information on what happens in the system from a reporting perspective. System events are stored in the events.log file and in the reporting database, if enabled.

Event format used is the CEF, Common Event Format.  

Configuration manager shows the last 200 events. To get a full view of all events see the events.log file or use the reporting view in the configuration UI.

An event consists of an ID and a user-friendly description.

PhenixID server has two types of logs, events and server runtime information.

Events are typically well defined known messages meant to provide information on what happens in the system from a reporting perspective. System events are stored in the events.log file and in the reporting database, if enabled.

Event format used is the CEF, Common Event Format.  

Configuration manager shows the last 200 events. To get a full view of all events see the events.log file or use the reporting view in the configuration UI.

An event consists of an ID and a user-friendly description.

PhenixID server has two types of logs, events and server runtime information.

Events are typically well defined known messages meant to provide information on what happens in the system from a reporting perspective. System events are stored in the events.log file and in the reporting database, if enabled.

Event format used is the CEF, Common Event Format.  

Configuration manager shows the last 200 events. To get a full view of all events see the events.log file or use the reporting view in the configuration UI.

An event consists of an ID and a user-friendly description.

PhenixID server has two types of logs, events and server runtime information.

Events are typically well defined known messages meant to provide information on what happens in the system from a reporting perspective. System events are stored in the events.log file and in the reporting database, if enabled.

Event format used is the CEF, Common Event Format.  

Configuration manager shows the last 200 events. To get a full view of all events see the events.log file or use the reporting view in the configuration UI.

An event consists of an ID and a user-friendly description.

PhenixID server has two types of logs, events and server runtime information.

Events are typically well defined known messages meant to provide information on what happens in the system from a reporting perspective. System events are stored in the events.log file and in the reporting database, if enabled.

Event format used is the CEF, Common Event Format.  

Configuration manager shows the last 200 events. To get a full view of all events see the events.log file or use the reporting view in the configuration UI.

An event consists of an ID and a user-friendly description.

PhenixID server has two types of logs, events and server runtime information.

Events are typically well defined known messages meant to provide information on what happens in the system from a reporting perspective. System events are stored in the events.log file and in the reporting database, if enabled.

Event format used is the CEF, Common Event Format.  

Configuration manager shows the last 200 events. To get a full view of all events see the events.log file or use the reporting view in the configuration UI.

An event consists of an ID and a user-friendly description.