Quest has been named as an ASP "Ten Best Web Support Sites" award winner. Learn more.

Foglight - Knowledge Base

Filter Your Results
Search All Products

Self Service Tools
Knowledge Base
Notifications & Alerts
Product Support
Software Downloads
Technical Documentation
User Forums
Video Tutorials
Featured Content
Online Documentation
New to Foglight?
Contact Support
Contact Support

Search Knowledge Base by keyword

(Choose different product)



Sort By Last Updated
Displaying 1-25 of 26

Please run

ps -ef | grep -i Foglight

on your Linux server

See KB 138568 for example of servers exclusion at the rule level.

When trying to validate the type of connection being established by the Windows agents, the log file 001 for the agent can be reviewed for the keywords:

  • Established a PoolableWMINative
  • Established a WinRMConnection

Agent logs are available on the directory "<Foglight Agent Manager installation path>\state\default\logs\fb8be857-fbcf-4747-973d-295a8570e581\HostAgents\<agent version>\WindowsAgent\Agent_Name_001.log). 

The MultiHostProcessAgent name can be known by doing a search of the hostname in the MonitoringPolicies_yyyy-mm-dd_nnnnnn.xml file. This file is included in the root of the Foglight Management Server (FMS) Support Bundle zip file. 

How to generate a Support Bundle review: 

https://support.quest.com/kb/41911

From Foglight web console, navigate to the Databases dashboard.

  1. Select all of the database agents of a single type (for example SQL Server) to change.
  2. Click Settings | Administration 
  3. select Connection Details
  4. Connection Details populates with previously selected database agents, select all the agents.
  5. click the Set Credentials to selected agents button, fill in appropriate fields for user and password.
  6. click Validate Connectivity
  7. click Apply at bottom right.

Yes, by using Rules.

Foglight comes with several Rules out of the box, and some of them have an associated EmailAction action. Those can be customized to also execute a CommandAction action, which passes a specified command to the OS where the Foglight Management Server is running.

For more information, please check our documentation here.

The URL of the Foglight web console is <IP_ADDRESS>:8080

KB 189372 discusses using the "Groovy Script" field of the Alarm Filter to select the rules and severities of the alarms associated with a service.

See KB 90881 for example regex usage.

The supported Windows platforms for as a SQL PI or Oracle PI repository are:

  • Windows 2008
  • Windows 2008 R2
  • Windows 2012
  • Windows 2012 R2

The supported Linux platforms for as a SQL PI or Oracle PI repository are:

  • CentOS 6.x (x86-64)
  • CentOS 7.x (x86-64)
  • Red Hat Enterprise Linux 6.x (x86-64)
  • Red Hat Enterprise Linux 7.x (x86-64)
  • SUSE Linux 11 (x86-64)
  • SUSE Linux 12 (x86-64)

Oracle Enterprise Linux is not supported as a SQL PI or Oracle PI repository.

NOTE: Linux® is the recommended platform for both Oracle and SQL Server monitoring. Exclude the SQL PI repository directory (named Infobright™) from real-time scanning (for example, Antivirus software).

To install a DB2 agent:

  1. On the Foglight navigation panel, click Homes | Databases.
  2. Click Monitor | DB2 in the upper left corner of the Databases View.
    The Monitor Instance dialog box appears.
  3. Follow the online prompts to configure an agent to monitor the DB2 host, instance, and databases. For help with options, click the 'i' icon.

To install a single SQL Server or Oracle agent:

  1. On the Foglight navigation panel, click Homes | Databases
  2. Click Monitor | < DB Type> in the upper left corner of the Databases View.
    The Monitor Instance dialog box appears.
  3. Choose the agent manager on which the agent is running. The default is the agent manager with the least agents installed.
  4. On the Monitor Instance pane, provide connection details.
  5. Select an Alarm Sensitivity Level to determine what level of alarms the system stores and displays for this instance.
  6. Optional SQL PI- In the Monitoring Extensions pane, click the SQL PI monitoring extension. You are prompted to choose the Agent Manager on which the SQL PI repository is installed.
  7. Optional OS. In the Monitoring Extensions pane, click the Operating System link. To configure the extension, choose the connection details of the host on which the SQL Server instance is running.
  8. Optional VM. In the Monitoring Extensions pane, click Collect VM statistics. To configure the extension, select the connection details of the vCenter® or ESX® on which the SQL Server instance is running.

