SAP release notes release notesRSS

Included patch files

This V3.0 SP11 release contains three files:

• K-300SP11NEWR.SAR
• _NEWR_DATA_PROVIDERV3.11.SAP
• _NEWR_COLLECTION_MANAGER.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. NR_BTP_UDM: Provides SAP Usage Data Management events for SAP BTP. Gathers, stores, and makes usage information available for all services and applications across all regions in a cloud deployment for central analysis, reporting, and license auditing (Data Provider Type: Event).
2. NR_CLOUD_CONNECTOR: Enhanced to include a new numerical attribute DAYS_TO_EXPIRE for the event table NR_CLOUD_CONNECTOR_CERT. This attribute identifies remaining days before certificate expiration in Cloud Connector.
3. API-based data providers: Added certificate expiration checks in /NEWR/API_DATA_COLLECTOR data provider function module. Compiles all certificates available in STRUST (under SSL Client Standard or SSL Client Anonymous) and matches them against the target host of the respective RFC destination. When a match is found, the valid-to date is checked. An error is thrown stating "The certificate is expired for the host <host_name>" when an expired certificate is detected during data provider execution.

S/4 HANA and ECC related updates

1. HANA DB data providers: Enhanced /NEWR/AGENT_HDB and /NEWR/AGENT_HDB_EVENT function modules to handle query statements that use aliases for table names.
2. Background RFC Q data provider: New data provider NR.SAP.BGRFC.Q for monitoring background RFC queues.
3. IDoc data provider: Updated NR_SAP_IDOC to include partner IDoc ID.
4. System memory data provider: Updated NR.SAP.SYSTEM.MEMORY.HEAP_USAGE - changed parameter MTE_CLASS to R3MemMgmtHeapAct.
5. Connection issue handling: Protection triggered by temporary connection issues no longer requires manual intervention to clear.
6. HANA Sidecar support: Bug fix allows HANA Sidecar to be added as a monitored system without specifying the RFC destination.
7. New Relic account parameter: Bug fix ensures the NR_ACCID parameter in New Relic data providers is not overridden when new monitored system configuration is generated.

Updated HANA data providers

NR.SAP.HDB.METRICS: Enhanced to include two new data points:

• NUM_CONNECTIONS: Shows number of connections by status
• THREADCNT: Shows active thread counts

New HANA data providers

1. NR_SAP_HDB_BACKUP_BROKEN: Captures HANA backup history broken information (Event)
2. NR_SAP_HDB_BLKED_TRANS: Provides snapshots of HANA blocked transactions (Event)
3. NR_SAP_HDB_LICENSES: Monitors HANA license information (Event)
4. NR_SAP_HDB_LONG_TRANS: Tracks long running transactions (Event)
5. NR_SAP_HDB_PWD_EXPIRE: Shows users with expiring passwords (Event)
6. NR_SAP_HDB_THREADS: Captures long running thread information (Event)

Bug fixes

1. RFC check program: Updated /NEWR/REGISTRY_RFC_CHECK with improved functionality.
2. Payload data gap: Fixed bug causing data gaps in payload data for data provider NR_SAP_ABAP_WS.
3. Expensive statement traces: Fixed issue where expensive statement spans were not shown in New Relic traces for programs accessing HANA database.

Manual configuration updates

Upgrade from SP10 to SP11 with existing CloudALM data providers

If CloudALM-based data providers are configured in SP10, add a new CALM_LMS system to monitored systems after upgrading to SP11. During upgrade, after completing "Copy Template Tables from Client 000", proceed to "Define the Monitored Systems" and add:

New RFC check program

The RFC check program has been updated with a maximum wait time to receive responses from each destination.

Results now include latency measurements from each destination.

Authorization role updates

Authorization role /NEWR/DATA_PROVIDER

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

• SREL_GET_NEXT_NEIGHBORS

Authorization role /NEWR/COLLECTION_MANAGER

This role is created specifically for the batch user on the central monitoring system to run collection manager jobs.

New data providers for ABAP business systems

NR_SAP_HDB_BACKUP_BROKEN

Captures HANA DB backup broken history events.

Configuration:

• Data Provider Function: /NEWR/AGENT_HDB_EVENT
• Finisher Function: /NEWR/EVENTS_FINISHER
• Monitoring Group: HANA_DB
• DP Period: 1 Hour

This data provider comes pre-activated. Required parameters:

Output attributes:

NR_SAP_HDB_BLKED_TRANS

Captures blocked transactions in HANA DB events.

Configuration:

• Data Provider Function: /NEWR/AGENT_HDB_EVENT
• Finisher Function: /NEWR/EVENTS_FINISHER
• Monitoring Group: HANA_DB
• DP Period: 5 Minutes

This data provider comes pre-activated. Required parameters:

Output attributes:

NR_SAP_HDB_LICENSES

Captures HANA DB license information events.

Configuration:

• Data Provider Function: /NEWR/AGENT_HDB_EVENT
• Finisher Function: /NEWR/EVENTS_FINISHER
• Monitoring Group: HANA_DB
• DP Period: 5 Minutes

This data provider comes pre-activated. Required parameters:

Output attributes:

NR_SAP_HDB_LONG_TRANS

Captures long running transactions in HANA DB events.

Configuration:

• Data Provider Function: /NEWR/AGENT_HDB_EVENT
• Finisher Function: /NEWR/EVENTS_FINISHER
• Monitoring Group: HANA_DB
• DP Period: 5 Minutes

This data provider comes pre-activated. Required parameters:

Output attributes:

NR_SAP_HDB_PWD_EXPIRE

Captures expiring user password events.

Configuration:

• Data Provider Function: /NEWR/AGENT_HDB_EVENT
• Finisher Function: /NEWR/EVENTS_FINISHER
• Monitoring Group: HANA_DB
• DP Period: 1 day

This data provider comes pre-activated. Required parameters:

Output attributes:

NR_SAP_HDB_THREADS

Captures long running threads in HANA DB events.

Configuration:

• Data Provider Function: /NEWR/AGENT_HDB_EVENT
• Finisher Function: /NEWR/EVENTS_FINISHER
• Monitoring Group: HANA_DB
• DP Period: 5 Minutes

This data provider comes pre-activated. Required parameters:

Output attributes:

BTP monitoring new data providers

NR_BTP_UDM

Provides SAP Usage Data Management events for SAP BTP. Gathers, stores, and makes usage information available for all services and applications across all regions in a cloud deployment. This information supports central analysis, reporting, and license auditing.

Prerequisite:

RFC destination must be configured to handle authentication. Uses BASIC authentication based on Client ID and Client Password.

Configuration:

• Type: Event (API)
• Data Provider Function Module: /NEWR/API_DATA_COLLECTOR
• Finisher Function Module: /NEWR/BTP_UDM_FINISHER
• Monitoring Component: BTP_UDM

This data provider comes pre-activated. Required parameters:

Setup instructions:

To get details for API_HOST, Authentication URL, Client ID, and Password:

1. Create a Service Instance for Usage Data Management Service with plan reporting-ga-admin.
2. Create a service key - it will contain the necessary details.
3. Base URI format: https://uas-reporting.cfapps.<landscape domain>/reports/v1

Transport details

SAP transport SD1K901231 delivered in two files:

• K901231.SD1 (co-file)
• R901231.SD1 (data)

Enhancements

NR_CALM_LANDSCAPE event

The NR_CALM_LANDSCAPE event is enhanced to include the client endpoints (if any) configured in the system. This does not apply for SAP PaaS/SaaS based services. Example: If your SAP instance has 3 clients - 100, 200, 300... then a separate LMSID would be generated for each one of them.

Required action: Change the monitoring component for this DP from CALM to LANDSCAPE in the DP Registry transaction.

NR.CALM.HM event

The NR.CALM.HM event is enhanced to send the relevant metrics based on the org_name to respective NR accounts of the org unit. This enhancement will be applicable only for serviceType = SAP_CPI and for metrics (CPI.JMS.Queue.Active, CPI.JMS.Queue.Status, CPI.JMS.Queue.Message.Number)

New attribute - ORG_NAME: org_name used as filter for metric names. Add this field to the template table (/NEWR/DP_SELOPTIN) using SM30.

NR_CALM_IS_MPL data provider

The NR_CALM_IS_MPL data provider now requires a new parameter_id SERVICE_TYPE to differentiate between the IS CPI and MACO instances. Add this field to the template table (/NEWR/DP_SELOPTIN) using SM30.

Program updates

The /NEWR/SYS_GENERATE_DELIVERY program is enhanced to exclude the monitoring component CALM related data provider from generation of Call ID configuration. Instead use the program /NEWR/GEN_DP_CALLID for monitoring component CALM.

The /NEWR/GEN_DP_CALLID program is enhanced to update the new attributes added to the Registry Configuration table.

Fixes

Issue: The NR_CALM_LANDSCAPE data provider does not transmit all systems configured in the Cloud ALM tenant.

Resolution:

• /NEWR/ABAP_COLLECTION_MANAGERN (program) - When data providers are submitted for parallel processing and if there is a resource constraint of WP, then that particular DP is skipped for data collection. Now we have enabled the retry mechanism.

• /NEWR/REGISTRY (Tcode) - When we generate the Call ID for a new monitored system, the previously suspended data provider is re-activated again.

Transport details

SAP transport SD1K901229 delivered in two files:

• K901229.SD1 (co-file)
• R901229.SD1 (data)

Fixes

Issue: One of the standard SAP delivered data elements (DMC_GUID) referenced in the New Relic code does not exist in some customer SAP systems. This impacted the SLT replication data providers.

Resolution: Created a copy of this data element in the New Relic namespace.

Transport details

SAP transport SD1K901215 delivered in two files:

• K901215.SD1 (co-file)
• R901215.SD1 (data)

Enhancements

The NR_SAP_IDOC event is enhanced by including information about related IDocs from partner systems. This creates a link between the current IDoc and the corresponding IDoc(s) in other systems.

New attributes added:

• Partner_IDOC: Stores the IDoc number from the connected partner system.
• Partner_IDOC_LOGSYS: Identifies the logical system of the partner.
  • Outbound IDoc: The logical system of the sending partner.
  • Inbound IDoc: The logical system of the receiving partner.
• Role ID, Role Type, hops: These fields are populated by the SAP Object Relationship Service to define the nature of the relationship.

Example values:

Fixes

Issue: Formatting issue on timestamp when IDoc payload is retrieved.

Resolution: Fixed timestamp formatting.

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.

Included patch files

This V3.0 SP9 release contains two files:

• K-300SP09NEWR.SAR
• _NEWR_DATA_PROVIDERV3.9.SAP

Implementation procedures

Installation and configuration steps

• 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).

Authorization role changes

• An updated authorization role is included in the file _NEWR_DATA_PROVIDERV3.9.SAP.
• More information: See the Authorization role changes section below.
• Required action: Apply this role file to update RFC user authorization profiles across all monitored systems.
• Note: The file _NEWR_DATA_PROVIDER.SAP has also been updated to ensure fresh installations automatically include the new authorization objects.

What's new in this release

This service pack delivers several enhancements:

• Backup and Restore capabilities in the Registry transaction (/NEWR/Registry)
• Selective registry configuration generation for specific monitored systems

For detailed usage guidance, see the New feature instructions section.

Changes in this release

BTP monitoring enhancements

• Pagination is now supported for BTP and CALM API data provider functions.
• Enhanced pagination for NR_BTP_IS_MPL:
  • New finisher function: /NEWR/BTP_MPL_FINISHER_V2
  • New parameter API_PAGINATION_LIMIT with a default value of 500. The SAP API supports up to 1000 records per call.
• Updated query for NR_CALM_LANDSCAPE data provider: The API_QUERY now includes ?limit=999. This adjustment addresses a change in the SAP CALM API, which now returns only 100 records by default. The new limit enables more efficient data collection.

Additional changes

Enhanced functionality

• Flexible data provider configuration: Generate or remove data provider configurations for selected monitored systems.
• Registry backup and restore: New capabilities for backing up and restoring the Data Provider Registry.
• Extended resend program support: The resend program (/NEWR/RESEND_FAILED_API_TRANS) now handles the API_TRACE data provider type.

Performance improvements

• Enhanced payload retrieval for NR_SAP_ABAP_WS: The NR_SAP_ABAP_WS data provider can now retrieve attributes from Node Only tags, improving data processing efficiency.
• Expanded job logging: The collection manager job (/NEWR/ONE_COLLECTION) now provides more detailed messages in job logs for better execution tracking.

