Glossary

Java-based, open-source message broker supported by the Apache community (see Set up Message Broker).

Indicators for problems occurring on entities that Horizon monitors (see Alarms).

An OpenNMS framework that uses artificial intelligence and machine learning to provide alarm triage. It groups related alarms so you can better manage the more complex situations that they might represent.

A method that uses the Minion infrastructure to monitor a service’s availability from different perspectives. It helps to identify if nodes are down for everyone, or if an outage affects only certain sites. When a service is not responsive, an outage is generated using the perspective that detects the outage (see Application Perspective Monitoring).

A set of configuration categories that are specific to nodes (for example, Display Category, Notification Category).

A set of optional fields, similar to metadata, that can be associated with a node to provide additional information (for example, physical location, hardware specifications).

Nodes that are automatically added to Horizon through routine or one-time discovery (see Auto Discovery).

A cloud hosting platform that allows users to host a variety of services.

A framework that allows scripting to be used in Java code via a set of classes. The Horizon BSFDetector runs arbitrary BSF scripts to determine the existence of a service, and the BSFMonitor uses scripts to determine the status of a service.

A Horizon feature that lets you monitor and generate alerts for issues affecting complex business services spanning multiple nodes (see Business Service Monitoring).

An open-source distributed/scale-out NoSQL database designed to hold large amounts of structured or unstructured data across many servers. The optional Newts storage strategy requires a Cassandra instance for back-end storage.

Custom collections of entities on Horizon-monitored networks. They let you define a matrix for aggregating monitoring results (see Categorize nodes).

The practice of continuous integration (frequently merging small changes into a repository’s main branch) and continuous delivery (short software development cycles with repeatable deployment processes).

A continuous integration and delivery platform that hosts The OpenNMS Group’s CI/CD environment. It integrates with and monitors the OpenNMS GitHub repositories, and automatically launches and tests a new build when it detects a commit.

A program that lets you run commands for various operating system functions (for example, compiling code).

Horizon sub-services that perform specific sets of tasks (see Daemons).

Nodes that are added to Horizon manually through a requisition (see Directed Discovery).

An open-source forum platform that hosts the OpenNMS community forums. There, users can find knowledge base articles, support, announcements, and general discussion about all things OpenNMS.

A process that uses ICMP to find network devices and services in your network, then automatically adds them to monitoring (see Automatic discovery).

An open-source container virtualization service that lets you deploy application-level services without worrying about operating system maintenance. Horizon components may optionally be deployed as Docker containers.

The service on a Horizon instance that controls Minion operations (see Configuring Minion via confd).

A system to manage business rules that supports the Java Rules Engine API standard. It helps provide a more robust infrastructure for workflow and problem state management in alarmd (see Alarm Service Daemon).

A component of the Elastic Stack (comprised of Elasticsearch, Logstash, and Kibana). It is a NoSQL database with an integrated search engine based on the Lucene library. Horizon persists and forwards certain data to Elasticsearch to store flow records, and warehouse events and alarm history for long-term storage of this data (see Elasticsearch Integration).

Structured historical records of activities in Horizon and the nodes, interfaces, and services it manages (see Events).

Summaries of network traffic sent by network devices (see Flows).

A unique identifier for a provisioning source that is located outside of your local network.

A custom set of service detectors and provisioning policies for a foreign source (see Foreign Source Definition).

The actual physical location of a node monitored by Horizon, represented by its latitude and longitude. Nodes can be manually assigned a location, or the location can be automatically determined using the GeoIP Provisioning Adapter.

An open-source analysis and visualization web application. It connects to data sources and generates dashboards with charts, graphs, and alerts.

An open-source solution from The OpenNMS Group that lets you visualize and monitor everything on your local and remote networks. The free, community-driven project includes the latest technology and features and is delivered through a rapid release cycle.

An automation and workflow service that integrates apps, devices, and services. Horizon can integrate with IFTTT to trigger actions on other services based on customized alarms (see IFTTT Integration).

(1) A single, unique occurrence of an element, document, or running program. (2) A data structure that is used in data collection to store tabular data as individual data points. (3) A single implementation of Horizon.

The percentage of time that a node interface is detected as being accessible. Horizon typically shows availability statistics for the past 24 hours; this is calculated by subtracting the amount of outage time for an interface during the given time period.

A set of tools for managing and monitoring services, resources, and service-oriented networks. Horizon uses it to collect long-term performance data for Java applications (see JMX Configuration Generator).

A project management platform that The OpenNMS Group uses to track software issues, feature requests, and IT requests for its projects, including Horizon (see OpenNMS Jira).

A clone of RRDTool written in Java. It is the default time series database for new Horizon instances.

A clusterable, open-source message broker designed for high-throughput/low-latency event streaming. Originally developed at LinkedIn, it is now supported by the Apache community (see Set up Message Broker).

A component of the Elastic Stack (comprised of Elasticsearch, Logstash, and Kibana). It enables visualizations for data indexed in an Elasticsearch cluster.

Key SNMP customized (KSC) reports provide a way to generate prefabricated graphical views of collected data. They let you display data from different devices and sources (SNMP, ICMP, HTTP) on one page (see KSC Reports).