Please consult the Deployment Guide for the Foglight database cartridge available for download from here for the current list of supported monitored databases.

Please refer to the System Requirements and Platform Support Guide available for download from here for the list of supported platforms for the Foglight Management Server (FMS).

High Availability (HA) is not supported for Sybase agents.

PI manages data using an internal time pyramid; the roll-up process runs every 15 minutes.

Time Resolution                     Retention Period

1 minute                                 6 hours

15 minutes                             3 days

1 hour                                    2 weeks

6 hours                                  30 days

1 day                                     90 days

1 week                                   2 years

Foglight cartridges run on the Foglight Management Server (FMS), which is the operation framework. Therefore, Foglight Management Server must be installed before installing a cartridge.

To install the Foglight cartridge:

  1. Copy the cartridge car file included in the installation media to your local computer.
  2. Log in to the Foglight browser interface.
  3. On the navigation panel, click Dashboards | Administration | Cartridges | Cartridge Inventory.
  4. On the Cartridge Inventory dashboard, click Browse to find the CAR file on your local computer.
  5. Click Install Cartridge.

Permissions required for database monitoring depend on the database that is being used. Please refer to the Foglight for Databases deployment guide available for download from here for most recent list of permissions required.

Please refer to the System Requirements and Platform Support Guide available for download from here for the current list of the supported platforms for the Foglight Agent Manager (FglAM).

Changing a database agent collection frequency and timeout

  1. On the Database Dashboard, place a check mark next to the Oracle agent or agents to be modified.
  2. Click Settings | Administration.
  3. Select the Collections menu item.
  4. Highlight the Collection name.
  5. Click the Edit button.
  6. Modify the Offline Frequency field, Online Frequency, Realtime, and/or timeout value.
  7. Click the Set button.
  8. Click Save Changes

Foglight collects data by running scripts (i.e. shell, sql, wmi) on a regular basis. Some these frequencies may be determined by the collection frequencies that are set in the agent properties.

For example, the Backup Config, Backup Jobs, and Backup Type Status collections by default are set to a Collection Interval or 21,600 seconds (six hours) for the realtime, online, and offline frequency modes. This is done to minimize the impact of performing queries regularly agent all of your monitored hosts.

Collection frequencies can be adjusted to reduce or increase the frequency of how often a particular collection is run against a monitored host. This is set on a agent-by-agent basis.

Here at Technical Support it is Quest’s policy not to be on call for assistance with Upgrades or Installations as we deal with break/fix issues at time of the problem. However, we will provide you with as much information as we can to help you to be successful on your upgrade.  Should you run into a problem during the upgrade or Installation we would recommend opening a Service Request and we will respond as quickly as possible to address any issues you may have encountered.  Most installations and upgrades proceed without issues.

The Foglight cartridges for DB2, Oracle, and SQL Server has a user defined query (user defined collection) component that allows users to provide custom SQL statements to retrieve data. With this solution you would be able to run custom queries to gather data in addition to data the Foglight SQL Server cartridge provides without installing an agent on the monitored server.

Please refer to the Database cartridge user guide available for download from here for more information on configuring and viewing User-Defined Collections in Foglight.

 

The available sampling frequencies are as follows:

  • Real-Time - When a user is currently focusing on a screen, the sampling frequency for all of the collections associated with this screen switches to Real-Time.
  • Online - When at least one user is connected, the sampling frequency for all of the collections that are not currently running at Real-Time frequency switches to Online.
  • Offline - when no user is currently connected to the application 

There are three main components:

  • Foglight Management Server and Foglight Database Repository — Responsible for managing, alerting and viewing the collected data. Both components can be set to run on the same machine or reside on separate machines.
  • Agent Manager — Hosts the monitoring database agents.
  • SQL PI Repository — An embedded repository which stores the SQL PI data that the monitoring agents collect. Currently available on Oracle and SQL Server monitoring only

NOTE: The product components can be either distributed over different machines — preferable in large or growing environments — or centralized.

Please refer to the Foglight for SQL Server or Foglight for Oracle deployment guides available for download from here for more information.