Resolved issues

• Fixed IDoc timestamp bug: Corrected a timestamp error in the NR_SAP_IDOC data provider.
• Security role correction: Updated the /NEWR/DATA_PROVIDER security role to resolve authorization issues affecting NR.SAP.LOG.GW and NR.SAP.LOG.AUDITLOG data providers.

Authorization role changes

The /NEWR/DATA_PROVIDER authorization role now includes these objects:

• Transaction SM20: Enables Audit Log retrieval
• Transaction /IWFND/VIEW_LOG: Enables Gateway Log retrieval for backward compatibility

New feature instructions

Service pack deployment procedure

To deploy a New Relic Service Pack, complete these steps:

• Deploy the Service Pack file:
  1. Access client 000 of the Central Monitoring System
  2. Apply the Service Pack file using transaction SPAM
• Transfer configuration templates:
  1. Access the business client of the Central Monitoring System
  2. Navigate to menu /n/NEWR/INSTALL
  3. Select Copy Template Tables from Client 000
• Create configurations for new data providers:
  1. Select Generate Configurations for New Data Providers to create delta configurations for the Service Pack

Generating configurations for specific monitored systems

Three new configuration fields are now available to improve registry configuration control:

Available fields:

• Process option: Choose between Generate or Remove operations
• Configuration generation based on: Choose your generation method:
  • Monitored System ID
  • Data Provider Name

How to use:

• When using Monitored System ID: Input the System ID for the newly added Monitored System, then click Execute to regenerate data provider configurations.

• When using Data Provider Name: Input the Data Provider Name or Monitoring Group (wildcards are supported), then click Execute to regenerate data provider configurations.

For repeat installations, you may encounter a confirmation dialog. Select Yes to proceed. A status bar message will confirm successful completion.

Updating configuration templates

We recommend updating configuration templates only for new custom data providers rather than using the Update Configuration Templates option from the installation menu to update all templates.

Recommended approach:

• Create backups before making configuration changes
• Apply template updates only to data providers needed for newly onboarded systems

Template update procedure:

1. Launch program /NEWR/REP_INSTALL_REPLACING using transaction SE38
2. Keep "Transfer Stage" at 0 (do not modify)
3. Enter only the data provider template from registry entries that requires updating

This targeted method modifies only necessary templates, optimizing the update process and reducing the risk of disrupting existing configurations.

Configuration backup and restore

The Registry transaction (/NEWR/REGISTRY) now includes backup and restore functionality that improves configuration management. These features support both individual and comprehensive backup and restoration operations for data provider configurations.

Feature overview:

Registry backup and restore operations (/NEWR/REGISTRY)

When in change mode, you can access:

• Backup One: Creates a backup for a single selected data provider configuration.
• Backup All: Creates a backup for all active data provider configurations.
• Restore One: Restores a single data provider configuration from any previously created backup (from either Backup One or Backup All).
• Restore All: Restores all data provider configurations from a Backup All backup.

These operations are accessible through the Table View menu in Change Mode.

Management features

• Descriptive comments: Add comments when creating backups to help identify backup versions later.
• Version history: Select from previously created backup versions when restoring configurations.
• Restoration controls: After choosing a backup version, you can:
  • Restore: Start the restoration process immediately.
  • DP header from backup: Review the Data Provider's technical settings from the backup, including function names and frequencies.
  • DP configuration from backup: View the configuration parameters saved in the backup.

These capabilities offer improved control over New Relic configuration management, simplifying recovery from unintended modifications and facilitating efficient updates.

Patch files

V3.0 SP8 contains one file:

• K-300SP08NEWR.SAR

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

• New data provider NR_CALM_RUM_TRACE. This data provider sends Real User Monitoring Trace data to New Relic.

Bug fixes

• Updated NR_SAP_ABAP_WP to fix a bug that limited Tag Name to only 30 characters. The tag name now matches the SAP standard data structure of 60 characters.

Patch files

V3.0 SP7 contains one file:

• K-300SP07NEWR.SAR

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).
• This service pack includes an enhancement to data provider NR_SAP_ABAP_WS. If you want to customize this data provider, see the Manual configuration steps for instructions.

Updates in this patch

BTP monitoring related updates

