List of log files maintained by Site24x7 server monitoring agent

List of log files generated and maintained by the Site24x7 server monitoring agent

Here is the list of log files generated by the Linux and Windows server monitoring agent. The log files are stored in the same directory where the agent source file is installed. By default they are at:

For Linux :
<Installation_Directory>/site24x7/monagent/logs

For Windows :
<Installation_Directory>/Site24x7/WinAgent/Monitoring/Logs

Legend

File name : The name of the log file and the path where it is stored.
Description : A brief description of the log file.
No. of files maintained : The maximum number of log files in this category that will be stored.
Total file size : The maximum size of log file in this category that will be stored. For example, 10 * 1MB means the path will contain 10 files of that particular log, with a size of 1MB each.

Once the maximum file size is reached, the oldest log file is deleted to make space for the newest log file.
 


Linux

 S.No

File n ame

Description

No. of files maintained

Maximum file size

1

logs/main.txt

Primary logs about agent registration and communications

10

10 * 1MB

2

logs/metrics.txt

Logs related to Prometheus and StatsD

10

10 * 2MB

3

logs/critical.txt

Logs classified as critical in a server monitor

10

10 * 1MB

4

logs/apps.txt

Logs related to server applications

10

10 * 1MB

5

logs/database.txt

Logs related to the database application

10

10 * 1MB

6

logs/query.txt

Logs related to database query-based data collection

10

10 * 1MB

7

logs/da.txt

Logs related to a Docker agent

10

10 * 1MB

9

logs/framework.txt

Logs related to Hadoop monitoring

10

10 * 1MB

10

logs/hardware.txt

Logs related to hardware monitoring

10

10 * 1MB

11

logs/kubernetes.txt

Logs related to Kubernetes monitoring

10

10 * 1MB

12

logs/details/collector.txt

Logs related to data collection in a server monitor

7

7 * 4MB

13

logs/details/stdout.txt

Logs related to data archiving and uploads

2

2 * 4MB

14

logs/details/stderr.txt

Exception log

3

3 * 2MB

15

logs/details/checks

Logs related to resource checks

3

3 * 4MB

16

logs/details/plugins

Logs related to plugins

3

3 * 4MB

17

logs/details/ping

Logs related to ping communications

1

1 * 2MB

18

logs/details/udp

Logs related to yslog monitoring

2

2 * 2MB

19

logs/details/udp_raw

Logs of raw syslog data

2

2 * 2MB

20

logs/details/udp_filtered

Logs of filtered syslog data

2

2 * 2MB

21

logs/details/deployment

Logs of script and plugin deployments

4

4 * 1MB

22

logs/applog/application.log

Logs related to the Applog application

10

10 * 10MB

23

logs/applog/stderr.log

Logs related to Applog errors

10

10 * 10MB

24

logs/applog/stdout.log

Logs related to Applog output data

10

10 * 10MB

25

logs/applog/dms.log

Logs related to Applog dms information

10

10 * 10MB

26

logs/applog/objstats.log

Debug logs related to Applog file reads (Only initialization will enable logs when needed)

10

10 * 10MB

27

logs/applog/readstat.log

Debug logs related to Applog files processed (Only initialization will enable logs when needed)

10

10 * 10MB


Windows

 S.No

File name

Description

No of files maintained

Total file size

1

logs\site24x7agentlog.log

Primary log related to server monitoring

10

10*1MB

2

logs\Cloudlog.txt

Log related to check ing whether the machine is a cloud VM or not

1

1MB

3

logs\agenthelper.log

Log related to the agent watcher process

10

10*1MB

4

logs\BulkInstall.log

Log related to agent remote install from the machine to a remote host

1

10MB

5

logs\AgentMsiInstall.txt

Logs related to agent installation during upgrade

1

2MB

6

logs\AgentMsiUninstall.txt

Log related to agent uninstallation during upgrade

1

2MB

7

logs\agentupgrade.log

Log related to agent upgrade

1

2MB

8

logs\PriorUpgrade.log

Log related to pre-upgrade verification

1

2MB

9

logs\Details\Access.log

Log related to agent communication

10

10*1MB

10

logs\Details\agent.log

Log related to the server monitoring agent and all communications

40

40*1MB

11

logs\Details\agenthelperbackup.log

Backup log related to the agent watcher process

1

10MB

12

logs\Details\AppsLog.txt

Log related to the Windows application monitor

10

10*1MB

13

logs\Details\PluginLog.log

Log related to plugin data collection

10

10*1MB

14

logs\Details\PluginRegisterLog.log

Log related to plugin registration

10

10*1MB

15

logs\Details\WinCommunicator.log

Log related to the Site24x7 communicator

10

10*1MB

16

logs/applog/application.log

Logs related to the Applog application

10

10 * 10MB

17

logs/applog/stderr.log

Logs related to A ppLog errors

10

10 * 10MB

18

logs/applog/stdout.log

Logs related to Applog output data

10

10 * 10MB

19

logs/applog/dms.log

Logs related to Applog dms information

10

10 * 10MB



    • Related Articles

    • Troubleshooting false positive alerts in monitoring

      Problem False positive alerts are being generated. Possible cause The monitoring system is down in some locations. The Website monitor might be configured for one location, such as Seattle, but may appear down when accessed from another location, ...
    • Exclude the selective SSH algorithms in On-Premise Poller during SFTP Transfer monitoring

      By excluding SSH algorithms, you can restrict Site24x7 SSH Client from using the excluded algorithm while connecting to the SSH server during SFTP Transfer monitoring. Follow the steps mentioned below for SSH algorithm exclusion in On-Premise Poller ...
    • How do I monitor an Oracle database hosted in a Docker container in the same machine?

      To monitor your Oracle Database hosted in a Docker container, follow these steps: Log in to Site24x7 and install the Site24x7 Linux monitoring agent. Execute the following command in your terminal and enter your Oracle Database instance's username ...
    • Exclude Site24x7 monitoring traffic from Google Analytics

      You can exclude traffic from the Site24x7 Web Transaction (Browser) monitor and Webpage Speed (Browser) traffic from Google Analytics in two ways. To exclude traffic for the Web Defacement monitor, you can follow the first method. 1. Creating a ...
    • Response time in Website monitoring

      In website monitoring, response time is calculated as the total time taken to resolve the DNS, complete the TCP hand-shake, negotiate an SSL handshake (for HTTPS) and download the full HTML output from the server. However, it does not include getting ...