SAP BTP, Neo environment
Available Monitoring Content
| Category | Type | Description |
|---|---|---|
| Java Application Logs | Exceptions | Collects exceptions in Java Logs for applications running in SAP Business Technology Platform |
Connect SAP BTP, Neo environment
To perform the necessary setup steps to connect SAP BTP Neo environment to SAP Cloud ALM, please refer to:
Setup Integration & Exception Monitoring
Activate Monitoring and Alerting
Because you have to choose the correct end-point for each of the categories in SAP BTP, Neo environment you have to activate the monitoring manually.
- Open the Integration & Exception Monitoring application from the launchpad
- Open the scope selection via the target icon in the upper right corner
- Change the drop-down for Display Service to "All"
- Make sure to select your cloud service in the scope
- Click the rack-wheel icon in the upper right corner to access the configuration
- Expand the Configuration panel
- In the configuration panel, click on the name of the cloud service
- The "Configuration of Services" screen opens
- In the "Configuration for Services" screen, click the > button at the end of the line for the cloud service you want to change
Adjust Monitoring Categories
- Use the toggle button in the column Active to turn the monitoring category "Java Application Logs" ON or OFF
Adjust Alerting
- Use the toggle button in the column Active to turn a standard alert ON or OFF
- Press the > button at the end of the line to access the detail setup for an existing alert or use the + button to create a new alert
- Adjust the display name if desired
- Expand the Filter Configuration tray
- Enter a filter name
- Select the filter category
- Maintain the available filter fields (see details below)
Available Alerts for SAP BTP, Neo environment
- Erroneous Java Application
Available Filter Fields for SAP BTP, Neo environment
The filter fields depend on the monitoring category the alert is created for and additional on the filter category, if there is more than one available.
Java Application Logs
- Application: Application Name
- Logger: This field usually contains the area and the application name to identify the origin of the logged problem. Supports wildcards (e.g. com.sap*)
- Message: Error text of the exception. Supports wildcards (e.g. Failed*cache)
- Passport ID: The passport of the exceptions
- Runtime: Runtime of the application (e.g. java or html5)
- Severity: Comma-separated list of the severity of the exceptions (e.g. ERROR, FATAL)
- Tenant: The account or sub-account ID for the exception
- User: The user who triggered the exception