Types of information available in data views

The following section describes the different types of data views and how they are created and organized:

  • Configuration Information
  • Performance (stats, raw) information
  • Rate (Rolled up, Condensed) Information
  • Baseline Information
  • Event Information

Default data views

The following section describe the default data views that are available in Infrastructure Management.

Thresholds (Absolute, Service Level Objective (SLO), and Signature)

The following table lists the thresholds information of type 'Absolute Default Thresholds (156 ):

Global absolute thresholds - ABSDFLTTHRESHOLDS_VIEW

Columns

Description

ABSDFLTABOVE

Above means current value should be greater than the thresholdfalse - belowtrue - above

ABSDFLTAUTOCLOSE

Tells whether to automatically close the event or not.false - Notrue - yes

ABSDFLTDURATION

How long the current values should exceed the threshold value before generating an event. 0 means event is generated immediately as one data point crosses the threshold value.

ABSDFLTSEVERITY

Severity of the event: Critical, Major, Minor, Event Only

THRESHOLDID

Internal threshold ID

MOTYPE

Monitor type ID

MOATTRID

Attribute ID

MONAME

Monitor type name

MOATTRNAME

Monitor Attribute Name

ABSDFLTTHRESHOLD

Threshold value

ABSDFLTBLTYPE

Can work in conjunction with threshold value. Non-zero, raw data points also need to pass the hourly, daily, or weekly baseline before the event can be triggered.  Same thing applies for closing of events

The following table lists the thresholds information of type 'Absolute Instance Thresholds (161)':

Instance absolute thresholds - INSTABSTHRESHOLDS_VIEW

Columns

Description

ABSINSTANCEABOVE

Above means current value should be greater than the thresholdfalse - belowtrue - above

ABSINSTANCEAUTOCLOSE

Tells whether to automatically close the event or not.false - Notrue - yes

ABSINSTANCEDURATION

How long the current values should exceed the threshold value before generating an event. 0 means event is generated immediately as one data point crosses the threshold value.

ABSINSTANCESEVERITY

Severity of the event: Critical, Major, Minor, Event Only

THRESHOLDID

Internal threshold ID

MOTYPE

Monitor type ID

MOATTRID

Attribute ID

MONAME

Monitor type name

MOATTRNAME

Monitor Attribute Name

MOINST

Monitor instance ID

DEVICENAME

Device name

INSTNAME

Monitor instance name

ABSINSTANCETHRESHOLD

Threshold value

ABSINSTANCEBLTYPE

Can work in conjunction with threshold value. Non-zero, raw data points also need to pass the hourly, daily or weekly baseline before the event can be triggered. Same thing applies for closing of events

The following table lists the thresholds information of type 'Signature Default Thresholds (157)':

Global signature thresholds - SIGNDFLTTHRESHOLDS_VIEW

View Name

Description

THRESHOLDID

Internal threshold ID

MOTYPE

Monitor type ID

MONAME

Monitor type name

MOATTRID

Attribute ID of threshold

MOTTRNAME

Monitor attribute name

SIGNDFLTTHRESHOLD

Threshold value

SIGNDFLTSEVERITY

Severity of the event. Critical, Major, Minor, Event Only

SIGNDFLTDURATION

How long the current values should exceed the threshold value before generating an event. 0 means event is generated immediately as one data point crosses the threshold value.

SIGDFLTSUPPRESSEVNTS

Whether to deactivate the signature threshold

SIGNABSPADFACTOR

Specify a margin around the baseline values to make it more difficult for signature events to occur.

SIGNPERPADFACTOR

Same as absolute pad factor, but instead of using a number, a percentage of the baseline is used.

SIGNDFLTBLTYPE

Allow threshold to be compared of daily and weekly baseline, in addition to hourly baseline.

SIGNDFLTABOVE

Above means current value should be greater than the thresholdfalse - belowtrue - above

SIGNDFLTAUTOCLOSE

Tells whether to automatically close the event or not.false - Notrue - yes

The following table lists the thresholds information of type 'Signature Instance Thresholds (162)':

Global signature thresholds - INSTSIGNTHRESHOLDS_VIEW 

View Name

Description

THRESHOLDID

Internal threshold ID

MOTYPE

