Overview
The SAP Alert Notification service for SAP BTP provides a central service for receiving, filtering, and delivering alerts and notifications from SAP BTP services, applications, and custom event providers. It can be used to monitor availability, performance, errors, and operational events across SAP BTP environments and route those notifications to external systems.
The PowerConnect Cloud agent collects alert notification events from the SAP Alert Notification service and sends them to the target platform for monitoring, reporting, and alerting.
Data Collected
Alert severity
Alert category
Alert subject and body
Alert source
Resource and service information
Event timestamps
Event tags and properties
Alert status and metadata
APIs Used
SAP Alert Notification service REST APIs
Credential management / OAuth client credentials for API access
Status
Generally Available
Configuration
Get API User Details
PowerConnect Cloud requires access to the SAP Alert Notification service API to extract alert notification data. The most secure way to do this is to create or use a service binding / service key for the SAP Alert Notification service instance in your SAP BTP tenancy. This provides OAuth client credentials that PowerConnect Cloud can use to authenticate against the service API.
To do this, follow the steps below for your environment:
-
Login to the SAP BTP Cockpit.
-
Navigate to your subaccount.
-
Under Services → Instances and Subscriptions, find your Alert Notification service instance.
-
Open the service instance and create or view the service binding / service key credentials.
-
Note down the following values:
-
url -
clientid -
clientsecret -
identityzone -
uaadomain
-
Depending on the SAP BTP cockpit version and service plan, these values may be shown under the service key, service binding, or credentials section.
Adding the Alert Notification Input to PowerConnect Cloud
-
Login to the PowerConnect Cloud web UI.
-
Click on the Inputs link in the menu bar.
-
Click the + button to add a new Input.
-
Choose alerts-cf under BTP Platform.
-
Fill in the details on the form using the API authentication values from the step above.
-
Fill in the System ID.
The System ID maps to the
sourcefield in Splunk/Dynatrace and is used by dashboards to group related events. -
Choose the Splunk output you wish to send the Alert Notification data to.
-
Click Save.
The Input is now created.
Configuration Options
|
Configuration |
Description |
Required |
Default Value |
Comments |
|---|---|---|---|---|
|
How frequently to poll for new data in seconds |
How often the input will check for new alert notification data |
True |
60 seconds |
|
|
Unique Identifier for the Input |
A unique ID for the input |
True |
Spaces are not allowed |
|
|
Friendly name for the Input |
Friendly name for the input |
True |
|
|
|
System ID |
System ID or SID of the system. The value of this field will be mapped to the source field in Splunk and is used in dashboards for grouping related system events |
True |
|
|
|
Lag in Seconds |
How far behind the input will lag in seconds |
True |
60 |
This setting is to deal with SAP APIs that sometimes lag behind under high load |
|
Enable Data Collection |
Enable / Disable the Input |
True |
True |
|
|
SAP BTP platform host |
SAP BTP platform host |
True |
|
|
|
Identity zone |
Identity zone |
True |
|
|
|
Client Id |
Client Id of the Alert Notification service API user |
True |
|
|
|
Client Secret |
Client Secret/password of the Alert Notification service API user |
True |
|
|
|
Page Size |
Number of records to return in a single API call |
False |
100 |
|
|
Filter by severity |
|
False |
|
|
|
Filter by category |
|
False |
|
|
|
Filter by event type |
|
False |
|
|
|
Filter by resource name |
|
False |
|
|