Chatta subito con l'assistenza
Chat con il supporto

Foglight 5.9.1 - Administration and Configuration Guide

Administering and Configuring Foglight Extending Your Monitoring Reach with Foglight Cartridges Administering Foglight Configure Rules and Metric Calculations to Discover Bottlenecks Customizing Your Foglight Environment with Tooling

Enabling Automatic Communication with Quest

The Foglight™ Management Server can communicate with Foglight.com to check for important updates and to send usage data to Quest. Enabling this setting also allows usage data to be sent to Quest including visited dashboards, unique ID of Management Server, Server version and configuration details. This information is then displayed on the Automatic Communication with Quest dashboard or can be viewed in a popup by hovering over the Update link on the Administration page.

When this setting is enabled, you will receive messages:

Notifications are sent to users with the Administrator role. By default, this feature is turned on. To turn it off, click Disable on the Automatic Communication with Quest dashboard. To access this dashboard, from the Administration dashboard, in the Support column, click Support Notifications.

 

 

Extending Your Monitoring Reach with Foglight Cartridges

Each Foglight™ cartridge contains extensions for monitoring a specific environment, such as applications, operating systems, or database management systems. Cartridges are installed on the server. A cartridge can contain one or more agents that are used to collect data from monitored environments.

The Foglight Management Server includes a set of default cartridges that contain models, views and monitoring policies. In addition to these server-specific cartridges, there are other types of cartridges that are distributed separately from the server. They extend the server’s monitoring capabilities, allowing you to monitor specific types of environments, such as operating systems, processes, databases, applications, hosts, and others. These types of cartridges typically include agent packages, agent adapters, monitoring policies, and dashboards.

A cartridge monitoring policy contains settings that help Foglight analyze the data that the agents collect, such as rules, registry variables, schedules, and derived metrics. The items included in the monitoring policy are specific to each cartridge type. The dashboards included with a cartridge allow the information collected by the agents to be displayed in a unified view.

The Management Server includes the Cartridge Inventory dashboard, which contains controls for installing, enabling, disabling, and uninstalling cartridges, and for viewing information about the installed cartridges. To access this dashboard, from the navigation panel, click Dashboards > Administration > Cartridges > Cartridge Inventory.

Some cartridges include additional components, such as agent installers or additional configuration files. After cartridge installation, these components are available for download from the Foglight Management Server using the Components For Download dashboard. To access this dashboard, from the navigation panel, click Dashboards > Administration. On the Administration dashboard, click Component Download in the Cartridges column.

For more information, see the following topics:

Configuring Foglight Agents for Host Monitoring

Foglight™ agents collect data from monitored environments and send it to the Management Server. Each agent type can monitor a specific part of your environment, such as an operating system, application, or server. Foglight cartridges that you install on the server include one or more agent types. Foglight also includes internal agents that monitor Foglight components and services.

Foglight uses the Foglight Agent Manager to communicate with monitored hosts. A server installation includes an embedded Foglight Agent Manager. The embedded Agent Manager starts up and stops with the Foglight Management Server. This embedded instance can be used to monitor the host on which the Management Server is installed. To monitor additional hosts in your environment, most cartridges require an Agent Manager installation on each host computer.

After installing and enabling a cartridge, and downloading remaining cartridge components, deploy its agent package to each host running an Agent Manager that you want to monitor. After deployment, create an agent instance for each monitored host, edit the agent’s properties, and start its data collection. See the Installation and Setup Guide set for information on installing the Agent Manager on the hosts that you want to monitor.

There are two dashboards that allow you to deploy agent packages and create agent instances: Agent Status and Agent Managers. To access the Agent Managers dashboard, from the navigation panel, click Dashboards > Administration > Agents > Agent Managers.

To access the Agent Status dashboard, from the navigation panel, click Dashboards > Administration > Agents > Status.

For more information, see the following topics:

Editing Agent Properties by Type

When an agent connects to the Foglight™ Management Server, it is provided with a set of properties that it uses to configure its correct running state. Foglight stores agent properties on the Management Server.

You can edit the properties of agent types (global properties), or the properties of individual agent instances (private properties). Typically, after creating an agent instance, before its activation, you edit the agent properties. This causes the agent property values to become private. Agent instances with private properties are not affected by any subsequent changes made to its global properties. Changes to global properties are only carried over to new agent instances that are created after those changes.

Another classification of agent properties refers to their format, complexity, and shareability. Primary properties are typically text, number, or Boolean values. These types of values are easily specified and changed. Secondary or shared properties are in list form and contain multiple values organized into rows and columns. They can be easily cloned and modified to suit the needs of individual agent instances. The difference between primary and secondary (shared) properties is that secondary properties can be shared amongst multiple agent instances, meaning that a list can be associated with multiple agent instances of the same type. However, any changes made to a shared list affect all of those agents.

Any passwords that are defined in agent properties are encrypted. This feature is useful in situations when a database password is defined in agent properties, and there are multiple databases in your environment, for example, a Foglight database and a production database. Encrypting database passwords prevents unauthorized database administrators from accessing the database.

Agent properties can be edited using the Agent Properties dashboard. You can use it to edit the properties globally, for all instances of the same type, or only for a specific agent instance. To access this dashboard, from the navigation panel, click Dashboards > Administration > Agents > Agent Properties, or select an agent instance on the Agent Status dashboard and click Edit Properties.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione