Top.Mail.Ru
Storing Monitoring Agent Logs
CTRL+K

Storing Monitoring Agent Logs

In this article
  • Storing Monitoring Agent Logs
  • Monitoring Agent Log Locations on Windows
  • Monitoring Agent Log Locations on Linux

Monitoring Agent Log Locations on Windows

Below is a list of directories containing the monitoring agent logs on Windows operating system.

  • Located at ProgramData\OperavixAgent:
    • data — saves agent service archives when the server is unavailable
    • dumps — stores the data when the agent crashes
    • logs — agent service logs in service.log
    • username@domain.com — stores the file with a path to the agent logs in AppData
    • settings.cfg file — stores information about the server address, proxy server settings, and agent auto-update
  • Located at AppData\Local\Temp\OperavixAgent: logs:
    • configurator.log — stores agent configuration logs, for example, errors
    • installer.log — stores agent installation logs, information about updates, etc.
  • Located at AppData\Roaming\OperavixAgent: logs:
    • sessionInspector.log — a file with agent logs: information about the agent version, loaded modules, sent archives, errors while sending requests, etc. When the file reaches the size of 1 MB, it is renamed to sessionInspector.1.log, then to .2.log etc. New logs are written to the file without a digit. In total, logs are stored up to 10 digits, then get deleted
    • timeTracker.log — a file with Time Tracking module logs
    • reservedSpace — a file for improving data collection, in case AppData is overloaded (the file size is 10 MB). When there is not enough space, the file gets smaller. When the space is freed up, the file restores its original size
    • settings.cfg — a file with information about the monitoring agent type, Time Tracking module activity and logging level. By default, the logging level is LEVEL_ERROR

Monitoring Agent Log Locations on Linux

Below is a list of directories containing the monitoring agent logs on Linux-based operating systems.

  • Located at /var/lib/OperavixAgent:
    • data — directory containing agent service archives saved when the server is unreachable
    • dumps — directory containing crash dump files from the monitoring agent
    • logs — directory containing the agent service logs in service.log
    • username@domain.com — file containing the path to the agent directory within the user's home folder
    • settings.cfg — configuration file containing server address, proxy settings, and agent auto-update options
  • Located at /home/<USER>/.OperavixAgent:
    • settings.cfg — configuration file containing agent monitoring type and logging level. By default, the logging level is set to LEVEL_ERROR
    • SessionInspectorInstance.pid — file containing the process identifier (PID) under which the agent is running
    • reservedSpace — placeholder file used to maintain data collection during low disk space conditions. This file is removed when space is critically low to free up storage for essential operations
    • logs directory:
      • sessionInspector.log — primary agent log file containing information about agent version, loaded modules, transmitted archives, request errors, etc. When this file reaches 1 MB in size, it is renamed to sessionInspector.1.log, then to .2.log, and so on. New entries are written to the file without a number. Log files are retained up to sessionInspector.10.log; older files are automatically deleted

Was the article helpful?

Yes
No
Previous
User Data Logging
We use cookies to improve our website for you.