About Profiles

Overview

This page categorizes the GroundWork distributed profiles and provides links to available documentation.

CONTENTS

RELATED RESOURCES

WAS THIS PAGE HELPFUL?

1.0 About GroundWork Monitor Profiles

GroundWork Monitor distributes the Service Ping, SNMP Network, and SSH UNIX profiles plus an extended library of monitoring profiles for a variety of devices, systems and applications, listed below. The Configuration tool is used to import additional profiles; the profile XML file and its companion Performance Configuration definition file, How to import profiles. For each Profile, graphs may be defined to track measurement values in certain services. The Uploaded category is provided as a landing zone for profile files uploaded to the GroundWork server by a local administrator. Distributed profiles are located in the /usr/local/groundwork/core/profiles/ directory within their respective principal category classifications as their parent directories. These are noted at the top of each section.

2.0 Distributed Profiles

2.1 Database

These profiles relate to the monitoring of various databases. The principal category classification and parent directory for these profiles is Database.

2.2 GDMA

These profiles relate to the deployment and monitoring of GroundWork Distributed Monitoring Agents. Click GDMA Profiles to view GDMA profiles with service detail. See GDMA Advanced for Windows PowerShell reference.

Also see in section 2.3 Citrix Product Monitoring, and 2.4 Hitachi Storage Platform Monitoring Profiles. The principal category classification and parent directory for these profiles is GDMA.

  • gdma-21-linux-host.xml   --   Linux base OS GDMA host profile
  • gdma-21-windows-host.xml   --   Windows base OS GDMA host profile
  • gdma-22-windows-host.xml   --   Windows PowerShell GDMA host profile
  • gdma-aix-host.xml   --   GDMA-monitored AIX host
  • gdma-autohost.xml   --   Virtual host for collection and processing of GDMA Auto-configuration messages
  • gdma-linux-host.xml   --   GDMA-monitored Linux host
  • gdma-solaris-host.xml   --   GDMA-monitored Solaris host
  • gdma-windows-host.xml   --   GDMA-monitored Windows host
  • service-profile-gdma-21-linux.xml   --   Base OS service profile for Linux host GDMA checks
  • service-profile-gdma-21-windows.xml   --   GDMA Windows Server (via WMI)
  • service-profile-gdma-23-aix.xml   --   Base OS service profile for AIX host GDMA checks
  • service-profile-gdma-23-exch-cas.xml   --   Exchange Client Access Server Role Services
  • service-profile-gdma-23-exch-mbox.xml   --   Exchange Mailbox Role Services
  • service-profile-gdma-23-exch-std.xml   --   Exchange Standard Checks for All Roles
  • service-profile-gdma-23-exch-trans.xml   --   Exchange Hub Transport Role Services
  • service-profile-gdma-23-linux.xml   --   Base OS service profile for Linux host GDMA checks
  • service-profile-gdma-23-solaris.xml   --   Base OS service profile for Solaris host GDMA checks
  • service-profile-gdma-23-windows.xml   --   Base OS service profile for Windows host GDMA checks
  • service-profile-gdma-mssql2008.xml   --   Group of all GroundWork services for MSSQL 2008 monitoring via GDMA.
  • service-profile-gdma-win-disk.xml   --   Windows Disk Performance Metrics
  • service-profile-gdma_auto.xml   --   Service definition for the collection of GDMA auto-configuration data
  • service-profile-windows-child-target.xml   --   Windows host monitored by Windows Child Server
  • service-profile-windows-child.xml   --   Windows Child Server
  • windows-child-target.xml   --   Profile for creating a target of a windows child system
  • windows-child.xml   --   Host profile for creating windows child host object

2.3 Citrix (GDMA Monitoring)

New to GroundWork Monitor as of the GWMEE 7.0.1 release, these profiles are used to support GDMA monitoring of Citrix XenApp and XenDesktop. These profiles reference a variety of VBS and PowerShell scripts that we already include in our Windows GDMA release. The principal category classification and parent directory for these profiles is Citrix. For additional information see the Operations Guide.

  • host-profile-citrix-xenapp.xml   --   GDMA based monitoring profile for all in one Citrix XenApp
  • host-profile-citrix-xendesk.xml   --   GDMA based monitoring profile for all in one Citrix XenDesk
  • service-profile-citrix-licensing-services.xml   --   Service profile for Citrix Licensing Server
  • service-profile-citrix-provisioning-services.xml   --   Service profile for Citrix Provisioning Server
  • service-profile-citrix-system.xml   --   Base OS service profile for Citrix Servers
  • service-profile-citrix-xenapp-extra-services.xml   --   Service profile for Citrix XenApp Server Extra Services
  • service-profile-citrix-xenapp-services.xml   --   Service profile for Citrix XenApp Server
  • service-profile-citrix-xendesk-services.xml   --   Service profile for Citrix XenDesk Server

