Verint Community supports application observability via traces, metrics and logs and makes this data available using the Open Telemetry (OTLP) protocol.
What data is available?
Logs
Data included via logs (using the EventLog API or .net's ILogger interface) is included in log data. Log data is categorized into levels of increasing severity: Trace, Debug, Information, Warning, Error, Critical. By default, Verint Community will write logs of the level Information or greater to the log output. Logging configuration is managed via the Logging section of environment configuration .
Traces
Traces identify application flow through the various entry points to Verint Community (web requests, job executions, etc). Each trace is a hierarchy of waypoints in the application flow used to complete the task requested by the entry point. Verint Community defines tracepoints throughout the application and 3rd party developers can add tracing data using the TracePoint API .
Because collecting traces of every request is data intensive, Verint Community provides filtering support so that only traces that include specific TracePoints or timing are included. By default, Verint Community will only collect traces that contain a logged exception or a SQL command that takes over 500ms.
The configuration for traces is managed via the Tracing section of environment configuration .
Metrics
Metrics are aggregates of data that can be viewed over time like either numerically or visually (as a graph or a meter/gauge). Verint Community includes metrics to view CPU usage/pressure, RAM usage/pressure, community system indicator health percentages, number of errors logged, HTTP request timing, and much more. The configuration of metrics is managed via the Metrics section of environment configuration .
How do I view this collected data?
All of the observability data can be written to the console for immediate viewing of local collection or to a visualizer using an Open Telemetry-compatible collector with an external observability tool. Log data can also be configured to write logs to the event log which can be viewed within the Administration interface of Verint Community.
Most external observability tools have some level of support for Open Telemetry (not all will support all three of the types of data made available by Verint Community). When hosting Verint Community with Verint, observability data is sent to Verint's monitoring system for constant review and issue inspection. When self-hosting, it is recommended to use an Open Telemetry-compatible tool to view monitoring data. In the development compose stack, Microsoft Aspire Dashboard is included and is pre-configured to enable observability during development.
The configuration of the shipping of Open Telemetry data to an Open Telemetry-supporting collector via the OTLP protocol is managed via the Logging, Tracing, Metrics, Open Telemetry Tags, and Open Telemetry Resource Tags sections of environment configuration .