Glossary
This is a new GroundWork Support document currently in development. Check back as we fill in the blanks and add more GroundWork Monitor relevant terms.
A
audit log
A feature in GroundWork Monitor Enterprise used to track system configuration and run time changes in an audit trail. » Audit Log
auto discovery
A tool in GroundWork Monitor allowing administrators to automatically coordinate network resources with the configuration database, thereby relieving administrators from having to manage all of their host and service definitions manually. » Auto Discovery
B
bsm
The Business Service Monitoring (BSM) feature, included in the core version of GroundWork Monitor Enterprise, provides a way to group objects and assign status to a group based on the state of its members. » BSM and SLAs.
C
certificates
SSL certificates enable websites to move from HTTP to HTTPS which is more secure. » Certificates
cloud hub
A Connector is like a plug in - it has the details you need to scrape monitoring data out of a particular API, such as the Amazon CloudWatch API, the cAdvisor API from Docker, or even MS Azure. This section reviews the configuration for each of the currently available GroundWork Cloud Hub connectors. » Cloud Monitoring
D
dashboards
GroundWork Monitor Enterprise offers several ways to view and analyze your monitoring data in a set of out-of-the-box Dashboards. » Dashboards
docker
Docker® is a set of platform as a service products that use OS-level virtualization to deliver software in packages called containers. Containers are isolated from one another and bundle their own software, libraries and configuration files; they can communicate with each other through well-defined channels. For GroundWork Monitor 8, we "Dockerized" all of the GroundWork server components, allowing portability and easing the burden of administration, especially upgrades.
docker-compose
Compose is a tool for defining and running multi-container Docker applications. With Compose, you use a YAML file to configure your application’s services. Then, with a single command, you create and start all the services from your configuration. » Docker Commands
downtime
The Downtime tool is used to schedule and manage monitoring downtime for all monitored entities including hosts, services, host groups, and service groups for regular and recurring downtime. » Downtime
E
events
A change of state of a host or service object, or one of a number of other updates to a host or service attribute, such as an acknowledgement or notification. » Dashboards.
F
G
gdma
Monitoring systems can be overwhelmed if asked to do too many things from a single instance. GroundWork Distributed Monitoring Agent (GDMA) allows you to offload the GroundWork Monitor server of nearly all the active checks you would otherwise execute with Nagios, and can reduce the need to deploy GroundWork Child Servers. In addition, allowing the monitored system to execute its own checks, you gain the ability to access resources present only on the machine without opening ports or running services like SNMP or even SSH. » GDMA Monitoring
H
K
kibana
The Log Analysis dashboard option uses the Kibana application and is best used to view monitoring log data. ELK Stack containers are included in GroundWork Monitor 8 and Kibana lets users visualize data with charts and graphs in Elasticsearch. » Log Analysis
L
M
migrate
A Migrate Install is considered a fresh GroundWork Monitor 8 installation plus a migration of your Monarch configuration from a previous version of GroundWork Monitor 7.x. » Migrate Install
N
nagios monitoring
In GroundWork Monitor, the Configuration > Nagios Monitoring menu item, is devoted to configuring and managing Nagios monitored elements. » Nagios Monitoring.
notifications
Notifications are alerts sent to contacts when GroundWork Monitor detects a failure or over threshold limit condition. Once a problem has been acknowledged or a host or service is in scheduled downtime, alerts will not be sent to the configured contacts. » NoMa Notifications
O
open source
GroundWork Open Source, Inc., an innovative software company, combines the best-of-breed open source tools and proprietary development to provide a unified IT monitoring solution. GroundWork Monitor Enterprise® is a unified monitoring system bridging enterprise on-premise and cloud-scale monitoring and analytics. With GroundWork Monitor Enterprise you can collect and analyze all your performance and operational data from a single platform.
P
profiles
Nagios Monitoring configuration uses device-specific profiles that contain both pre-defined and user-definable monitoring parameter settings. » Nagios Monitoring
R
roles
GroundWork Monitor incorporates Role Based Access Control (RBAC) to enable Administrators to restrict specific system access to authorized users. » Users Roles and Permissions
S
service group
Roles are assigned access to inventory through Groups, including host groups, service groups, and custom groups. » Users Roles and Permissions
snmp
GroundWork Monitor supports monitoring with SNMP (Simple Network Management Protocol). Primarily, GroundWork uses SNMP for getting information about network devices, both from an inventory perspective using NeDi (Network Discovery) and from a monitoring perspective using TCG-SNMP and Nagios Plugins. » SNMP Monitoring
snmp traps
GroundWork also support for processing SNMP Traps, however this is a solution currently only supported through GroundWork implementation Partners or GroundWork Professional Services.
status
The Status Summary is the main view of monitored resources in GroundWork Monitor. Status offers real-time updates, responsive graphing and top-problem displays. » Dashboards
T
tcg
The connection between GroundWork servers and monitoring data sources such as Nagios is facilitated by a new component called TCG, or the Transit Connection Generator. TCG allows the creation of resilient connections that automatically re-establish when broken, and buffers data to ensure a lossless stream of metrics. » TCG Connectors
U
users
A Users access to GroundWork Monitor menu options and inventory is based on the associated roles. Roles are assigned to users to determine a user access. » Users Roles and Permissions