2.4 SAP HANA

New to GroundWork Monitor as of the GWMEE 7.2.1 release and available to GroundWork customers. See https://www.sap.com/products/hana.html.

See SAP HANA for profile documentation.

  • service-profile-sap-hana-sp-replication.xml
  • service-profile-sap-hana-sp-multitenant-replication.xml
  • service-profile-sap-hana-sp-multitenant.xml
  • service-profile-sap-hana-sp.xml

2.5 Hitachi (GDMA Monitoring)

New to GroundWork Monitor as of the GWMEE 7.0.1 release, these profiles are used to support GDMA monitoring of the respective Hitachi storage platforms. These profiles reference two distinct Windows binaries, check_HDvM.exe and check_HTnM.exe, which are not currently provided in our GDMA releases. The principal category classification and parent directory for these profiles is Storage. Additionally, see Hitachi Profiles.

  • service-profile-Hitachi-AMS.xml   --   Standard selection of services for an Hitachi AMS
  • service-profile-Hitachi-USPV.xml   --   Standard selection of services for an Hitachi USPV
  • service-profile-Hitachi-VSP.xml   --   Standard selection of services for an Hitachi VSP
2.6 Linux-UNIX

These profiles relate to monitoring of machines running UNIX-like operating systems (Linux, Solaris, AIX, HP-UX). The principal category classification and parent directory for these profiles is Linux-UNIX.

2.7 Messaging

These profiles relate to the monitoring of mail and other messaging channels (Network News, Internet Relay Chat, etc.). The principal category classification and parent directory for these profiles is Messaging.

2.8 Miscellaneous

These profiles serve a variety of monitoring functions that don't seem to fit into any of the other broad categories. The Syslog Profile includes the service checks necessary to process incoming syslog messages from remote servers within GroundWork Monitor. The principal category classification and parent directory for these profiles is Miscellaneous.

  • service-profile-group_status_checks.xml   --   A simple template profile for using the check_hostgroup_foundation.pl plugin
  • service-profile-ssh-nmon.xml   --   NMON service profile
  • service-profile-syslog.xml   --   syslog receiver
  • service-profile-LogLogic_Server_Checks.xml   --  LogLogic Server checks
2.9 Network

These profiles relate to the monitoring of various network-related entities, capabilities, and protocols. Some monitoring in GroundWork Monitor is done without the use of installed agents, or at least agents installed as part of GroundWork Monitor. Profiles in this category communicate with monitored servers over the network using common protocols such as ICMP, TCP, and in the case of Oracle, the SQL protocol is used. The principal category classification and parent directory for these profiles is Network.

2.10 Network Security Appliances