Monitor type ID

MONAME

Monitor type name

MOATTRID

Attribute ID of threshold

MOTTRNAME

Monitor attribute name

SIGNDFLTTHRESHOLD

Threshold value

SIGNINSTSEVERITY

Severity of the event. Critical, Major, Minor, Event Only

SIGNINSTANCEDURATION

How long the current values should exceed the threshold value before generating an event. 0 means event is generated immediately as one data point crosses the threshold value.

SIGDFLTSUPPRESSEVNTS

Whether to deactivate the signature threshold

SIGNABSPADFACTOR

Specify a margin around the baseline values to make it more difficult for signature events to occur.

SIGNPERPADFACTOR

Same as absolute pad factor, but instead of using a number, a percentage of the baseline is used.

SIGNINSTBLTYPE

Allow threshold to be compared of daily and weekly baseline, in addition to hourly baseline.

SIGNINSTABOVE

Above means current value should be greater than the thresholdfalse - belowtrue - above

SIGNINSTAUTOCLOSE

Tells whether to automatically close the event or not.false - Notrue - yes

MOINST

Monitor instance ID

DEVICENAME

Device name

INSTNAME

Monitor instance name

SLO thresholds - SLOTHRESHOLDS_VIEW

View Name

Description

ABSINSTABOVE

Above means current value should be greater than the thresholdfalse - belowtrue - above

ABSINSTAUTOCLOSE

Tells whether to automatically close the event or not.false - Notrue - yes

ABSINSTDURATION

How long the current values should exceed the threshold value before generating an event. 0 means event is generated immediately as one data point crosses the threshold value.

ABSINSTSEVERITY

Severity of the event: Critical, Major, Minor, Event Only

THRESHOLDID

Internal threshold ID

MOTYPE

Monitor type ID

MOATTRID

Attribute ID

MONAME

Monitor type name

MOATTRNAME

Monitor Attribute Name

MOINST

Monitor instance ID

DEVICENAME

Device name

INSTNAME

Monitor instance name

ABSINSTTHRESHOLD

Threshold value

ABSINSTBLTYPE

Can work in conjunction with threshold value. If non-zero, raw data points will also needs to pass the hourly, daily or weekly baseline before the event can be triggered.  Same thing applies for closing of events

SLO configuration information

The following table lists the information about the attributes sets used in the system in reports and SLO:

View Name - ATTRIBUTESET_VIEW

Columns

Description

MOINSTID

Attribute set ID

ATTRIBUTELIST

List of attributes

The following table lists the information about schedules.

View Name - SCHEDULE_VIEW

Columns

Description

MOINSTID

Internal schedule ID

NAME

Name of the schedule

TIMERANGE

Time

The following table lists the SLO information.

View Name - SLO_INFO_VIEW

Columns

Description

SLOID

SLO ID

NAME

Name of the SLO

CONTENTID

Content type SLO/instance. See CONTENTID in SLO_CONTENT_VIEW.

SLOTYPEID

SLO type ID

SLO_SCHEDULE

SLO schedule

COMPLIANCE_OBJECTIVE

Compliance objective value

OWNER

Name of the owner

CONTACT_INFO

Contact information

CREATE_DATE

Date when SLO is created

COMMENTS

Comments

UPDATE_DATE

Date when SLO is updated

The following table lists all SLO information:

View Name - SLO_INSTANCES_INFO_VIEW

Columns

Description

INSTID

SLO Instance ID

SLOID

SLO ID

MOTYPEID

Monitor type ID

MOINSTID

Monitor instance ID

The following table lists all the SLO information:

View Name - SLO_THRESHOLD_INFO_VIEW

Columns

Description

INSTID

SLO Threshold Instance ID

SERVICE_LEVEL_THRESHOLD_ID

See thresholdid in slo_threshold_view

WEIGHT

Weightage

COMMENTS

Comments

The following table lists SLO containment information

View Name- SLO_CHILD_INFO_VIEW

Columns

Description

SLOID

Parent SLO IDRefer sloid in slo_info_view

CHILD_SLOID

Child SLO IdRefer sloid in slo_info_view

WEIGHT

Weightage

SLO summary data

The following table lists the SLO summary information:

View Name - SLO_SUMMARY_VIEW

Columns

Description

SLOID

SLO ID

PREVIOUS_DAY

Compliance value for previous day

PREVIOUS_WEEK

Compliance value for previous week

WEEK_TO_DATE

Compliance value for week to date

PREVIOUS_MONTH

Compliance value for previous month

MONTH_TO_DATE

Compliance value for month to date

QUARTER_TO_DATE

Compliance value for quarter to date

YEAR_TO_DATE

Compliance value for year to date

PREVIOUS_DAY_TREND

Compliance value for previous day trend

WEEK_TO_DATE_TREND

Compliance value for week to date trend

The following table lists the SLO summary by day:

View Name - SLO_SUMMARY_DAY_VIEW

Columns

Description

SLOID

SLO ID

DATE_TIME

Date and Time

COMPLIANCE_VALUE

Compliance value

The following table lists the SLO summary by week:

View Name - SLO_SUMMARY_WEEK_VIEW

Columns

Description

SLOID

SLO ID

DATE_TIME

Date and Time

COMPLIANCE_VALUE

Compliance value

The following table lists the SLO summary by month:

View Name - SLO_SUMMARY_MONTH_VIEW

Columns

Description

SLOID

SLO ID

DATE_TIME

Date and Time

COMPLIANCE_VALUE

Compliance value

The following table lists the SLO summary by quarter:

View Name - SLO_SUMMARY_QUARTER_VIEW

Columns

Description

SLOID

SLO ID

DATE_TIME

Date and Time

COMPLIANCE_VALUE

Compliance value

The following table lists the SLO summary by year:

View Name - SLO_SUMMARY_YEAR_VIEW

Columns

Description

SLOID

SLO ID

DATE_TIME

Date and Time

COMPLIANCE_VALUE

Compliance value

The following table lists the data for each SLO instance by day:

View Name - SLO_INSTANCES_DAY_VIEW

Columns

Description

INSTID

See instid in slo_instances_info_view

SERVICE_LEVEL_THRESHOLD_ID

See thresholdid in slo_threshold_view

MOTYPEID

Monitor type ID

MOINSTID

Monitor instance ID

ATTRIBUTEID

Attribute ID

DATE_TIME

Date and Time

TOTAL_VALID_DATA_POINTS

Total valid data points

TOTAL_VIOLATED_DATA_POINTS

Total violated data points

TOTAL_UNKNOWN_DATA_POINTS

Total unknown data points

COMPLIANCE_VALUE

Compliance value

MINVALUE

Minimum value

MAXVALUE

Maximum value

MEDIAN

Median value

AVERAGE

Average value

WEIGHT

Weight

The following table lists the data for each instance by week:

View Name - SLO_INSTANCES_WEEK_VIEW

Columns

Description

INSTID

See instid in slo_instances_info_view

SERVICE_LEVEL_THRESHOLD_ID

See thresholdid in slo_threshold_view

MOTYPEID

Monitor type ID

MOINSTID

Monitor instance ID

ATTRIBUTEID

Attribute ID

DATE_TIME

Date and Time

TOTAL_VALID_DATA_POINTS

Total valid data points

TOTAL_VIOLATED_DATA_POINTS

Total violated data points

TOTAL_UNKNOWN_DATA_POINTS

Total unknown data points

COMPLIANCE_VALUE

 Compliance value

MINVALUE

Minimum value

MAXVALUE

Maximum value

MEDIAN

AVERAGE

WEIGHT

The following table lists the data for each instance by month:

View Name - SLO_INSTANCES_MONTH_VIEW

Columns

Description

INSTID

See instid in slo_instances_info_view

SERVICE_LEVEL_THRESHOLD_ID

See thresholdid in slo_threshold_view

MOTYPEID

Monitor type ID

MOINSTID

Monitor instance ID

ATTRIBUTEID

Attribute ID

DATE_TIME

Date and Time

TOTAL_VALID_DATA_POINTS

Total valid data points

TOTAL_VIOLATED_DATA_POINTS

Total violated data points

TOTAL_UNKNOWN_DATA_POINTS

Total unknown data points

COMPLIANCE_VALUE

Compliance value

MINVALUE

Minimum value

MAXVALUE

Maximum value

