Frontend Server Disk Space Check

The PerformanceGuard frontend server automatically checks if there is enough disk space on the computer that runs the frontend server.

The frontend server will automatically stop accepting data from PerformanceGuard agents if there is less than 3000 MB (about 3 GB) free disk space on the drive where the frontend server stores agent data. It checks again every 10 seconds, and automatically resumes accepting data from agents as soon as there is 3000 MB or more free disk space.

Technically, when the frontend server stops accepting data from agents, the PerformanceGuard Frontend Server service itself does not stop, but it stops listening on the port that agents use to deliver data (by default TCP port 4001, see Installation).

Caution

If the frontend server stops accepting data from agents because of limited disk space, it is important that you free up sufficient disk space on the computer that runs the frontend server. When you have freed up sufficient disk space, the frontend server will automatically resume accepting data from agents.

How will I know if a frontend server stops accepting agent data?

Caution

You can only do this if you’re a PerformanceGuard administrator.

There are several indications.

Frontend server log

PerformanceGuard administrators can see it in the frontend server log file, available on the Log Files tab (see View Log Files) of the PerformanceGuard web interface or directly under [PerformanceGuard installation folder]\collector\logs.

• When the frontend server stops accepting data from agents, a warning like this is logged, with the number of megabytes left:

  Not enough disk space, only [number] MB left, waiting

• When the frontend server resumes accepting data from agents, this warning is logged:

  Disk no longer full, continuing

System Status reports WARNING or FAILURE

PerformanceGuard administrators can see it in the PerformanceGuard web interface: When the frontend server stops accepting data from agents, the Agents Online status on the System Status tab (ADMINISTRATION > Status > System Status) changes to WARNING and then to FAILURE, because agents no longer deliver data. See System Status.

Caution

If your organization uses multiple frontend servers, agents will automatically connect to another frontend server (see Manage Frontend Servers). When that’s the case, the Agents Online status will remain OK. In that case, select the neighboring Frontend Servers tab. Because the PerformanceGuard Frontend Server service has technically not stopped on the affected frontend server, it will still appear with an Online status. However, you’ll be able to recognize the affected frontend server, because it will have an Online Agents count of 0.

Use Server Surveillance Tool to get automatic notifications

PerformanceGuard has a separate downloadable tool for monitoring the status of the PerformanceGuard system and alerting you by e-mail if something is wrong. The tool can thus automatically notify you if a frontend server stops accepting data from agents. This requires that you download, configure and run the tool. The tool can also write PerformanceGuard status messages in the Windows event log.

Poll the system status automatically

You can monitor the status of your PerformanceGuard system from another system, and get notified if the status changes. See Automatically Poll System Status from External System in System Status.

Caution

In an environment with multiple frontend servers, agents automatically connect to another frontend server if their preferred frontend server stops accepting data. When that’s the case, the overall status of your PerformanceGuard system can remain OK, so neither the Server Surveillance Tool nor a status poll will notify you. Also check the status of each frontend server.