New to GroundWork Monitor as of the GWMEE 7.0.1 release. These profiles relate to the monitoring of network security devices, including Cisco, Blue Coat, Check Point, Juniper, and others. The principal category classification and parent directory for these profiles is Network-Security-Appliances. Additionally, plugins which support the new Network-Security-Appliances category of profiles are listed below.

  • service-profile-Aventail_SSL_VPN_Checks.xml   --   Dell SonicWALL Aventail Connect SSL VPN checks
  • service-profile-Avocent_KVM_Checks.xml   --   Avocent KVM checks
  • service-profile-Blue_Coat_AAA_Checks.xml   --   Blue Coat Authentication and Authorization Agent checks
  • service-profile-Blue_Coat_AV_Checks.xml   --   Blue Coat Anti-Virus checks
  • service-profile-Blue_Coat_Director_Checks.xml   --   Blue Coat Director checks
  • service-profile-Blue_Coat_Proxy_Checks.xml   --   Blue Coat Proxy checks
  • service-profile-Blue_Coat_Reporter.xml   --   Blue Coat Reporter checks
  • service-profile-CheckPoint_NFR_IDS_Checks.xml   --   Check Point NFR Intrusion Detection System checks
  • service-profile-CheckPoint_Nokia_FW_Checks.xml   --   Check Point Nokia Firewall checks
  • service-profile-CheckPoint_Provider-1_CMA_Checks.xml   --   Check Point Provider-1 Customer Management Add-On checks
  • service-profile-CheckPoint_Provider-1_MDS_Checks.xml   --   Check Point Provider-1 Multi-Domain Security Management checks
  • service-profile-CheckPoint_SPLAT_FW_Checks.xml   --   Check Point Secure Platform Firewall checks
  • service-profile-CheckPoint_SmartCenter_Checks.xml   --   Check Point SmartCenter checks
  • service-profile-CheckPoint_UTM-1_Edge_FW_Checks.xml   --   Check Point UTM-1 Edge Firewall checks
  • service-profile-Cisco_ACE_Load_Balancer_Checks.xml   --   Cisco Application Control Engine Load Balancer checks
  • service-profile-Cisco_ACS_Checks.xml   --   Cisco Access Control Server checks
  • service-profile-Cisco_CSS_Load_Balancer_Checks.xml   --   Cisco Content Services Switch Load Balancer checks
  • service-profile-Cisco_FW_ASA5580_Environmental_Checks.xml   --   Cisco Adaptive Security Appliance 5580 Environmental checks
  • service-profile-Cisco_FW_Checks.xml   --   Cisco Firewall checks
  • service-profile-Cisco_FW_Client_VPN_Checks.xml   --   Cisco Firewall Client VPN checks
  • service-profile-Cisco_IDPS_Checks.xml   --   Cisco Intrusion Detection and Prevention System checks
  • service-profile-Cisco_IronPort_Checks.xml   --   Cisco IronPort checks
  • service-profile-Cisco_MARS_Checks.xml   --   Cisco Security Monitoring, Analysis, and Response System checks
  • service-profile-Cisco_Security_Manager_CSM_Checks.xml   --   Cisco Security Manager checks
  • service-profile-Cisco_VPN_3000_Concentrator_Checks.xml   --   Cisco VPN 3000 Concentrator checks
  • service-profile-Crossbeam_C-Series_Firewall_Checks.xml   --   Crossbeam C-Series Firewall checks
  • service-profile-Crossbeam_X-Series_APM_Checks.xml   --   Crossbeam X-Series Application Processor Modules checks
  • service-profile-Crossbeam_X-Series_CPM_Backup_Checks.xml   --   Crossbeam X-Series Control Procesor Modules Backup checks
  • service-profile-Crossbeam_X-Series_CPM_Primary_Checks.xml   --   Crossbeam X-Series Control Processor Modules Primary checks
  • service-profile-Crossbeam_X-Series_NPM_Checks.xml   --   Crossbeam X-Series Network Processor Modules checks
  • service-profile-F5_Edge_Gateway_Checks.xml   --   F5 Edge Gateway checks
  • service-profile-F5_Enterprise_Manager_Checks.xml   --   F5 Enterprise Manager checks
  • service-profile-F5_FirePass_Checks.xml   --   F5 FirePass checks
  • service-profile-F5_Load_Balancer_Checks.xml   --   F5 Load Balancer checks
  • service-profile-FortiGate_FW_Checks.xml   --   Fortinet FortiGate Firewall checks
  • service-profile-FortiManager_Checks.xml   --   Fortinet FortiManager checks
  • service-profile-Gigamon_TAP_Checks.xml   --   Gigamon Network Test Access Point checks
  • service-profile-HP_BladeSystem_OA_Checks.xml   --   HP BladeSystem Onboard Administrator checks
  • service-profile-HP_iLO_Checks.xml   --   HP Integrated Lights-Out checks
  • service-profile-IBM_DataPower_XML_Checks.xml   --   IBM DataPower XML checks
  • service-profile-IBM_Proventia_Checks.xml   --   IBM Proventia checks
  • service-profile-ICMP_Only_Checks.xml   --   ICMP-only checks
  • service-profile-IDS_Switch_Checks.xml   --   Intrusion Detection System Switch checks
  • service-profile-Infoblox_Checks.xml   --   Infoblox checks
  • service-profile-Juniper_DX_Load_Balancer_Checks.xml   --   Juniper DX Load Balancer checks
  • service-profile-Juniper_FW_Checks.xml   --   Juniper Firewall checks
  • service-profile-Juniper_IVE_SSL_Checks.xml   --   Juniper Instant Virtual Extranet SSL checks
  • service-profile-Juniper_SRX_Checks.xml   --   Juniper SRX checks
  • service-profile-Mazu_Profiler_Checks.xml   --   Mazu Profiler checks
  • service-profile-McAfee_IntruShield_IPS_Checks.xml   --   McAfee IntruShield Intrusion Prevention Solution checks
  • service-profile-NIKSUN_IDS_Checks.xml   --   NIKSUN Intrusion Detection System checks
  • service-profile-NetApp_NetCache_Checks.xml   --   NetApp NetCache checks
  • service-profile-NetScaler_Load_Balancer_Checks.xml   --   NetScaler Load Balancer checks
  • service-profile-Network_Critical_TAP_Checks.xml   --   Network Critical Network Test Access Point checks
  • service-profile-Nortel_VPN_Checks.xml   --   Nortel VPN checks
  • service-profile-Palo_Alto_FW_Checks.xml   --   Palo Alto Networks Firewall checks
  • service-profile-Sidewinder_Proxy_Checks.xml   --   Sidewinder Proxy checks
  • service-profile-Snort_IDS_SSH_Checks.xml   --   Snort Intrusion Detection System SSH checks
