Versions Compared

Old Version 16

changes.mady.by.user Nadja Pollard

Saved on

compared with

New Version 17

changes.mady.by.user Nadja Pollard

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Before you start browsing the Alerts MIB, it is recommended to be familiar with the following issues:•    Technology

  • Technology representation

...

  • Identifying environments and instances in the MIB

...

  • Identifying metrics in the MIB

...

  • Identifying property fields in the MIB

...

  • MIB structure

Technology representation

The MIB tree shows the technologies of the Precise environment as the numbers 1 - 15. The table below shows how each number in a MIB tree is mapped to a technology.

Table 16-5    MIB 5 MIB tree mapping

MIB

...

numberMapped to ...

...

1    Oracle

2    Sybase

3    MS-SQL

4    Tuxedo

5    Web

6    J2EE

7    SAP

8    Oracle Applications

9    Microsoft .NET

10    RESERVED

11    EMC Storage

12    Other

13    OS

14    Precise status

15    Websphere MQ

16    Sybase Replication Server

...

1Oracle
2Sybase
3MS-SQL
4Tuxedo
5Web
6J2EE
7SAP
8Oracle Applications
9Microsoft .NET
10RESERVED
11EMC Storage
12Other
13OS
14Precise status
15WebSphere MQ
16Sybase Replication Server
17DB2

Identifying environments and instances in the MIB

Alerts displays environments and instances by their names (environment_name, instance_name), while the MIB presents them by their identifiers (environment_id, instance_id).

To identify environments and instances in the MIB1.    Retrieve

  1. Retrieve a mapping table that maps the environment and instance names to their identifiers by running the following SQL statement in the Alerts schema:
    select
         INCE_ID INSTANCE_ID, INCE_NAME
         INSTANCE_NAME, INEN_ID
         ENVIRONMENT_ID, INEN_NAME
         ENVIRONMENT_NAME
    from
    PS_INCE_INSTANCE_INSTANCE, PS_INII_INSTANCE_APPTIER
    INSTANCE_APPTIER, PS_INAP_APP_TIER APPTIER,
    PS_INEN_ENVIRONMENT ENVIRONMENT
    where
         INCE_ID = INII_INCE_ID AND
         INAP_ID = INII_INAP_ID AND
         INAP_INEN_ID = INEN_ID AND
         INCE_DELETED = ‘F’ AND
         INII_DELETED = ‘F’ AND
         INAP_DELETED = ‘F’ AND
         INEN_DELETED = ‘F’ AND

Identifying metrics in the MIB

Alerts displays metrics by their names (metric_name), while the MIB presents them by their identifiers (metric_id).

The mapping table is sorted by the metric name.

To identify metrics in the MIB•    Retrieve

  • Retrieve a mapping table that maps between the metric names and their identifiers by running the following SQL statement in the Alerts schema:
    select indicator_id,indicator_name, from pulse_indicators order by indicator_name;

Available property fields in the MIB

The table below describes the available property fields for a metric.

Table 16-6    Available 6 Available property fields in the MIB

No.

...

FieldDescriptionApplies to
0Value

Specifies

...

the metric's value.

...

Same as the dynamic parameter: $METRIC_VALUE

...

Displayed in the Value metrics tab only. In case of a parent metric, only the sub-metrics show this field.

...

Get
1Status

Specifies the metric's status. Possible values: Critical, Near-critical, Normal, and Unsampled.

In the MIB browser, Downtime and Disabled statuses appear also as

...

Unsampled status.

...

Get
2SampleRate

Specifies

...

the sampling rate in minutes.

 

Same as the dynamic parameter: $SAMPLING_RATE

In case of a parent metric, only the parent shows this field.

...

Get
3NearCrThr

Specifies

...

the metric's Near-critical threshold.

 

Same as the dynamic parameter: $NEAR_CRITICAL_THRESHOLD

In case of a parent metric, only the sub-metrics show this field.

...

Get
4CriticalThr

Specifies

...

the metric's Critical threshold.

 

Same as the dynamic parameter: $CRITICAL_THRESHOLD

In case of a parent metric, only the sub-metrics show this field.

...

Get
5EnabledSpecifies

...

whether or not the metric is enabled (values: yes or no).

...

Get
6SampleTime

Specifies

...

the metric's last sampling time.

 

Same as the dynamic parameter:  $ACTUAL_SAMPLING_

...

TIME

Get
7MetricName

Specifies

...

the metric's name.

...

Same as the dynamic parameter: $METRIC_

...

NAME

Get
8InstanceName

Specifies

...

the instance's name.

...

Same as the dynamic parameter: $INSTANCE_

...

NAME

Get
9ItemsTable

Specifies the list of items returned by the metric sampling.

Same as the dynamic parameter: $ITEMS

Displayed in the list of items of the metrics list. For parent metrics, the list

...

contains also the sub-metrics.

...

Get
10Technology

Specifies the Technology name.

...

Same as the dynamic parameter: $TECHNOLOGY_

...

NAME

Get
11Machine

Specifies

...

the Machine name.

 

Same as the dynamic parameter: $SERVER_MACHINE_

...

NAME

Get
12AppTier

Specifies

...

the AppTier name.

 

Same as the dynamic parameter: $APPTIER_

...

NAME

Get
13Environment

Specifies

...

the Environment name.

 

Same as the dynamic parameter: $ENVIRONMENT_

...

NAME

Get
14MetricIDSpecifies the Metric ID name.

...

Get
15Returned value

Specifies the Returned value name.

...

Same as the dynamic parameter: $METRIC_

...

VALUE

Get
16Thresholds

Specifies

...

the Thresholds name.

...

Same as the dynamic parameter :

...

$THRESHOLDS

Get

MIB structure

