Server Monitoring

Server monitoring provides visibility to your server enabling the ability to monitor application availability. Specifically, server monitoring enables you to:

• Monitor system resources and alert on service status
• Inventory system information and hardware components

Server Monitoring supports servers running Windows Server 2016 and newer.

Using Server Monitoring:

• Getting Started with Server Monitoring
• Alerting on Servers
• System Information
• Resource Usage and Windows Services
• Server Inventory

Getting Started with Server Monitoring

To get started, log into the Auvik platform and

• Have the Auvik Collector deployed where it can reach the server, and
• Have the Auvik Endpoint Agent installed on the server.

Servers will be registered to a site and are accessible within the Inventory menu, under All Servers. From this list you can select the server you want to investigate by selecting the device’s name.

Server Monitoring Features

Alerting on Servers

Proactively detect incidents such as 

• Named services are no longer running
• Server is offline
• CPU utilization exceeds a threshold
• Memory utilization exceeds a threshold
• Drive (disk partition) capacity falls below a threshold

To reduce your Mean-Time-To-Resolution (MTTR), you can create your own alerts using the following triggers:

• Service State
• Service Name
• Service Display Name
• Service Start Type
• Service Started
• Online Status
• CPU Utilization
• Memory Utilization
• Disk Partition Utilization

Server monitoring leverages alerting 2.0, so you’ll get the ability to build alerts with complex trigger conditions, access to more suppression options and better notifications. Note: Operational Status is available based on Collector data. To alert on a Windows Service state:

1. Navigate to Manage Alerts >New Alerts.
2. Click Add Alert.
3. Fill in the Alert Name
4. Fill in the Alert Description.
5. Set Apply Conditions dropdown to Windows Services on a device.
6. For Which devices?, there are two options:
   • Create a new tag or use an existing one. If more than one server alert will be created, it is better to create a tag. To create a new tag:
     1. Select Devices with this tag.
     2. Select Create New Tag.
     3. Provide a Tag name.
     4. Add a rule where Device Model contains Windows Server.
   • Manually set the devices.
     1. Select Devices that match these conditions.
     2. Add a rule where Device Model contains Windows Server.
7. Set the Alert Severity.
8. Define the Trigger Conditions.
   • Add a rule for Windows Services State not equal to RUNNING if you want to alert on when the service is no longer running.
   • Add a rule for Windows Services Name equal to the name of the Windows Service that you want to alert on.
   • Some items to consider when you set the trigger condition.
     Using Windows Services Name is better than Windows Services Display Name because Windows Services Name is the unique identifier for Windows Services and it is independent of the OS language set on the server.
9. Enter a Trigger message.
   • Type $ to see the list of available variables.
10. Set the Alert delay.
    • Leverage this to avoid alerting on services that recover on their own.
11. Add Notifications.
    • If you are adding email notification channels, set the Email delivery delay.
12. Define the Clear conditions
    1. Use Custom Clear Condition
    2. Add a rule for Windows Services State equal to RUNNING (assuming it was set to not equal to RUNNING in the trigger condition).
    3. Add a rule for Windows Services Name equal to the service name in the trigger condition.
13. Define the Clear message.
14. Click Complete and Save.

Refer to Creating Alerts using Alerting 2.0 to get started.

System Information

Leverage system information on the Server dashboard to understand the server environment to facilitate initial troubleshooting.

• Hostname
• Make & Model
• Serial Number
• OS
• Processor
• Memory 
• Disk(s)
• Graphics Card(s)
• IP Address(es)
• MAC Address(es)
• BIOS/UEFI
• TPM
• Chassis
• Online Status
• Installed Software

Resource Usage and Window Services

CPU utilization, memory utilization, disk partition utilization and state of Windows Services on the Server dashboard enables you to quickly spot check issues with server resources for initial troubleshooting.

• Disk utilization can be expanded to view partition information, which is more helpful for application troubleshooting.
• Detailed information about each Windows Service is available for analysis.

CPU and memory utilization history enables you to detect longer term capacity issues such as memory leaks and increased load. Use the time range filter to evaluate the period of interest.

Server Inventory

A list of all registered servers are displayed in All Servers in the Inventory menu. You can see the status of the servers at a glance, spot any servers running outdated OS versions, or navigate to see more detailed information about a specific server.

Software Inventory

Auvik now automatically collects and displays a full inventory of software installed on each monitored server. This includes:

• Application name
• Vendor
• Version number
• Install date

Software inventory is updated regularly, ensuring you always have an up-to-date view of what’s installed on each server. This is especially useful for:

• Security audits
• Software compliance
• Troubleshooting software-related issues