2.11 Network Security Appliances Plugins

GroundWork Monitor includes new plugins in the product to support the new Network-Security-Appliances category of profiles. At this time, you will need to invoke the plugin from the /usr/local/groundwork/nagios/libexec directory for available usage options.

# check_cisco_ironport_snmp.pl
check_cisco_ironport_snmp.pl:  The '-c' option is missing or incorrect.
Valid options are (? == optional, ! == boolean):
           -c  => Community string
           -h  => Hostname
           -i  => IP address
           -l? => Levels [warning:critical]
           -t  => Type of check
                  -> cpu
                  -> int_list
                  -> license
                  -> mail
                  -> mem
                  -> sensors
                  -> uptime
                  -> version
           -v  => SNMP version [1 or 2c]
  • check_aventail_snmp.pl
  • check_bluecoat_director_snmp.pl
  • check_bluecoat_https.pl
  • check_bluecoat_snmp.pl
  • check_cisco_ace_snmp.pl
  • check_cisco_acs_snmp.pl
  • check_cisco_css_snmp.pl
  • check_cisco_fw_snmp.pl
  • check_cisco_fw_ssh.pl
  • check_cisco_idps_https.pl
  • check_cisco_idps_snmp.pl
  • check_cisco_ironport_snmp.pl
  • check_cisco_vpn3000_snmp.pl
  • check_datapower_snmp.pl
  • check_f5_firepass_snmp.pl
  • check_f5_snmp.pl
  • check_fortigate_snmp.pl
  • check_hp_ilo_xml.pl
  • check_hpblade_snmp.pl
  • check_infoblox_snmp.pl
  • check_juniper_dx_snmp.pl
  • check_juniper_fw_snmp.pl
  • check_juniper_ive_snmp.pl
  • check_juniper_srx_snmp.pl
  • check_linux_snmp.pl
  • check_linux_ssh.pl
  • check_loglogic_snmp.pl
  • check_loglogic_ssh.pl
  • check_mcafee_intrushield_snmp.pl
  • check_nagios_stats.pl
  • check_netcache_snmp.pl
  • check_networkcritical_snmp.pl
  • check_nokia_ipso_snmp.pl
  • check_nortel_vpn_snmp.pl
  • check_paloalto_snmp.pl
  • check_ping.pl
  • check_snmp.pl
  • check_splat_snmp.pl
  • check_splat_ssh.pl
  • check_ssh.pl
  • check_ssl.pl
  • check_utm1edge_snmp.pl
  • check_windows_snmp.pl
  • get_snmp_interfaces.pl
  • interface_debug.pl
  • notify.pl
  • notify_wrapper.pl
2.12 Self-Check

These profiles relate to monitoring of the monitoring system itself, on either the local server or a supporting remote server. The principal category classification and parent directory for these profiles is Self-Check.

2.13 Services

These profiles refer to individual services rather than service profiles or host profiles that directly or indirectly refer to them. The principal category classification and parent directory for these profiles is Services.

  • service-cisco_loadaverage.xml   --   check_snmp_cisco_loading
  • service-cisco_memory_utilization.xml   --   check_snmp_cisco_memutil
  • service-dhcp_alive.xml   --   "dhcp_alive" service
  • service-dns_alive.xml   --   "dns_alive" service
  • service-ipmi_alive.xml   --   "ipmi_alive" service
  • service-irc_alive.xml   --   "irc_alive" service
  • service-mysql_alive.xml   --   "mysql_alive" service
  • service-nntp_alive.xml   --   "nntp_alive" service
  • service-nrpe_alive.xml   --   check version on nrpe server
  • service-ntp_alive.xml   --   "ntp_alive" service
  • servive-pop3_alive.xml   --   "pop3_alive" service
  • service-snmp_alive.xml   --   "snmp_alive" service
  • service-tomcat_alive.xml   --   "tomcat_alive" service
