Chat now with support
Chat con el soporte

Foglight Experience Monitor 5.8.1 - SQL Reference Guide

Foglight Experience Monitor SQL reference
Database Tables Alarm database Application database Enterprise database HTTP Fault database Location database Instrumented Application database Page database Protocol database Server database Service database Site database Soap Database Soap Consumer database Soap Fault database Soap Transaction database Subnet database System database User Agent database User Session database
Appendix: Column description Appendix: Example queries

Foglight Experience Monitor SQL reference

This section provides a description of the Structured Query Language (SQL) databases that the Foglight Experience Monitor uses to store metrics and related information.

By navigating to Help > Support Tools in the Foglight Experience Monitor and clicking on either the Enable Detailed Logging or the Disable Detailed Logging links, you can see queries that the web console uses to obtain metrics from the database. For each page that you navigate to in the web console, logging statements are generated. Search for the text SQL query to see the query that the web console is using.

For details, see these topics:

Database

The following table displays the individual databases that every appliance maintains.

Contains alarm

Contains Application, Application by City, Application by Country, Application by Region, Application by ISP, Application by Subnet category metrics

System use only

Contains Enterprise category metrics

Contains HttpFault entries

Contains Instrumented Application Component, Instrumented Application Component by City, Instrumented Application Component by Country, Instrumented Application Component by ISP, and Instrumented Application Component by Region category metrics

Contains City, Country, ISP, and Region category metrics

Contains Content Type, Hit, Page, Instrumented Page, Path, and Synthetic Service category metrics

Contains Protocol category metrics

Contains Server category metrics

Contains Service, Application by City, Application by Country, Application by Region, Application by ISP, Application by Subnet category metrics

Contains Site category metrics

Contains Soap Operation, Soap Server, Soap Web Service category metrics

Contains Soap Consumer category metrics

Contains Soap Fault entries

Contains Soap Transaction and Soap Transaction Step category metrics

Contains Subnet category metrics

System use only

Contains User Agent category metrics

Contains User Session category metrics

System use only

Tables

This section includes detailed information about the following topics:

Metric tables

Metric tables contain all of the standard metrics for resources (or objects) that the system is monitoring. These include all metrics other than distributions and reference counters. The descriptions starting in section 3 include a table showing each column, its type, and a comment. Many of the comments show the actual metric label that appears in the web console. Some labels have a suffix that identifies the exact statistic that the column represents.

The following table presents these suffixes.

Number of events associated with the metric. For End-to-End Time this is the number of page downloads.

Sum total for all events.

For End-to-End Time this is the sum total of the time taken for all page downloads in the interval.

Square of the Sum.

Minimum value seen during the interval.

Maximum value seen during the interval.

Percentile (usually 95th percentile) for the metric.

Mean of all values seen during the interval. This equals Sum / Count.

Standard deviation of all values seen during the interval.

Numerator of a percentage metric. For Hit Redirect Ratio this is the total number of hits redirected.

Denominator of a percentage metric. For Hit Redirect Ratio this is the total number of hits.

Every resource the system has monitored has a unique identifier that is present in the ResourceID column of every table. The algorithm used to calculate a resource identifier varies from category to category, but it is typically based on some unique aspect of the resource. For some categories (such as Application Component and Service) it is calculated from the unique configuration database item that defines the resource. For categories like Pages and Hits, the identifier is calculated using the URL of the underlying object.

An example of a resource identifier is shown here:

This object is from the Application Component category. The first two characters 2a indicate the category of the object. Convert this number from hexadecimal to decimal and you get 42. See the CategoryID section for a complete list of category identifiers.

Herramientas de autoservicio
Base de conocimientos
Notificaciones y alertas
Suporte de productos
Descargas de software
Documentación técnica
Foros de usuarios
Tutoriales en video
Comuníquese con nosotros
Obtenga asistencia con las licencias
Soporte Técnico
Ver todos
Documentos relacionados