Chat now with support
与支持团队交流

Foglight for Integrations 5.9.4 - User and Reference Guide

Using Foglight for Integrations Reference

Using Foglight for Integrations

This User and Reference Guide provides instructions, and conceptual information about how to receive alarms from third-party systems in to Foglight. Learn how to receive Simple Network Management Protocol (SNMP) Traps into Foglight as alarms, and how to forward alarms from Foglight to third-party systems. Information on how external systems can format XML documents and feed them into Foglight to perform acknowledge and clear functions on alarms is provided.

In addition, this guide provides information about the dashboards, rules, and views that are available for your monitored Foglight for Integrations infrastructure.

This guide is intended for an expert user.

Understanding the Workflow

Foglight for Integrations enables you to receive alarms from third-party systems in to Foglight, and to forward alarms from Foglight to third-party systems. In addition, Foglight for Integrations contains a Simple Network Management Protocol (SNMP) Trap Receiver that can convert traps into alarms based on their Management Information Base (MIB) definitions and associated configurations. The following topics outline the different workflows for the Foglight for Integrations.

Alarms Workflow

Alarm workflows involve examining a set of alarms in real time and acting on those alarms. Operators who use the alarm workflows are interested in all alarms on some set of items. They watch the trend of those alarms over time and the most recent alarms. When alarms appear, the Operator takes immediate action by either acknowledging the alarm, clearing the alarm (to close an alarm that is no longer active), and forwarding the problems for resolution. The Alarms dashboard is best suited for system-wide alarm-oriented workflows.

User-defined properties can be supplied on third-party alarms and Configuration Items. These properties can be used to provide additional details about the alarm or Configuration Item.

A transformer concept is used to send alarms to Foglight. It transforms the data from the third-party systems format to the XML format that Foglight requires. During that transformation, additional properties can be formatted by using key-value pairs.

The key is the property name and the value is the value of the property. Before sending in a new property, it must be defined in Foglight. This is accomplished using the CI Property dashboard or the Alarm Property dashboard.

After the properties are fed into Foglight, the Configuration Items are displayed in a new model called the CIModel. You can search for Configuration Items either by using a Data browser interface or by viewing the list in the Integration dashboard.

These Configuration Items can then be included in services using traditional functionality already in Service Builder dashboard. Alarms received from the third-party systems would then impact the appropriate services.

Service-Oriented Workflow

A service is a collection of objects that you want to monitor. Users create most services on the basis of what they are responsible for, and are typically organized around what an Operator needs to monitor.

Foglight provides a feature called a Service Builder which allows the user to group one or more components. It provides the functions needed to create a service and edit existing services. When you create a service, a corresponding service level is automatically created.

Services are used as inputs to many other dashboards (Hosts Table, Agents) besides the Services dashboards, as well as to reports. Defining a good set of services can make other dashboards more useful and easier to understand.

For more information, see Using the CI Model in Service Builder .

自助服务工具
知识库
通知和警报
产品支持
下载软件
技术说明文件
用户论坛
视频教程
联系我们
获得许可 帮助
技术支持
查看全部
相关文档