2.14 SNMP

Theses profiles use SNMP to monitor services on a remote device and communicate back information to the GroundWork monitoring server. The principal category classification and parent directory for these profiles is SNMP.

2.15 SSH

These profiles use SSH (Secure Shell) to monitor services on a remote device and communicate back information to the GroundWork monitoring server. GroundWork's standard method of monitoring UNIX servers is to have the GroundWork Monitor server connect to the monitored server using SSH and execute specially written plugins that return operating system and application properties. These plugins are included with GroundWork Monitor and numerous additional plug-ins are available in the open source community. The principal category classification and parent directory for these profiles is SSH.

2.16 VMware

These profiles relate to the monitoring of VMware entities and capabilities. The principal category classification and parent directory for these profiles is VMware.

2.17 Web

These profiles relate to the monitoring of various Web-related entities, capabilities, and protocols, such as web servers. The principal category classification and parent directory for these profiles is Web.

2.18 Windows

These profiles relate to monitoring Windows machines and their services. NSClient is used to monitor Windows services. An older monitoring agent called NSClient is still widely used in the Nagios community. It is installed on any Windows server requiring monitoring. The NSClient profiles use functions of NSClient to access operating system and application properties. The GroundWork Monitor server communicates directly with each NSClient agent. One drawback of NSClient is that extending it requires rebuilding the NSClient agent from source code, but this is a useful service for legacy installations. The principal category classification and parent directory for these profiles is Windows.

  • gdma-21-windows-host.xml   --   Windows base OS GDMA host profile
  • gdma-22-windows-host.xml   --   Windows Powershell GDMA host profile
  • service-profile-gdma-21-windows.xml   --   GDMA Windows Server (via WMI)
  • service-profile-nsclient-exchange.xml   --   Windows Exchange Mail Server (via NSClient)
  • service-profile-nsclient-mssql.xml   --   Windows MSSQL Server (via NSClient)
  • service-profile-nsclient-win.xml   --   Windows Server (via NSClient) 6.1-1
  • service-profile-snmp-win2k3.xml   --   Windows 2003 Service Profile 6.1-1
  • service-profile-windows-child-target.xml   --   Windows host monitored by Windows Child Server
  • service-profile-windows-child.xml   --   Windows Child Server
  • windows-child-target.xml   --   Profile for creating a target of a windows child system
  • windows-child.xml   --   Host profile for creating windows chld host object
2.19 Windows-NRPE

These profiles relate to monitoring Windows machines via the Nagios Remote Plugin Executor (NRPE). They allow for monitoring Windows operating system and application properties where the GroundWork Monitor server communicates directly with each monitored server and not through any proxy. An agent (NRPE or Nagios Remote Plug-in Executor) is installed on each monitored server along with VBS scripts that are accessed through the agent from the GroundWork Monitor server. These scripts are identical to those used in the WMI profiles. They allow access to thousands of properties on the monitored server. The GroundWork Monitor distributed NRPE-ALL profile consists of all the profiles with that specific monitoring type. WMI Profiles use the Windows Management Instrumentation (WMI) protocol to monitor Windows Services. Nagios Remote Plugin Executor (NRPE) is used by the Nagios Server to communicate with the WMI Proxy Server. This Proxy Server queries the monitored Windows Server for measurements and status using WMI. GroundWork uses an agent (NRPE) and a set of VBS scripts installed on a single Windows Server to communicate with monitored Windows Servers for operating system and application properties. The communication from the Proxy to the monitored Windows Servers is based on WMI (Windows Management Instrumentation) from Microsoft. WMI is installed on all currently supported Microsoft operating systems and is therefore 'agentless' making adding servers to GroundWork Monitor very easy. The VBS scripts allow access to thousands of properties on the monitored server. The GroundWork Monitor distributed WMI-ALL profile consist of all the profiles with that specific monitoring type. The principal category classification and parent directory for these profiles is Windows-NRPE.

Labels

profiles profiles Delete
services services Delete
distributed distributed Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.