• The BTP/CALM API Host can now be accessed via the same proxy server configured for the Authentication HTTP destination. This enhancement is useful when the Central Monitoring System requires a proxy server to access BTP and/or CALM API endpoints.
• The BTP/CALM service identifier attribute (SOURCE_ACCT) is now exported when telemetry data is sent to New Relic. This enhancement is useful when monitoring multiple BTP/CALM accounts.

Other updates

• Updated NR_SAP_ABAP_WP to allow retrieval of all data and attributes under a Node Only tag.
• Fixed a bug in NR_SAP_JOB_ALL where the timestamp for unfinished jobs was using local time as UTC time.
• Fixed bugs in the Test function of the registry.
• Added new configuration parameter BYPASS_PARA_ID for skipping configuration parameter pattern recognition when updating the configuration template. This prevents word strings in certain parameters, such as API_PATH and API_QUERY, from being recognized as SYS_ID.

Manual configuration steps

Configure NR_SAP_ABAP_WS to retrieve XML payload tags

Data Provider NR_SAP_ABAP_WS is designed with the capability to retrieve values from payload web service XML tags. Previously, only data type or attribute type tags could be retrieved. This service pack allows Node type tags to also be specified for retrieval.

The payload tag to be extracted is configured using the configuration parameter TAG_LIST. Here is an example:

In previous versions, only data or attribute tag names could be configured for retrieval. Here is an XML fragment:

<NodeTag Attribute = Attribute_value>
<DataTag> Data_value </DataTag>
</NodeTag>

To retrieve the data from the XML, the TAG_LIST is configured with the value: Attribute;DataTag.

Then the NR_SAP_ABAP_WS event will have these attributes:

• Attribute: Attribute_value
• DataTag: Data_value

Now the TAG_LIST can be configured as NodeTag. In this case, the event attributes are as follows:

• NodeTag_Attribute: Attribute_value
• NodeTag_DataTag: Data_value

Overview

This service pack introduces a series of API-based data providers for monitoring SAP BTP/CALM accounts.

New data collection authentication method for BTP Integration Suite API Management

• SP06 introduces a new data collection authentication method using API Management, API Portal, in addition to the two authentication methods introduced in SP05.
• This option requires a subscription to the API Management, API Portal service with the apiportal-apiaccess plan.
• Your BTP Global Account Administrator can subscribe to this service under Entitlements > Service Assignments.

Patch files

V3.0 SP6 contains one file:

• K-300SP06NEWR.SAR

Updates in this patch

BTP monitoring related updates

New data providers

SP06 adds new data providers for BTP monitoring and enhances existing BTP data providers:

• NR_BTP_IS_APIMGMT: Data provider to retrieve BTP integration suite API Management logs. This data provider is assigned to Monitoring Group BTP_APIM. The New Relic event generated from this data provider is NR_IS_APIM_LOG.
• NR.CALM.HM: Data provider to retrieve all Health Monitoring (HM) data via CloudALM HM API. This data provider is assigned to Monitoring Group CALM. The metric generated from this data provider can be identified using dp_name = NR.CALM.HM.
• NR.CALM.JAM: Data provider to retrieve all Job and Automation (JAM) data via CloudALM JAM API. This data provider is assigned to Monitoring Group CALM. The metric generated from this data provider can be identified using dp_name = NR.CALM.JAM.
• NR.CALM.RUM: Data provider to retrieve all Real User Monitoring (RUM) data via CloudALM RUM API. This data provider is assigned to Monitoring Group CALM. The metric generated from this data provider can be identified using dp_name = NR.CALM.RUM.

Bug fixes and enhancements

• Fixed duration calculation and missing RETRY data issue in data provider NR_BTP_IS_MPL.
• Added test functionality for API_METRIC data providers to display output as JSON from the Registry screen.

Other updates

• Updated testing features in New Relic Registry. OTel API-based metrics can now display results in JSON format when tested from Registry.
• The protection feature, which stops data providers with remote errors, can now be enabled or disabled via a global configuration parameter.
• Enhanced all trace data provider function modules /NEWR/SAP_WORKLOAD_TRACE* to truncate the EID namespace based on expressions (parameter ID: EID_EXCLUDE_EXPR) stored in registry configuration.