Patch Release V3.0 SP10

Included patch files

This V3.0 SP10 release contains three files:

• K-300SP10NEWR.SAR
• _NEWR_DATA_PROVIDERV3.10.SAP
• _NEWR_SLT_COLLECTORV3.10.SAP

Implementation procedures

Service pack installation and configuration

• Where to install: Deploy this service pack to client 000 of your Central Monitoring System.
• Configuration location: Perform all subsequent configuration tasks in the business client of your Central Monitoring System.
• Complete instructions: For step-by-step installation procedures, consult Installation Guide V3.0 (Appendix VIII: Install Service Pack) or Admin Guide V3.0 (Section: Install Service Pack).

Updates in this patch

BTP monitoring related updates

1. New BTP data providers:
   • NR_CF_AUDIT_EVENTS: Captures events generated by applications deployed on BTP subaccounts - Cloud Foundry Environment (Data Provider Type: Event).
   • NR_CLOUD_CONNECTOR: Health monitoring for SAP Cloud Connector (Data Provider Type: Event).
2. New utility: Utility to generate configurations for CloudALM-based data providers.

S/4 HANA and ECC related updates

1. New Monitoring Groups (/NEWR/DP_GROUP):
   • CF: Cloud Foundry
   • SAP_CC: SAP Cloud Connector
   • SLT: SAP Landscape Transformation Server
2. New data providers:
   • NR_SAP_CLIENT_MODIFIABLE: Event showing client modification setting in table T000.
   • NR_SAP_BGRFC_Q: Snapshot event of BGRFC Queues.
   • NR_SAP_LICENSE: Event of current SAP License status.
   • NR.SAP.GW.ERROR: Metric of gateway errors.
   • NR.SAP.GW.PERFORMANCE: Metric of gateway performance in terms of average XML size and response time.
   • NR.SAP.SLT.INFO: Collection of metrics that monitors SLT Processes.

Bug fixes

• Fixed a bug in data providers NR_SAP_SERVER_LIST and NR_SAP_INSTANCE_INFORMATION where they retry indefinitely if the monitored system does not have port 5XX13/5XX14 opened.
• Fixed a bug where join conditions are truncated in function module /NEWR/RFC_EVENTS_COLLECTOR_JN, which is used in data providers for complex table retrieval.

Enhancements

• Configuration table /NEWR/NRCONNECT: A new attribute for New Relic account name has been added to this configuration table.
• Data provider NR_CALM_LANDSCAPE: Performance improvements.

Collection manager updates

The Collection Manager now supports sending telemetry data through the BTP Integration Suite cloud integration.

Authorization role updates

Authorization role /NEWR/DATA_PROVIDER

Authorization role /NEWR/DATA_PROVIDER has been updated to add access to the following functions:

• /SDF/GET_USER_TYPE
• /SDF/IMA_DC_BGRFC_Q
• /SDF/IMA_DC_BGRFC_T
• /SDF/SLIC_READ_LICENSES_700
• RFC_SYSTEM_INFO
• New authorization object S_TABU_RFC with ACTVT = '03' (Display)

Additional authorization objects required for job spool retrieval, which is also used by data provider NR_SAP_CERTIFICATE:

Authorization role /NEWR/SLT_COLLECTOR

For the new SLT data provider, the remote RFC system user requires a special authorization object S_DMIS:

Manual configuration updates

BTP monitoring new data providers

NR_CF_AUDIT_EVENTS

This data provider captures events generated by applications deployed on BTP subaccounts - Cloud Foundry environment. It offers the flexibility to capture all events or specific events using the AUDIT_EVENTS parameter ID.

Configuration:

• Data Provider Function: /NEWR/CF_DATA_COLLECTOR
• Finisher Function: /NEWR/CF_AUDIT_FINISHER
• Monitoring Group: CF
• Credentials Storage Table: /NEWR/SEC_STORE

Prerequisite:

For Cloud Foundry, host authentication credentials cannot be stored in the SM59 RFC destination. They must be maintained in the New Relic credentials storage table /NEWR/SEC_STORE using transaction SM30.

This data provider comes pre-activated. Available parameters:

NR_CLOUD_CONNECTOR

This data provider captures health monitoring data for the SAP Cloud Connector instance.

Prerequisites:

• You must use basic authentication or form field authentication to read monitoring data via API. If certificate-based authentication has been configured for the Cloud Connector, a client certificate must be used instead.
• Users must be assigned to the sccmonitoring or sccadmin roles.

Configuration:

• Data Provider Function: /NEWR/CC_DATA_COLLECTOR
• Finisher Function: /NEWR/CC_FINISHER
• Monitoring Group: SAP_CC

This data provider comes pre-activated. Available parameters:

New utility to generate configurations for CloudALM-based data providers

Configuration:

• Transaction Code: /NEWR/GEN_DP_CALLID
• Program Name: /NEWR/GENERATE_CONFIG_CALLID
• Configuration table: /NEWR/CALLID_CNF

Prerequisites:

• Data provider NR_CALM_LANDSCAPE must be active and collecting data.
• The BTP services to be monitored must be linked to the data provider and maintained in table /NEWR/CALLID_INF using transaction SM30.

Limitation:

• Can only be used for data providers assigned to monitoring group CALM (SAP Cloud ALM).

Selection criteria:

Scope:

This utility allows you to add, change, delete, and automatically generate configurations for the selected data provider.

SAP HANA and ECC - New data providers

NR_SAP_CLIENT_MODIFIABLE

This is an event that captures the change in Client modification setting from table T000.

Configuration:

• Data Provider Function: /NEWR/RFC_EVENTS_COLLECTOR
• Finisher Function: /NEWR/EVENTS_FINISHER
• Monitoring Group: SAP_SYSTEM
• DP Period: 1 Day

This data provider comes pre-activated. Required parameters:

NR_SAP_BGRFC_Q

This data provider captures the snapshot of each BGRFC queue's locking status.

Configuration:

• Data Provider Function: /NEWR/SDF_IMA_DC_BGRFC_Q_EVENT
• Finisher Function: /NEWR/EVENTS_FINISHER
• Monitoring Group: SAP_APPL

This data provider comes pre-activated. Required parameters:

Output attributes:

Status code (STATE):

NR_SAP_LICENSE

This data provider monitors the current SAP license status, which can be used to create alerts on expired SAP licenses.

Configuration:

• Data Provider Function: /NEWR/LICENSE_EXPIRE_EVENT
• Finisher Function: /NEWR/STPI_FINISHER
• Monitoring Group: SAP_APPL
• Metric Type: Summary

This data provider comes pre-activated. Required parameters:

NR.SAP.GW.ERROR

This data provider extracts error counts for the SAP gateway.

Configuration:

• Communicator Function: /SDF/E2E_DISPATCHED_COLLECTOR
• Data Provider Function: /SDF/E2E_GW_ERROR_LOG
• Finisher Function: /NEWR/STPI_FINISHER
• Monitoring Group: SAP_APPL
• Metric Type: Summary

This data provider comes pre-activated. Required parameters:

NR.SAP.GW.PERFORMANCE

This data provider has two metrics for gateway performance:

Configuration:

• Communicator Function: /SDF/E2E_DISPATCHED_COLLECTOR
• Data Provider Function: /SDF/E2E_GW_PERF
• Finisher Function: /NEWR/STPI_FINISHER
• Monitoring Group: SAP_APPL
• Metric Type: Summary

This data provider comes pre-activated. Required parameters:

NR.SAP.SLT.INFO

This data provider provides the following metrics for SLT monitoring:

Metric output:

Traffic lights (Rating):

• 0: Not active
• 1: Green
• 2: Yellow
• 3: Red

Configuration:

• Data Provider Function: /SDF/E2E_SLT_INFO
• Finisher Function: /NEWR/STPI_FINISHER
• Monitoring Group: SLT
• Metric Type: Gauge

This data provider comes pre-activated. Required parameters:

Collection manager updates

Data transmission to New Relic

The Collection Manager program now supports sending data to New Relic using SAP Cloud Integration (SAP CPI) as middleware.

Configuration steps

1. Select iFlow authorization type: Choose the authorization method you'll use: ClientId/Secret, Certificate, or External Certificate.
2. Create a service instance for SAP Process Integration Runtime and assign either a service key or certificate based on your selected authorization method.
3. Use the New Relic-provided iFlow as a starting point. Customize it to meet your requirements, ensuring the authorization method is configured and the iFlow is deployed as an endpoint.
4. Create an RFC destination (SM59) using the service key or certificate generated in the previous step along with the iFlow endpoint destination.
5. Configure the Collection Manager program to use this iFlow endpoint for transmitting data to New Relic.

Integration flow

Prerequisite:

If you create a custom version of the iFlow, ensure the following mappings are included:

iFlow setup:

1. Configure Allowed headers to include API-Key|targetURL.

2. Configure the Authorization Method based on your selected iFlow authorization type:
   • For ClientId/Secret or Certificate authorization, select User Role.

• For External Certificate authorization, select Client Certificate and add the root certificates in the designated section.

3. Configure the Request content modifier to store exchange properties.

4. Add Groovy Script to dynamically set the headers coming to iFlow.

import com.sap.gateway.ip.core.customdev.util.Message;
def Message processData(Message message) {

message.setHeader("API-Key", message.getProperty("apikey"));
message.setHeader("Content-Type", "application/json");
message.setHeader("Accept", "application/json");

message.setHeader("CamelHttpUri", message.getProperty("targeturl"));

def turl = message.getProperty("CamelHttpUri", String);


def logText = "---Headers---\n";

message.getHeaders().each { k, v -> logText += "${k} = ${v}\n" };
messageLogFactory.getMessageLog(message)?.addAttachmentAsString("AllHeaders", logText, "text/plain");

messageLogFactory.getMessageLog(message)?.addAttachmentAsString("URL", turl, "text/plain");
}

5. Use Response content modifier to hold the message header/body.

6. Update the New Relic response HTTP connection.