Logs and Statistics

Logs

To monitor the OvenMediaEngine, you can view in real-time the log files generated by itself. You can configure a log type and level by creating the Logger.xml configuration file in the same location as Server.xml.

You can set up Logger.xml as shown in the following example: OvenMediaEngine prints logs separated by many tag names and levels. Set <Tag name=".*" level="debug"> to have OvenMediaEngine print all logs and read the logs. And then it's better to disable tags that you don't need.

<Logger version="2">
	<!-- Log file location -->
	<Path>/var/log/ovenmediaengine</Path>

	<!-- Disable some SRT internal logs -->
	<Tag name="SRT" level="critical" />
	<Tag name="Monitor" level="critical" />

	<!-- Log level: [debug, info, warn, error, critical] -->
	<Tag name=".*" level="info" />
</Logger>

OvenMediaEngine generates log files. If you start OvenMediaEngine by systemctl start ovenmediaengine, the log file is generated to the following path.

/var/log/ovenmediaengine

If you run it directly from the command line, it will be generated to the following location:

If you run it in the Docker container, the log file is in the following path:

Following is the example of real logs.

Statistics

OvenMediaEngine collects the following metrics for each host, application, and stream.

  • Bytes in/out by protocol

  • Connections by protocol

  • Maximum connections and time

  • Time is taken to connect to origin

You can get the current statistics using the REST API. See Stat API for the statistics REST API.

Files such as webrtc_stat.log and hls_rtsp_xxxx.log that were previously output are deprecated in the current version. We are developing a formal stats file, which will be open in the future.

Was this helpful?