An open-source container orchestration system for automating software deployments, scaling, and management. Originally designed by Google, the Cloud Native Computing Foundation now maintains it.

A subscription-based, optimized, and stable version of the OpenNMS Horizon platform that includes only the most stable and secure Horizon features. It is distributed via annual release with monthly security patches.

An asynchronous service that enables communication between an application’s distributed components. When using Minions and Sentinels, a message broker is required for communication between servers. Horizon has an embedded ActiveMQ server available for smaller deployments. You can swap the broker with a dedicated ActiveMQ, gRPC, or Kafka cluster to provide scalability and load balancing.

A distributed component that enables Horizon to monitor devices and services in locations that it normally cannot reach. Minions communicate with these remote devices while Horizon performs coordination and task delegation (see Minion).

Also referred to as "Minion location" or "location." Nodes assigned to a location are monitored by Minions assigned to the same location.
This is distinct from geolocation, which is the actual physical location of a monitored entity.

An OpenNMS component that enables horizontal scaling of flow processing. It is not required for flow processing, but can improve performance for deployments with a very high volume of flow documents.

One or more locations where a network is monitored and controlled (see Network Operations Center).

An OpenNMS time series datastore based on Apache Cassandra. You can use it as an alternative persistence strategy (instead of JRobin or RRDtool).

A device or application that sends communications over a network (for example, a server). They can be provisioned to and monitored by Horizon. A node must include at least one IP interface, otherwise it is removed from your Horizon inventory.

The percentage of time that a node is detected as being accessible. A node is considered "down" when its critical path is inaccessible. Horizon typically shows availability statistics for the past 24 hours; this is calculated by subtracting the amount of outage time for a node during the given time period.

An interface responsible for conveying details of Horizon-generated alarms to a higher-level component.

Messages delivered to a set of recipients. Horizon notifications inform you about events in their monitored networks without forcing you to sign in and look at the UI (see Notifications).

A Grafana plugin for creating flexible dashboards to display and customize fault, flow, and performance data from Horizon. Previously known as Helm.

Customizable dashboard to visualize monitoring information.

The ability to measure the internal state of a system by examining its output. If the system’s state can be estimated using only its output, it is considered "observable."

A customizable dashboard that lets you visualize monitoring information (see Operator Board).

Also known as "downtime," this is a period of time that a service is unavailable or offline. It can be caused by systems or communications failures, or planned as part of routine maintenance.

The process by which a newSuspect event is detected by provisiond and converted into a new node. You can configure trapd and syslogd to generate this event when Horizon receives messages from nodes that do not exist in the database (see Add nodes via newSuspect events).

A commonly used open-source relational database known for its stability. PostgreSQL scales up, but not out (see Set up PostgreSQL).

The process of importing node and service definitions to a Horizon instance from either an external source (for example, DNS, HTTP) or via the web UI (see Provisioning).

An optional service that gathers node inventory information from an external source. You can use it to generate requisition XML files for creating, updating, or removing nodes for monitoring.

A common type of database that stores data in tables, with relationships between tables to structure data (for example, a PostgreSQL database).

A Java API that lets one object running in a Java Virtual Machine (JVM) invoke methods on an object running in another JVM. RMI integration lets you access a remote Horizon or Meridian instance for monitoring and management (see Enable RMI).

Sets of nodes to import into Horizon for monitoring and management. You can build requisitions iteratively and import them at a later date (see Create a requisition).

Any hardware or software that Horizon can access.

A database designed for collection, visualization, and analysis of time series data. Data is maintained as a fixed-size circular buffer that overwrites the oldest data with new data.

A small set of data collected from a Horizon-monitored source.

A Karaf container that provides scalability for data processing of flow data. It also supports thresholding for streaming telemetry if you are using the Newts time series strategy.

The percentage of time that a service is detected as being accessible. Horizon typically shows availability statistics for the past 24 hours; this is calculated by subtracting the amount of outage time for a service during the given time period.

An internet standard protocol. Horizon monitors SMTP availability on network nodes to ensure that email messages can be sent and received (see MailTransportMonitor).

An internet standard protocol used to collect, organize, and modify information about managed devices on an IP network (see Configure SNMP for provisioning).

Self-contained software packages that run in a sandbox and have mediated access to host systems. The OpenNMS Appliance Service uses snaps to distribute operating system packages and Minion service updates.

A hardware or software vendor file that describes SNMP objects their products provide. MIB files can be processed to convert the definition into data collection and event objects for Horizon to work with. Many of the major vendor MIB definitions are included out of the box.

The process of automatically recording and transmitting data from an external source to a system in a different location for monitoring or analysis. Telemetryd accepts data sent from nodes in one of the supported protocol formats.

A sequence of data points that occur in successive order over a period of time.

A database that is designed to store and serve time series data (see Time Series Database and Time Series Database).

A description or visual representation of a network’s elements (devices, services) and the relationships among them (see Topology).

Event triggers generated by SNMP-capable devices on the network and sent to trapd (see SNMP Traps).

A string that uniquely identifies an event’s type. UEIs must begin with uei. (see Events and UEIs).