Export - Capacity Planner - Server

Host Template: Export - Capacity Planner - Server

Monitor your physical server with the required information for Standard Capacity Reports, including CPU and Memory capacity and utilization, hardware details, and filesystem information. Works with both supported Linux and Windows systems.

This Host Template includes the following Service Checks:

Service Check Name	Description	Check Interval
Cap Plan Export - Server - Specification	The number of physical and logical cores, the average CPU clock speed (MHz) and the memory capacity (B) of the server. NOTE: Visual check output units for memory capacity will match the implementation of `free -h` on the monitored system.	1 day
Cap Plan Export - Server - Utilization	The current CPU utilization (%) and memory utilization (%) of the server.	5 mins
Cap Plan Export - Filesystem - Capacity	The total storage capacity (B) of all filesystems on the server. Supports exclusion of specific filesystem types or mount points. NOTE: Visual check output units will match the implementation of `df -h` on the monitored system.	1 day
Cap Plan Export - Filesystem - Utilization	The current storage utilization (%) of all filesystems on the server. Supports exclusion of specific filesystem types or mount points.	5 mins
Cap Plan Export - Tag	Allows attaching custom tags to the exported data to categorise servers.	1 day

Usage Instructions

Step 1: Add the Host Template

Add the Add the Export - Capacity Planner - Server Host Template to your Opsview Monitor host. Host Template to your Opsview Monitor host.

For more information, refer to Opsview Knowledge Center - Adding Host Templates to Hosts.

Step 2: Add Variables if appropriate

The following variables can be used to configure communication with the Agent (see Agent Security):

NRPE_CERTIFICATES
NRPE_CIPHERS
NRPE_EXTRA_ARGS

The following variables will be added to your Opsview Monitor instance when you import the Opspack.

CAPACITY_PLANNER_EXCLUDE

The "Cap Plan Export - Filesystem - Capacity" and "Cap Plan Export - Filesystem - Utilization" Service Checks can use the following variable to exclude filesystems from being exported:

Position in Variable	Name	Description	Default
Arg1	Filesystems to exclude	Comma-separated list of filesystem types to exclude from being exported.	tmpfs,devtmpfs,squashfs,CDRom
Arg2	Mountpoints to exclude	Comma-separated list of mountpoints whose linked filesystems will not be exported. Supports regex expressions.	N/A

CAPACITY_PLANNER_TAG

The "Cap Plan Export - Tag" Service Check will be added to the Host once for each instance of the following Variable, which will then attach the Tag Name and Tag Value as a key-value pair to the exported server details:

Position in Variable	Name	Description	Default
Value	Tag Name	The name of the tag to be applied to the exported server e.g. "Location".	N/A
Arg1	Tag Value	The value of the tag to be applied to the exported server e.g. "New York". Limited to 1000 characters.	N/A

Each Tag added will be listed as a separate Service Check:

Step 3: Apply changes and the system will be monitored

NOTE: If Checks report an UNKNOWN state, the output will indicate that the integration with Standard Capacity Reports for the respective monitored physical server is broken, as this data is required for capacity reports to generate. The "Cap Plan Export - Tag" Service Check is an exception, and will report that the integration is impacted, as this data is not required for Standard Capacity Reports to work, but not having it available will decrease the efficacy of the reports.

Known Issues

If using RRD as a timeseries provider, then the "Cap Plan Export - Server - Specification" and "Cap Plan Export - Filesystem - Capacity" Service Checks will display no data in their timeseries graphs. However, the Standard Capacity Reports will still work as expected.
If a monitored server uses a filesystem with subvolumes e.g. btrfs, then each filesystem may be duplicated in Standard Capacity Reports as <filesystem name>, <filesystem name>2, <filesystem name>3 etc. for each subvolume using it.