The Alerts MIB structure complies with the Alerts SNMP Object Identifier (OID) structure. The OID of the Alerts Get requests for a specified metric is:

1.3.6.1.4.1.2608.1000.8.envId.techId.instId.metricId.field

Where field is the field number as specified in the metric fields table (previous table). You can identify this OID from the SNMP trap messages, using the  the $METRIC_TOKEN dynamic parameter.

SNMP trap operation

Using SNMP trap operations, you can automatically receive alerts in your SNMP server. The trap message contains critical information about the trap alert.

...

Alerts supports both SNMP message versions, SNMPv1 and SNMPv2. Alerts sends traps when a change occurs in a metric severity level, that is, when the metric state is changed between the following states: Critical, Near-Critical, Normal, and Unsampled.

Alerts trap message

The following is an example of an Alerts'SNMP trap message:

Trap(v1) received from host test.precise.com(10.42.136.103) at Nov 18, 2008 12:27 PM. Enterprise Oid:

.1.3.6.1.4.1.2608.1000.8.1079.1.1080.1199 (.iso.org.dod.internet.private.enterprises.2608.1000.8.1079.1.1080.1199) , Specific Type : 1, Trap Varbinds :

Object ID: .1.3.6.1.4.1.2608.1000.8.1079.1.1080.1199.7
(.iso.org.dod.internet.private.enterprises.2608.1000.8.1079.1.1080.1199.7) STRING: Availability

Object ID: .1.3.6.1.4.1.2608.1000.8.1079.1.1080.1199.14
(.iso.org.dod.internet.private.enterprises.2608.1000.8.1079.1.1080.1199.14) STRING: 1199

Object ID: .1.3.6.1.4.1.2608.1000.8.1079.1.1080.1199.8
(.iso.org.dod.internet.private.enterprises.2608.1000.8.1079.1.1080.1199.8)

STRING: ORCL

Object ID: .1.3.6.1.4.1.2608.1000.8.1079.1.1080.1199.10
(.iso.org.dod.internet.private.enterprises.2608.1000.8.1079.1.1080.1199.10) STRING: Oracle Object ID:
.1.3.6.1.4.1.2608.1000.8.1079.1.1080.1199.11

(.iso.org.dod.internet.private.enterprises.2608.1000.8.1079.1.1080.1199.11) STRING: server-name1

Object ID: .1.3.6.1.4.1.2608.1000.8.1079.1.1080.1199.12
(.iso.org.dod.internet.private.enterprises.2608.1000.8.1079.1.1080.1199.12) STRING: Oracle Object ID:
.1.3.6.1.4.1.2608.1000.8.1079.1.1080.1199.13 (.iso.org.dod.internet.private.enterprises.2608.1000.8.1079.1.1080.1199.13)
STRING: Default

Object ID: .1.3.6.1.4.1.2608.1000.8.1079.1.1080.1199.6
(.iso.org.dod.internet.private.enterprises.2608.1000.8.1079.1.1080.1199.6) STRING: test Precise trap

Object ID: .1.3.6.1.4.1.2608.1000.8.1079.1.1080.1199.1
(.iso.org.dod.internet.private.enterprises.2608.1000.8.1079.1.1080.1199.1)

STRING: test Precise trap

Object ID: .1.3.6.1.4.1.2608.1000.8.1079.1.1080.1199.15
(.iso.org.dod.internet.private.enterprises.2608.1000.8.1079.1.1080.1199.15) STRING: test Precise trap Object ID:
.1.3.6.1.4.1.2608.1000.8.1079.1.1080.1199.16 (.iso.org.dod.internet.private.enterprises.2608.1000.8.1079.1.1080.1199.16)
STRING: test Precise trap

Object ID: .1.3.6.1.4.1.2608.1000.8.1079.1.1080.1199.0
(.iso.org.dod.internet.private.enterprises.2608.1000.8.1079.1.1080.1199.0)

STRING: Test trap-message from Alerts

From the above table you can see that the Varbind Object ID for all the metrics of an Alerts trap starts with: 1.3.6.1.4.1.2608

The table below describes the SNMP trap structure. The abbreviated OID (Object ID) is the number after the last period on the varbinds table (as stated before, the rest of the number is the same for all varbinds).

Table 16-7    SNMP 7 SNMP trap structureDescription    Abbreviated Object

DescriptionAbbreviated object identifier (OID)

...

Metric    7

Instance    8

Technology    10

Machine    11

AppTier    12

Environment    13

Sampled on    6

Alert    1

Value    15

...

Metric7
Instance8
Technology10
Machine11
AppTier12
Environment13
Sampled on6
Alert1
Value15
Thresholds16
Message until v. 8.

...

00

The trap can be parsed with a commercial trap catcher according to the position of the varbinds or their OID. The following apply only to the last varbind on the table (OID=0):•    All

  • All the fields with the dollar sign ($) are dynamic parameters. Alerts translates these parameters before sending the SNMP trap.

...

  • Spaces inside items are converted to the underscore character (_) to allow saving the position.

To enable identification of the alerted metric's OID, required for the Get and Set requests, the SNMP action supports the following dynamic parameter:  $METRIC_TOKEN. This dynamic parameter is the MIB OID of the metric. In addition, consider the following:•    All

  • All items in the SNMP trap message keep their position, so you can access particular message items using built-in SNMP functions.

...

  • You can set all metrics of an instance to trigger SNMP actions through the Instances tab of the Settings dialog box.

See “Modifying instances association on the Instances tab” in the Precise Administration Guide.•    In

  • In case of parent metrics, Alerts sends an SNMP trap message only to the parent metric.

 

To cause the SNMP trap to act as in version 7.5, add the following parameter to the Alerts FocalPoint registry, and then restart the Alerts FocalPoint:

...