Redpeaks V6.8
Trouble shooting
Monitors Guide
Sidebar
products:promonitor:6.8:monitorsguide:netweaver:instancesavailability
Book Creator
Add this page to your book
Add this page to your book Book Creator
Remove this page from your book
Remove this page from your book 
Manage book (
Help Table of Contents
Instances availability
This monitor is dedicated for surveillance of ABAP application servers (AS). It will send an alarm if an AS cannot be reached, if it is not registered on the message server or if is has been restarted.
Configuration hints
- You need to define the expected AS in the surveillance table (Use autodetect) and set the appropriate levels of severity.
- If an unexpected AS is found, the monitor will also generate an alarm.
- Response time alert(s):
- Use the multi-threshold syntax to set multiple threshold/severity associations: G2W:1 W2M:2 M2C:3 (Green To Warning, Warning To Major, etc…), expressed in second, an alarm of the corresponding severity will be sent if time eapsed from last query is over threshold. Set 0 in the field if unused
Atomic fields
| Send metadata | Send collected instance information as metadata |
|---|---|
| Response time alert | The threshold for the elapsed time of query. You can use the multi threshold syntax (i.e. : G2W:30 W2M:45 M2C:50) |
| Query Time-out | Maximum duration in seconds of waiting before a query times out and an alert is sent |
| Severity unexpected instance | Severity of the alarm to send if an unexpected instance is found |
Surveillance table
| Parameter | Description |
|---|---|
| Mandatory | If checked, the instance must be registered and responding. |
| Instance name | The expected instance : [HOST]_[SID]_[NUMBER] , * can be used for select ALL |
| Availibility severity | The severity of the alarm sent if the AS is not responding. |
| Restart Severity | The severity of the alarm sent if the AS is restarted. |
| Auto clear | If checked, the alarm will be cleared as soon as the alarm condition is not met anymore. |
| Alarm tag | This field allows to add custom text within the alarm message. %MSG% variable will contain the actual generated message and can be used such as: “my_prefix %MSG% my_suffix”. By default, tag will be used as prefix. |
| Alarm | Enable of alarm sending |
| Metric | Enable for metric sending |
Examples
| Mandatory | Instance name | Availibility severity | Restart Severity | Auto clear | Alarm tag |
|---|---|---|---|---|---|
| true | mysap_PRD_00 | CRITICAL | WARNING | true |
Effect : Send a CRITICAL alarm if instance mysap_PRD_00 is not responding, and a WARNING if it is restarted.
Examples
| Mandatory | Instance name | Availibility severity | Restart Severity | Auto clear | Alarm tag |
|---|---|---|---|---|---|
| false | mysap_PRD_01 | CRITICAL | DISABLED | true |
Effect : Ignore the fact that the instance is not responding or registered, ignore if restarted. The purpose of this line is to declare expected instances, so the probe can detect *unexpected* instances
Generated metrics
| metricId | metricUnit | metricTarget | metricDescription |
|---|---|---|---|
| INSTANCE_AVAILABILITY | Status | INSTANCE | Sends TRUE if the instance is available, FALSE instead. |
/home/clients/8c48b436badcd3a0bdaaba8c59a54bf1/wiki-web/data/pages/products/promonitor/6.8/monitorsguide/netweaver/instancesavailability.txt · Last modified: 2024/07/25 14:52 by jtbeduchaud
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