MEDIAN

Median value

AVERAGE

Average value

WEIGHT

Weight

The following table lists the data for each instance by quarter:

View Name - SLO_INSTANCES_QUARTER_VIEW

Columns

Description

INSTID

See instid in slo_instances_info_view

SERVICE_LEVEL_THRESHOLD_ID

See thresholdid in slo_threshold_view

MOTYPEID

Monitor type ID

MOINSTID

Monitor instance ID

ATTRIBUTEID

Attribute ID

DATE_TIME

Date and Time

TOTAL_VALID_DATA_POINTS

Total valid data points

TOTAL_VIOLATED_DATA_POINTS

Total violated data points

TOTAL_UNKNOWN_DATA_POINTS

Total unknown data points

COMPLIANCE_VALUE

Compliance value

MINVALUE

Minimum value

MAXVALUE

Maximum value

MEDIAN

Median

AVERAGE

Average

WEIGHT

Weight

The following table lists the data for each SLO instance by year:

View Name - SLO_INSTANCES_YEAR_VIEW

Columns

Description

INSTID

See instid in slo_instances_info_view

SERVICE_LEVEL_THRESHOLD_ID

Refer thresholdid in slo_threshold_view

MOTYPEID

Monitor type ID

MOINSTID

Monitor instance ID

ATTRIBUTEID

Attribute ID

DATE_TIME

Date and Time

TOTAL_VALID_DATA_POINTS

Total valid data points

TOTAL_VIOLATED_DATA_POINTS

Total violated data points

TOTAL_UNKNOWN_DATA_POINTS

Total unknown data points

COMPLIANCE_VALUE

Compliance value

MINVALUE

Minimum value

MAXVALUE

Maximum value

MEDIAN

Median value

AVERAGE

Average value

WEIGHT

Weight

SLO Violation Records

The following table lists all the SLO violations:

View Name

Columns

Description

THRESHTIME

SLO threshold time

ENDTIME

SLO violations end time

KEEPALIVETIME

Time to keep SLO violations

VIOLATIONID

SLO violation ID

MOTYPEID

Monitor type ID

MOINSTANCEID

Monitor instance ID

ATTRID

Attribute ID

HOSTID

Host ID

SLTTYPE

SLT type

SLTID

SLT ID

SEVERITY

Severity of violation

LASTVALUE

Last value

EXCEEDPOINTCNT

Count for exceed point of violation

DESCRIPTION

Description for SLO violation record

Groups

The following table lists all the user groups:

View Name - GROUP_INFO_VIEW

Columns

Description

GROUPID

Group ID

GROUPNAME

Name of the group

DESCRIPTION

The following table lists groups containing other groups:

View Name - GROUP_TREE_VIEW

Columns

Description

PARENTGROUPID

Parent Group ID

CHILDGROUPID

Child Group ID

The following table lists monitors that belong to a specific group:

View Name - GROUP_MONITOR_VIEW

Columns

Description

GROUPID

Group ID

MOTYPEID

Monitor type ID

MOINSTID

Monitor instance ID

Using group views

Suppose there are three groups Sample_1, Sample_2, Sample_3. This information can be retrieved from GROUP_INFO_VIEW.

GROUP_INFO_VIEW

Group ID

Group Name

Description

1

Sample_1

Sample group 1

2

Sample_2

Sample group 2

3

Sample_3

Sample group 3

Sample_1 and Sample_2 groups are made of monitor instances. This information can be retrieved from GROUP_MONITOR_VIEW.

GROUP_MONITOR_VIEW

Group ID

MO Type ID

MO Instance ID

1

20031

1

2

20031

10

2

20035

15

This shows that Sample_1 group contains one instance with ID 1 of monitor type web URL (20031). Sample_2 group contains one instance with ID 10 of monitor type web URL (20031) and one instance with ID 15 of type web transaction (20035).

Lets assume that Sample_3 group is made of other two groups. This group containment information can be retrieved from GROUP_TREE_VIEW.

GROUP_TREE_VIEW

Parent Group ID

Child Group ID

3

1

3

2

For details of all the default data views in Infrastructure Management, run the pw dataview gendoc command.

Was this page helpful? Yes No Submitting... Thank you

Comments