SAP monitoring release notes

SAP monitoring

Wed, 09 Oct 2024 00:00:00 +0000

Patch overview

Patch files

v3.0 SP1 has one patch file for ABAP:

K-250SP03NEWR.SAR

The patch also includes a new role file:

_NEWR_DATA_PROVIDER V3.1.SAP

Updates in this patch

New data providers

SAP Workload monitoring data providers

The main feature enhancement for SP1 is data providers from SAP Workload Monitoring (Transaction ST03N). SAP Workload Monitor uses the SAP performance database to analyze the ABAP kernel's workload and performance. It has many views, such as Workload Overview, Task Profile, Top Long Running Dialog Programs, etc.

Standard SAP function SWNC_GET_WORKLOAD_SNAPSHOT is called every 5 minutes to take performance database snapshots by two main data providers:

NR_SAP_WORKLOAD_COMPLETE (Event)
NR.SAP.WORKLOAD.COMPLETE (Metric)

These retrieve snapshot data and transmit to New Relic with sub-events and sub-metrics.

Data providers and ST03 analytics views:

Data provider name

ST03 analytics view

Data provider type

Internal table name

NR.SAP.WORKLOAD.OVERVIEW

Workload Overview

sub-metric

TASKTYPE

NR_SAP_WORKLOAD_OVERVIEW

Workload Overview

sub-event

TASKTYPE

NR_SAP_TRANSACTION_PROFILE

Transaction Profile, Standard

sub-event

TIMES

NR.SAP.TASKTIME

Time Profile

sub-metric

TASKTIMES

NR_SAP_TIME_PROFILE

Time Profile

sub-event

TASKTIMES

NR_SAP_TOP_DIALOG

Ranked Top 25 Program Dialog Response Time

sub-event

HITLIST_RESPTIME

NR_SAP_TOP_DB_ACCESS

Ranked Top 25 Database Access Response Time

sub-event

HITLIST_DATABASE

NR_SAP_USER_PROFILE

User Statistics: User Profile

sub-event

USERWORKLOAD

NR_SAP_USER_TCODE

User Statistics

sub-event

USERTCODE

NR_SAP_FRONTEND

Frontend Statistics

sub-event

FRONTEND

NR_SAP_MEMORY

Memory Use Statistics

sub-event

MEMORY

NR_SAP_SPOOL_STATISTICS

Spool Statistics

sub-event

SPOOLACT

NR_SAP_WEB_CLINT_STATISTICS

Web Client Statistics

sub-event

WEBC

NR_SAP_WEB_CLINT_DESTINATION

Web Client Destination Statistics

sub-event

WEBCD

NR_SAP_WEB_SERVER_STATISTICS

Web Server Statistics

sub-event

WEBS

NR_SAP_WEB_SERVER_DESTINATION

Web Server Destination Statistics

sub-event

WEBSD

NR_SAP_RFC_CLIENT

RFC Client Profile

sub-event

RFCCLNT

NR_SAP_RFC_DEST_PROFILE

RFC Client Destination Profile

sub-event

RFCCLNTDEST

NR_SAP_RFC_SERVER

RFC Server Profile

sub-event

RFCSRVR

NR_SAP_RFC_SERVER_DEST

RFC Server Destination Profile

sub-event

RFCSRVRDEST

External outbound email data provider

This data provider (NR_SAP_EXTERNAL_OUTBOUND_EMAIL) extracts emails sent from SAP application server instance to an external address.

Bug fixes

This service pack fixes the following issues:

Trace sending incorrect span timestamps
The user who runs the collection job has to use the system time zone
The collection manager dumps when HANA expensive statement data provider is not configured
The RFC check program does not check New Relic endpoint HTTP destinations when the only monitored system is the monitoring system and RFC destination is set to 'NONE'

Manual configuration steps

There are a few data provider configuration changes that need to be manually done. Configuration changes can be performed using SAP transaction /n/NEWR/REGISTRY. Select the data provider in question and click on the "Configure" button to make the change.

Workload complete data providers configuration

The NR_SAP_WORKFLOW_COMPLETE and NR.SAP.WORKLOAD.COMPLETE data providers are shipped with SETTING_SWITCH parameters empty, therefore default values are used during execution. However, they can be adjusted for optimal performance:

SETTING_SWITCH parameter

This parameter allows a precise tuning of system settings to strike a balance of performance and system resource demands. If this parameter is not set, the default values are in force. There are multiple configuration options, which are combined and separated by semicolon:

Parameter

Description

Default value

FREE%=nn

Minimum percentage of free work processes over total work processes.

25(%)

MINFT#=nn

Minimum number of free WP, nn is 01 to 99. Between FREE% and MINFT#, if both specified, this data provider takes the higher number of free work process numbers as the limit.

MWAIT#=nn

Maximum waiting time (in seconds). If the data provider cannot secure enough free dialog work processes within the maximum waiting time, the collection RFC call is skipped. This might lead to a data gap.

MREC#=nnnnn

Maximum IDOC header to be retrieved in each RFC call to /SDF/IMA_DC_IDOC. If not all IDOC are retrieved in one call, more RFC calls will be initiated until the complete data set in the collection period is retrieved.

10000

JSEND#=nnnn

Maximum number of events sent to New Relic Cloud in each batch.

5000

DPWP#=nn

Maximum data provider work processes per user. When work process and memory limitations exist on the monitoring system ABAP servers, this parameter limits the maximum dialog work processes occupied by New Relic Monitoring for SAP. Run the New Relic Monitoring Collection Manager with a specific user ID to implement this limit. The total work processes used equals the number of WPs occupied by that user ID. If the data provider attempts to start work processes beyond this limit, it waits 1 second and retries until work processes become available or the maximum wait time is reached.

Not enforced if empty or missing

USER=user

The user ID that runs Collection Manager. If this parameter is empty or missing, the maximum data provider work process is not enforced.

Not enforced if empty or missing

External outbound email configuration

The NR_SAP_EXTERNAL_OUTBOUND_EMAIL data provider is normally shipped as suspended and runs wide open. However, we recommend setting filters before running. Possible filter parameters are:

EMAIL_SENDS

Specific email sender for monitoring can be enumerated here, separated by semicolon. Wildcard is not supported for this parameter.

EMAIL_STATUS

Enumerated statuses to be monitored, separated by semicolon. Leaving this parameter empty will monitor all email statuses. By default, these statuses are monitored: WAIT;TRANSIT;OK;ERROR;INCONS;FUTURE;RETRY;DIRECT;ACTIVE.

EMAIL_TITLE

Filter on emails' subject line. Wildcard * is supported for this parameter.

Security role update

Upload the new role file _NEWR_DATA_PROVIDER.SAP to the monitored systems for the new authorization required for the new data provider.

The following RFC functions are added to the RFC security object:

SX_SNDREC_SELECT

SAP monitoring

Wed, 25 Mar 2026 00:00:00 +0000

Included patch files

This V3.0 SP12 release contains one file:

K-300SP12NEWR.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

SP12 is a collection of New Relic Notes addressing bug fixes and new features:

NR 1344

New parameter AIF_TABLES for NR_SAP_AIF_ERROR allows retrieving error messages from tables other than /AIF/STD_IDX_TBL.

NR 12-02

Fixes issues and adds new features for API-based data providers:

Fixed code dump in /NEWR/API_DATA_COLLECTOR when API destination is not reachable
Fixed resource failure when extracting CALM Landscape Data
Fixed resource failure when extracting BTP Message Processing Log
Added validation for Service ID (LMSID) configured as CALL ID for all data providers under monitoring group CALM
Added certificate validity check before calling Data Collection API

NR 12-03

Implements collection delay and fixed data collection window for the collection manager and testing by call ID in registry.

NR 12-05

Implements the following enhancements:

Pagination support for data providers in CALM monitoring group
New program parameter to allow RFC check program to check a single RFC destination
Configuration to force data provider test only for a single call ID

Fixes the following issues:

Blank call ID on collection manager output
Credential validation issue for NR_CF_AUDIT_EVENTS

NR 12-06

New data provider NR_SAP_ABAP_WS_COMPLETE collects ABAP web service events.

Additional bug fixes

In addition to the above notes, SP12 also fixes the following issues:

Fixed timestamp issue with table retrieval data provider function modules /NEWR/RFC_EVENTS_COLLECTOR and /NEWR/RFC_EVENTS_COLLECTOR2
Added Transaction ID to IDoc events to facilitate linking to trace records

Manual configuration updates

Add new parameter to NR_SAP_AIF_ERROR

To configure the new AIF_TABLES parameter:

Apply the included transport to the Central Monitoring System.
Go to transaction /n/NEWR/REGISTRY.
Select data provider NR_SAP_AIF_ERROR and click Configure.
Add parameter AIF_TABLES and enter the table name specified in /AIF/T_IDX_TBL for the configured namespace/interface/version combination.

If AIF_TABLES is left blank or not specified, the index table defaults to the standard single index table /AIF/STD_IDX_TBL.

Configure collection delay and fixed collection window

Two new configuration fields have been added to the Data Provider Registry to address data gaps caused by floating collection boundaries and database latency.

New fields in data provider registry:

DATA_COLLECTION_DELAY: Specifies a purposeful delay in minutes to subtract from collection timestamps. This buffer ensures late-arriving data from database updates are captured before the collection window closes.
FIXED_SCHEDULES: Flag to enable fixed collection periods. When set to X, seconds are stripped from collection timestamps to create consistent, predictable collection windows.

How it works:

Fixed Schedules (FIXED_SCHEDULES = 'X'):

Collection timestamps are normalized by removing seconds.
Example: 12:12:23 becomes 12:12:00.
Creates consistent, aligned collection boundaries across all collections.

Data Collection Delay (DATA_COLLECTION_DELAY > 0):

Subtracts the specified delay in minutes from both start and end data collection timestamps.
Shifts the collection window backward to capture missed database updates.
Example: 2-minute delay changes 10:00:00 - 10:05:00 to 09:58:00 - 10:03:00.

New parameter on RFC check program

A new RFC Destination parameter has been added to the RFC check program /NEWR/REGISTRY_RFC_CHECK. This enables the program to check an individual RFC destination. If left blank, all configured RFC destinations will be checked.

Configuration parameter to set data provider test for a single call ID

To access global parameters:

Go to menu /n/NEWR/INSTALL.
Use menu path SAP Menu > Expert Mode > Installation Setups > Global Configuration.
Or use transaction code /n/NEWR/Config.

Configuration parameter: REG_CALLID_TEST

Parameter value: <DP name> (default delivered: NR_SAP_ABAP_WS_COMPLETE, NR_SAP_IDOC_COMPLETE)

New data providers for ABAP business systems

NR_SAP_ABAP_WS_COMPLETE

Processes web service message headers and data (tag) records in parallel across monitored systems without record limitations.

Configuration:

Type: Event
Communicator: N/A
Data Provider Function: /NEWR/WS_MESSAGES_ARFC
Data Provider RFC enabled: Yes
Finisher Function: /NEWR/WS_EVENTS_FINISHER
Monitoring Group: SAP_APPL

Functional overview

This data provider comes pre-activated. Required parameters:

ADAPTER_TYPE
- Purpose: Specify adapter type to be selected from ABAP web service message header. Filter option of function module /SDF/IMA_DC_WS_ABAP.
- Sign: Inclusive only
- Option: EQ
- Values: Table fields separated by ;, can be multiple lines
DESTINATION
- Purpose: Specify RFC destination
- Sign: Inclusive only
- Option: EQ
- Values: RFC destination
DPC_COLL_TIME
- Purpose: Determine time interval
- Sign: Inclusive only
- Option: BT
- Values: System generated begin timestamp and end timestamp
IB_IF_NAME
- Purpose: Receiver interface name to be selected from ABAP web service message header. Filter option of function module /SDF/IMA_DC_WS_ABAP.
- Sign: Inclusive only
- Option: EQ
- Values: Receiver interface names separated by ;, can be multiple lines
IB_PARTY
- Purpose: Receiver party to be selected from ABAP web service message header. Filter option of function module /SDF/IMA_DC_WS_ABAP.
- Sign: Inclusive only
- Option: EQ
- Values: Receiver party separated by ;, can be multiple lines
JOIN_CONDITION
- Purpose: Specify join records for table /NEWR/JOIN_COND for further processing
- Sign: Inclusive only
- Option: EQ
- Values: Display titles separated by ;, can be multiple lines
NR_ACCID
- Purpose: Specify New Relic account ID
- Sign: Inclusive only
- Option: EQ
- Values: New Relic account ID
OB_IF_NAME
- Purpose: Sender interface name to be selected from ABAP web service message header. Filter option of function module /SDF/IMA_DC_WS_ABAP.
- Sign: Inclusive only
- Option: EQ
- Values: Sender interface names separated by ;, can be multiple lines
OB_PARTY
- Purpose: Sender party to be selected from ABAP web service message header. Filter option of function module /SDF/IMA_DC_WS_ABAP.
- Sign: Inclusive only
- Option: EQ
- Values: Sender parties separated by ;, can be multiple lines
SETTING_SWITCH
- Purpose: Specify options used by distributed processing
- Sign: Inclusive only
- Option: EQ
- Values: Multiple options separated by ; to control the distributed process:
  - HEADONLY=
    - SPACE (default): Provides both header and TAG data (if TAG names are specified in TAG_LIST parameter).
    - X: Only provides header data even if TAG names are specified in TAG_LIST parameter.
  - FIRSTONLY=
    - X (default): The data provider extracts data exclusively from the first occurrence of each TAG listed in TAG_LIST parameter.
    - SPACE: The data provider extracts data from all occurrences of each TAG listed in TAG_LIST parameter.
  - FREE%=nn: Specify the percentage of the available Working Processes in the monitoring system to determine the Desired Free Working Processes Limitation:
    - If the number of free Working Processes in the current monitoring system is equal to or greater than this Desired Free Working Processes Limitation, continue the distribution processing.
    - Otherwise, wait 1 second and repeat the check above until either:
      - The distribution processing can continue, or
      - The total waiting time exceeds the specified Maximum Waiting Time (see MWAIT#=nn).
    - The default value for this option is 30(%).
  - MINFT#=nn: Specify the Minimum Free Working Processes Limitation:
    - If the Desired Free Working Processes counted by the monitoring system falls below this minimum threshold, the system will pause for 1 second before attempting further processing.
    - The default value for this option is 3.
  - MWAIT#=nn: Specify the maximum waiting time (in seconds).
    - If the total waiting time (see FREE%=nn) exceeds the specified maximum, the distribution process will be canceled to conserve system resources.
    - The default value for this option is 60.
  - MREC#=nnnnn: Specify the number limitation of the Web Service Message Header records retrieved each time when calling Function Module /SDF/IMA_DC_WS_ABAP.
    - The default value for this option is 10000.
  - JSEND#=nnnn: Specify the number limitation of the result attribute records sent to New Relic server each time.
    - The default value for this option is 5000.
  - USER=user: Specify the RFC user name for each monitored system to retrieve the total number of work processes currently used by that system. The user is the SAP user ID.
  - DPWP#=nn: Specify the Maximum Working Processes Limitation.
    - During distributed processing: If the number of free Working Processes in the current monitoring system is less than or equal to this maximum limit, continue the distributed processing.
    - Otherwise, wait 1 second and then loop back to check again.
    - Continue this loop until the distributed processing can proceed or the total waiting time exceeds the specified Maximum Waiting Time (MWAIT#=nn).
    - Note: This check is only executed when the USER parameter is specified with non-initial values.
    - The default value for this option is 8.
STATE_GROUP
- Purpose: Processing status group to be selected from ABAP web service message header. Filter option of function module /SDF/IMA_DC_WS_ABAP.
- Sign: Inclusive only
- Option: EQ
- Values: Processing status groups separated by ;, can be multiple lines
SYS_ID
- Purpose: Determine system ID
- Sign: Inclusive only
- Option: EQ
- Values: System ID
TAG_LIST
- Purpose: Specify TAG names to be selected from ABAP web service message data and displayed as output in message data. Filter option of function module /SDF/IMA_DC_WS_ABAP.
- Sign: Inclusive only
- Option: EQ
- Values: Table fields separated by ;, can be multiple lines
USERNAME
- Purpose: User names who created message to be selected from ABAP web service message header (CREATED_BY). Filter option of function module /SDF/IMA_DC_WS_ABAP.
- Sign: Inclusive only
- Option: EQ
- Values: User names separated by ;, can be multiple lines

SAP monitoring

Tue, 05 Nov 2024 00:00:00 +0000

Patch files

v3.0 SP2 has one patch file for ABAP:

K-300SP02NEWR.SAR

Updates in this patch

New utilities

Telemetry attribute batch maintenance utility

Program: /NEWR/MODIFY_REGISTRY_PARALINE

This utility can be used to add configuration parameters to multiple data providers in batch mode. It can also be used to add system level tags to the data sent to New Relic. This utility can also be accessed on the /NEWR/INSTALL menu, under the "Expert Mode" section.

Key features:

Add, delete, or update configuration parameters
Batch mode operations across multiple data providers
System-level tag management

Registry configuration copy utility

Program: /NEWR/COPY_TABLE_FROM

This utility was designed to copy registry table (/NEWR/DPREGISTRY) and template table (/NEWR/DP_REG_IN) with the corresponding configuration table (/NEWR/DPSELOPDIR) and (/NEWR/DP_SELOPIN) from one system/client to another system/client.

The table name cannot be changed. The new enhancement allows copying these tables to different names.

RFC check utility update

Program: /NEWR/REGISTRY_RFC_CHECK

Added a new checkbox parameter to bypass checking of NR API endpoints (External HTTP destinations). The new parameter is required when scheduling the RFC check job. If external HTTP destinations are not bypassed when checked periodically by the job, New Relic platform may mistake it for failed data transmission attempts.

Bug fixes

This service pack fixes the following issues:

When the Central Monitoring System ST-PI version is 740 SP23 and above, calling the Log data provider function (/SDF/E2EEM_GET_DATA) causes ABAP dump
When the Central Monitoring System ST-PI version is 640 SP23 and above, calling the IDOC data provider function (/SDF/IMA_DC_IDOC) causes ABAP dump
If numeric attributes have empty spaces at the end, it causes the New Relic platform to reject the telemetry data. This patch removes the space
Increased the length of count field for metric data type to prevent metric data in Gauge type from being rejected by the New Relic platform
Truncate leading zeros of numeric attribute values to fix NR integration errors
Pass HDB name to self monitoring span calls (only impacts self-monitoring dashboard)

Manual configuration steps

Create a background job variant for RFC check

Create a new variant for program /NEWR/REGISTRY_RFC_CHECK, with "Exclude NR API Endpoints" checkbox checked. Use this variant to schedule the RFC check job.

Use "Modify data provider configuration parameters"

This service pack includes a new utility to add/delete/modify attributes or tags for all or selected data providers in batch mode. One of the use cases for this utility is to add a system tag to show the central monitoring system where all data is collected.

Access methods:

Menu path: /n/NEWR/INSTALL > Expert mode > Data provider maintenance > Modify data provider configuration parameter
Transaction code: /n/NEWR/DP_CONFIG_PARA in the SAP GUI command window

Configuration screen sections

Top section: data provider filtering

The top section of the selection screen allows filtering for the data provider where the configuration parameter should be added, deleted, or updated. If left blank, all data providers will be updated including deactivated and suspended data providers. Data provider status is part of the selection screen so you can apply the change to only data providers in certain status, such as active only.

Second section: parameter specification

Use the second section of the screen to specify the parameter to be modified. The parameter ID is mandatory. This field is not case sensitive; all characters will be converted to uppercase once saved.

All the fields specified on this screen will be updated to registry as-is. Please make sure each field has a value specified. Any field left blank will be blank in the registry.

Parameter operation modes

Adding a new parameter:

When adding a new parameter, the value specified in 'Parameter Sequence #' is ignored. The sequence number will be the next available sequence number for this parameter.

Deleting a parameter:

When deleting a parameter, leaving the sequence number field blank will remove all instances of the specified parameter, regardless of the sequence number.

Updating a parameter:

When updating a parameter, a sequence number is mandatory.

SAP monitoring

Wed, 11 Dec 2024 00:00:00 +0000

Patch files

v3.0 SP3 has two files:

K-300SP03NEWR.SAR
_NEWR_DATA_COLLECTORV3.3.SAP

Updates in this patch

v3.0 SP3 includes the following features:

New utilities

New program /NEWR/ONE_COLLECTION

Starting from SP3, the functionality of /NEWR/ABAP_COLLECTION_MANAGERN and RSBTONEJOB2 are combined into one program /NEWR/ONE_COLLECTION. This program has all the parameters from /NEWR/ABAP_COLLECTION_MANAGERN and the job name used in RSBTONEJOB2. It is used the same way as the program RSBTONEJOB2.

Bug fixes

This service pack fixes the following issues:

Changed the collection time zone from UTC to local server time zone for the data providers NR_SAP_WORKLOAD_COMPLETE and NR.SAP.WORKLOAD.COMPLETE
Data provider parameter ID now allows mixed upper and lower case
Data provider NR_SAP_JOB_ALL returns empty event attributes. This problem is specific to the central monitoring system with S/4 HANA Foundation 2023

Manual configuration steps

Starting from SP3, the functionality of /NEWR/ABAP_COLLECTION_MANAGERN and RSBTONEJOB2 are combined into one program /NEWR/ONE_COLLECTION. To schedule jobs, variants should be created for /NEWR/ONE_COLLECTION and jobs scheduled with these variants.

Create variants for /NEWR/ONE_COLLECTION

Program /NEWR/ONE_COLLECTION has all the parameters from /NEWR/ABAP_COLLECTION_MANAGERN and the job name previously used in RSBTONEJOB2. It is used the same way as the program RSBTONEJOB2.

Create variants with the following values:

Parameter

TRACE variant

IDOC variant

SYSTEM variant

Job name

NR_COLLECTION_TRACE

NR_COLLECTION_IDOC

NR_COLLECTION_SYSTEM

New Relic account ID

SAP account used to receive data

Records per trans

Default to 10000

Data provider name

Select single values:

- NR.SAP.TRANSACTION

- NR.SAP.TRANSACTION.COMPLETE

- NR.SAP.SYSTEM.PROCESS

- NR_SAP_PROGRAM

- NR_SAP_WORKLOAD_COMPLETE

- NR.SAP.WORKLOAD.COMPLETE

Select single values:

- NR_SAP_IDOC

- NR_SAP_IDOC_COMPLETE

- NR_SAP_IDOC_Configuration

Exclude single values:

- NR.SAP.TRANSACTION

- NR.SAP.TRANSACTION.COMPLETE

- NR.SAP.SYSTEM.PROCESS

- NR_SAP_PROGRAM

- NR_SAP_WORKLOAD_COMPLETE

- NR.SAP.WORKLOAD.COMPLETE

- NR_SAP_IDOC

- NR_SAP_IDOC_COMPLETE

- NR_SAP_IDOC_Configuration

Execution mode

Sequential processing

Parallel processing

Min WP required

If system DIA WP >= 30, set to 6; otherwise set to 3

N/A

If system DIA WP >= 30, set to 6; otherwise set to 3

Schedule collection jobs

Use transaction SM36 to schedule 3 jobs:

Parameter

Job 1

Job 2

Job 3

Job name

NR_COLLECTION_TRACE

NR_COLLECTION_IDOC

NR_COLLECTION_SYSTEM

Program

/NEWR/ONE_COLLECTION

Variant

TRACE

IDOC

SYSTEM

Running frequency

Every 5 minutes

Security role update

Upload the new role file _NEWR_DATA_PROVIDERV3.3.SAP to the monitored systems. The new security roles exclude user master tables from the object S_TABU_NAM.

SAP monitoring

Thu, 06 Feb 2025 00:00:00 +0000

Patch files

V3.0 SP4 contains one file:

K-300SP04NEWR.SAR

Updates in this patch

V3.0 SP4 includes the following features:

New utilities

Self monitoring/protection utility

Issues in monitored systems, such as missing authorization, RFC interface changes between SAP versions, and resource constraints (CPU, memory, etc.), may cause data provider functions to dump in remote monitored systems. This new self monitoring/protection utility records and alerts on dumps caused by data collection, and stops data collection on the affected remote system until the issues are resolved.

The utility includes the following components:

Monitors RFC calls to remote systems. Captures any System Failure exceptions and records Data Provider Name, RFC Destination, and Remote Function Module in the /NEWR/PROTECTION table.
Collects error messages and sends them to the New Relic platform as log entries (LOGTYPE = 'NR.RFC.CALL.STATUS.LOG'), which can be used to create alerts.
Skips the failed Data Provider + RFC destination combinations in future data collection runs, until the issues are resolved and removed from transaction /NEWR/PROTECTION.

New Relic account ID field

A New Relic Account ID column has been added to the Monitored System Configuration screen. The Monitored System/Database can now send data to a default New Relic account. If left blank, the collection job determines which New Relic account receives the data.

Bug fixes

HANA database connection instances are now released after each SQL query and recreated for the next query. This resolves an issue where too many database connections were created for HANA data providers.

SAP monitoring

Tue, 09 Dec 2025 00:00:00 +0000

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

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

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.
Background RFC Q data provider: New data provider NR.SAP.BGRFC.Q for monitoring background RFC queues.
IDoc data provider: Updated NR_SAP_IDOC to include partner IDoc ID.
System memory data provider: Updated NR.SAP.SYSTEM.MEMORY.HEAP_USAGE - changed parameter MTE_CLASS to R3MemMgmtHeapAct.
Connection issue handling: Protection triggered by temporary connection issues no longer requires manual intervention to clear.
HANA Sidecar support: Bug fix allows HANA Sidecar to be added as a monitored system without specifying the RFC destination.
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

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

Bug fixes

RFC check program: Updated /NEWR/REGISTRY_RFC_CHECK with improved functionality.
Payload data gap: Fixed bug causing data gaps in payload data for data provider NR_SAP_ABAP_WS.
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:

Field

Value

SAP System ID

CALM_LMS

Client

Leave blank

Destination

RFC Destination used for CALM data provider authentication

Software Component

Leave blank

Database Vendor

Leave blank

DB Connection

Leave blank

New Relic Account ID

New Relic account to send data to

API Host

API host used for CALM data providers

Select Monitoring Group CALM_LMS for this monitored system.

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:

Parameter

Description

Default Value

Attribute

DB_CONC

Database Connection

RFC_DEST

Monitored System RFC Destination

DPC_COLL_TIME

Collection Time Period

SYS_ID

Monitored System ID

Yes

Output attributes:

Attribute

Description

BACKUP_ID

The unique ID of the broken backup history entry

SYS_TIME

The local time at which the broken backup history was detected

UTC_TIME

The UTC time at which the broken backup history was detected

SOURCE_ID

The persistence volume ID

HOST

The host name

SERVICE_TYPE_NAME

The type of database service

REDO_LOG_POSITION

The redo log position of the broken backup history entry

REASON

The reason for the broken backup history

Message

Additional message for backup broken history

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:

Parameter

Description

Default Value

Attribute

DB_CONC

Database Connection

RFC_DEST

Monitored System RFC Destination

DPC_COLL_TIME

Collection Time Period

SYS_ID

Monitored System ID

Yes

Output attributes:

Attribute

Description

BLK_START

Blocking starting time

END_TIMESTAMP

Blocking end time

SITE_ID

Site ID

HOST

Host name

PORT

Internal port

LOCK_TYPE

Type of lock: Record, Table, Metadata

LOCK_MODE

Lock mode: SHARED, EXCLUSIVE

WAITING_SCHEMA_NAME

The name of the schema on which the lock is currently placed

WAITING_OBJECT_NAME

The name of the object on which the lock is currently placed

WAITING_RECORD_ID

The ID of the record on which the lock is currently placed

BLOCKED_CONNECTION_ID

The connection ID associated with the blocked write transaction

BLOCKED_UPDATE_TRANSACTION_ID

The write transaction ID of the write transaction waiting for the lock

BLOCKED_STATEMENT_HASH

Hash code for the statement being blocked

LOCK_OWNER_CONNECTION_ID

The connection ID associated with the write transaction holding the lock

LOCK_OWNER_UPD_TRANSID

The write transaction ID of the write transaction holding the lock

LOCK_OWNER_HOST

The client host for the lock owner

LOCK_OWNER_PID

Process ID for the lock owner

LOCK_OWNER_APPLICATION_SOURCE

Application source for the lock owner

LOCKOWNER_STATEMENT_STR

Lock owner's statement

LOCK_OWNER_STATEMENT_HASH

Hash code for the lock owner statement

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:

Parameter

Description

Default Value

Attribute

DB_CONC

Database Connection

RFC_DEST

Monitored System RFC Destination

DPC_COLL_TIME

Collection Time Period

SYS_ID

Monitored System ID

Yes

Output attributes:

Attribute

Description

HARDWARE_KEY

The hardware key of the SAP HANA installation

SYSTEM_ID

The system identifier (SID)

INSTALL_NO

The installation number

SYSTEM_NO

The system number

GLAS_APPLICATION_ID

The license ID for the software product

PRODUCT_NAME

The name of the licensed software product

PRODUCT_DESCRIPTION

The description of the licensed software product

PRODUCT_LIMIT

The allowed product usage as specified by the license in bytes (e.g., main memory)

PRODUCT_LIMIT_DESCRIPTION

Description of allowed product usage

PRODUCT_USAGE

The peak product usage value during last 13 months, measured periodically, in bytes

MEASUREMENT_INTERVAL

The interval of license measurement, in hours

FIRST_INSTALLATION_TIME

The date of the first installation of the license

START_DATE

The start date of the license validity period

EXPIRATION_DATE

The expiration date of the validity period of the license

LAST_SUCCESSFUL_CHECK

The latest date on which the license was successfully checked and found valid

PERMANENT

Displays TRUE if the license is permanent and FALSE if the license is temporary

VALID

Indicates whether the license is valid or not: TRUE/FALSE

ENFORCED

Indicates whether the license is a memory-enforced license or not: TRUE/FALSE

LOCKED_DOWN

Indicates whether the system is locked down due to license status: TRUE/FALSE

IS_DATABASE_LOCAL

Indicates whether the license is a local database license: TRUE/FALSE

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:

Parameter

Description

Default Value

Attribute

DB_CONC

Database Connection

RFC_DEST

Monitored System RFC Destination

DPC_COLL_TIME

Collection Time Period

SYS_ID

Monitored System ID

Yes

Output attributes:

Attribute

Description

CONNECTION_ID

The connection ID

TRANSACTION_ID

The transaction object ID

START_TIME

The transaction start time

ELAPSED_SECONDS

Elapsed time in seconds

USER_NAME

User name

CLIENT_HOST

Client host

CONNECTION_STATUS

Connection status

STATEMENT_STRING

Statement string for the transaction

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:

Parameter

Description

Default Value

Attribute

DB_CONC

Database Connection

RFC_DEST

Monitored System RFC Destination

DPC_COLL_TIME

Collection Time Period

SYS_ID

Monitored System ID

Yes

Output attributes:

Attribute

Description

USER_NAME

User name

VALID_UNTIL

Password valid until this date

DAYS_TO_EXPIRE

Number of days remaining before password expiration

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:

Parameter

Description

Default Value

Attribute

DB_CONC

Database Connection

RFC_DEST

Monitored System RFC Destination

DPC_COLL_TIME

Collection Time Period

SYS_ID

Monitored System ID

Yes

Output attributes:

Attribute

Description

HOST

Host name

PORT

Internal port

CONN_ID

Connection ID

STATEMENT_ID

The ID of the statement being executed

THREAD_ID

The thread ID

THREAD_TYPE

The thread type

THREAD_STATE

The thread state

THREAD_METHOD

The thread method

LOCK_WAIT_NAME

The internal name of the lock

THREAD_DETAIL

The thread detail

CLIENT_IP

The IP of the client machine

CLIENT_PID

The client process ID

CALLER

The service that called the thread

CALLING

The service called by the thread

ACTIVE

Whether the thread is active

USER_NAME

The SQL user name

APPLICATION_NAME

The name of the application

APPLICATION_USER_NAME

The application user name

TRANSACTION_ID

The transaction ID

DURATION

The thread duration in milliseconds

CPU_TIME_SELF

The active CPU time of the thread in microseconds

CPU_TIME_CUMULATIVE

The active CPU time of the thread and its associated children in microseconds

STATEMENT_THREAD_LIMIT

The statement thread limit

STATEMENT_MEMORY_LIMIT

The statement memory limit

WORKLOAD_CLASS_NAME

The name of the workload class

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:

Parameter

Description

Default Value

Attribute

API_HOST

UDM data extraction host

API_PATH

UDM data extraction path

API_QUERY

UDM data extraction query

DATA_COLL_PERIOD

An integer value determining the collection period. If set as 1, details for last month will be collected. If set as 2, details for last 2 months will be collected.

DESTINATION

Authentication destination for UDM

NR_ACCID

New Relic platform account number

SOURCE_ACCT

Monitored System ID

Yes

Setup instructions:

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

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

SAP monitoring

Fri, 26 Sep 2025 00:00:00 +0000

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

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).
New utility: Utility to generate configurations for CloudALM-based data providers.

S/4 HANA and ECC related updates

New Monitoring Groups (/NEWR/DP_GROUP):
- CF: Cloud Foundry
- SAP_CC: SAP Cloud Connector
- SLT: SAP Landscape Transformation Server
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 object

Description

Field

S_BTCH_ADM

Background Processing: Background Administrator

BTCADMIN = Y

S_SPO_ACT

Spool: Actions

SPOACTION = 'BASE' and SPOACTION = 'DISP'

S_ADMI_FCD

System Authorizations

S_ADMI_FCD = 'SP01' and S_ADMI_FCD = 'SP0R'

S_XMI_PROD

Authorization for External Management Interfaces (XMI)

EXTCOMPANY = 'NEW_RELIC' EXTPRODUCT = 'NRM4SAP' INTERFACE = *

S_XMB_MONI

Authorization object for XI message monitoring

ACTVT = 03, 29

SXMBIFNAME = *

SXMBIFNS = *

SXMBPARTY = *

SXMBPRTAG = *

SXMBPRTTYP = *

SXMBSERV = *

Authorization role /NEWR/SLT_COLLECTOR

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

Authorization object

Description

Field

S_DMIS

Authority object for SAP SLO Data migration server

ACTVT = 03

MBT_PR_ARE = SLOP

MBT_PR_LEV = PACKAGE

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:

Parameter

Description

Default value

Required

API_HOST

Cloud Foundry data extraction host

API_PATH

Cloud Foundry data extraction path

API_QUERY

Cloud Foundry data extraction query

AUDIT_EVENTS

Events to be captured (optional)

app.crash

audit.app.process.crash

DESTINATION

Authentication destination for Cloud Foundry

NR_ACCID

New Relic platform account number

SOURCE_ACCT

Monitored system ID

None

Yes

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:

Parameter

Description

Default value

Required

HOST_DESTINATION

SAP Cloud Connector host

NR_ACCID

New Relic platform account number

SOURCE_ACCID

Monitored system ID

Yes

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:

Selection criteria

Description

Data provider

CALM data provider for which configuration needs to be generated

Service type

Name of systems/services linked to your CALM

LMS ID

List of LMS IDs configured in CALM for the selected service type

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:

Parameter

Description

Default Value

Required

KEY_FIGURE

Display Attribute Name

TABLE_FIELDS

Table fields

TABLE_NAME

Table Name

T000

TIME_RANGE_NAME

Field for Date and Time

CHANGEDATE

DESTINATION

Monitored System RFC Destination

DPC_COLL_TIME

Collection Time Period

SYS_ID

Monitored System ID

Yes

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:

Parameter

Description

Default Value

Required

DIRECTION

BGRFC direction filter

MONITORED_DEST

BGRFC destination filter

QNAME

BGRFC queue name filter

SETTING_SWITCH

Data Collection configurations

TOT_ROWS=100000

STATE_GROUP

Status group filter

SYS_ID

Monitored System ID

Output attributes:

Attribute

Description

CLIENT

SAP Client

DIRECTION

Inbound (I) or Outbound (O)

QUEUE_NAME

DEST_LOCKED

Destination lock status: X or Space

UNIT_LOCKED

Unit lock status: X or Space

QUEUE_LOCK

Queue lock status

DEST_NAME

EXECUTE_TIMESTAMP

CREATE_TIMESTAMP

STATE

Status Code

MESSAGE

BGRFC_STATE_GROUP

CRIT (Critical), INTE (Interim), E (Error), L (Locked)

Status code (STATE):

State Code

Meaning

21211

basxml_not_supp_

21204

comm_failure__

21213

conversion_error__

21203

deleted___

21202

finished___

21201

in_execution__

21216

locked_from_serv_

21212

meta_data_error_

21217

noti_comm__

21220

noti_others__

21222

noti_requested__

21221

noti_sent__

21219

noti_success__

21218

noti_sys__

21206

resource_comm__

21207

resource_system__

21209

retry_forced__

21208

scheduler_abort__

21214

server_shutdown__

22204

srv_comm_failure_

22203

srv_confirmed__

22208

srv_ctx_not_found

22207

srv_ctx_not_in

22202

srv_finished__

22201

srv_in_execution_

22205

srv_system_fail_

22206

srv_unit_notin_db

22209

srv_unit_wr_state

21205

system_failure__

21200

unknown___

21210

utask_failure__

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:

Parameter

Description

Default Value

Required

RFC_DEST

Monitored System RFC Destination

SYS_ID

Monitored System ID

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:

Parameter

Description

Default Value

Required

SERVICE

OData Service Name

EXCEPTION

Exception Name

CLIENT

SAP Client Number

TIME_INTERVAL

Sample periods in minutes

RFC_DEST

Monitored System RFC Destination

SYS_ID

Monitored System ID

NR.SAP.GW.PERFORMANCE

This data provider has two metrics for gateway performance:

Metric Name (KEY_FIGURE)

Description

XMLSIZE

Average XML Size

RESPONSETIME

Average Response Time

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:

Parameter

Description

Default Value

Required

SERVICE

OData Service Name

CLIENT

SAP Client Number

KEY_FIGURE

Metric Name

RESPONSETIME

XMLSIZE

TIME_INTERVAL

Sample periods in minutes

RFC_DEST

Monitored System RFC Destination

SYS_ID

Monitored System ID

NR.SAP.SLT.INFO

This data provider provides the following metrics for SLT monitoring:

Metric Name (KEY_FIGURE)

Description

CON_SS_STATUS

Source System Status

CON_TS_STATUS

Target System Status

JOB_MASTER_STATUS

Master Job Status

JOB_LOAD_STATUS

Load Job Status

TRIGGER_STATUS

Trigger Status

STATUS_GROUP

Schema Status

STAT_LAT24H

Schema Latency

JOB_LOAD_CONFIGURED

Configured Number of Load Jobs

JOB_LOAD_NOT_RUN

Not Running but Configured Number of Load Jobs

JOB_LOAD_TERMINATED

Terminated Number of Load Job Runs since Last Refresh

JOB_MASTER_TERMINATED

Terminated Number of Master Job Runs since Last Refresh

TRIGGER_ACTIVE_STATUS

Trigger Active Status

TABLES_TO_REPLICATE

Table Number to be Replicated

AVG_LAT24H

Average Latency Time of the Last 24 Hours

MAX_LAT24H

Maximal Latency Time of the Last 24 Hours

TIMESTAMP_YOUNGEST

Youngest Timestamp of Replication

AVG_LATENCY_REFRESH

Average Latency Time of the Last Hour

MAX_LATENCY_REFRESH

Maximal Latency Time of the Last Hour

TIMESTAMP_OLDEST_AGE

Oldest Timestamp of a Table to be Replicated

SUM_TAB_ENT_TO_REPLICATE

Sum of all Table Entries to be Replicated

MAX_SING_TAB_ENT_TO_REPLICATE

Max Entries to be Replicated

REPLICATED_TAB_ENT_REFRESH

Number of Tables not Fully Replicated

TABLES_ERROR

Table Number in Error State

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:

Parameter

Description

Default Value

Required

CONFIG_NAME

Display Configuration Name in Metric

UID

Master Transfer ID

KEY_FIGURE

Metric Name

CON_SS_STATUS

CON_TS_STATUS

JOB_MASTER_STATUS

JOB_LOAD_STATUS

TRIGGER_STATUS

STATUS_GROUP

STAT_LAT24H

Yes

TABLE_NAME

Transfer table to be monitored

RFC_DEST

Monitored System RFC Destination

SYS_ID

Monitored System ID

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.

Transmission method

Description

Direct

Data is sent directly from SAP to New Relic (existing functionality)

SAP Cloud Integration

Data is routed through SAP CPI as middleware

iFlow endpoint

iFlow endpoint destination

Configuration steps

Select iFlow authorization type: Choose the authorization method you'll use: ClientId/Secret, Certificate, or External Certificate.
Create a service instance for SAP Process Integration Runtime and assign either a service key or certificate based on your selected authorization method.
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.
Create an RFC destination (SM59) using the service key or certificate generated in the previous step along with the iFlow endpoint destination.
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:

Configure Allowed headers to include API-Key|targetURL.

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.

Configure the Request content modifier to store exchange properties.

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");
}

Use Response content modifier to hold the message header/body.
Update the New Relic response HTTP connection.

SAP monitoring

Tue, 04 Mar 2025 00:00:00 +0000

Overview

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

BTP data can be collected using two methods:

Through BTP Process Integration Runtime Service. This option requires a subscription to "Process Integration Runtime Service" in the monitored BTP accounts.
Through SAP CloudALM. This option requires setting up a CloudALM account to monitor the BTP accounts.

Patch files

V3.0 SP5 contains one file:

K-300SP05NEWR.SAR

Updates in this patch

V3.0 SP5 includes the following features:

New data provider types

API event: Event data from API calls
API metric: Metric data from API calls

New data providers

SP05 includes the following new data providers:

NR_BTP_IS_MPL: Data provider to retrieve BTP integration suite iFlow message logs. This data provider is assigned to Monitoring Group BTP_IS. The New Relic event generated from this data provider is NR_IS_IFLOW_LOG.
NR_CALM_IS_MPL: Data provider to retrieve BTP integration suite iFlow message logs via CloudALM Integration Monitoring. This data provider is assigned to Monitoring Group CALM. The New Relic event generated from this data provider is NR_IS_IFLOW_LOG.
NR_CALM_LANDSCAPE: Data provider to retrieve CloudALM landscape monitoring data. This data provider is assigned to Monitoring Group CALM.

Monitored System configuration screen updates

The Monitored System configuration screen has been updated to accommodate API-based monitoring:

An API Host field has been added to the configuration screen.

Bug fixes

Fixed an issue where ST-PI version mismatches between the monitoring system and monitored systems may cause the data provider function for NR_SAP_SYSTEM_USER_SESSION to dump.
Fixed an issue where the RFC Destination filter does not pick up monitored systems that have no New Relic account specified in the configuration.
Added automatic switching between HTTP and HTTPS protocols when calling SAPControl web services.
Added seconds to the schedule starting time field in the Run Time control table. This requires the runtime table to be cleared after installing SP05.
Fixed an issue in numeric attributes handling in finisher functions.

SAP monitoring

Thu, 08 May 2025 00:00:00 +0000

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.

SAP monitoring

Mon, 09 Jun 2025 00:00:00 +0000

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 [#manual-config]

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

export const _frontmatter = {"subject":"SAP monitoring","releaseDate":"2025-06-09","title":"Patch Release V3.0 SP7"}

SAP monitoring

Sat, 19 Jul 2025 00:00:00 +0000

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.

SAP monitoring

Tue, 19 Aug 2025 00:00:00 +0000

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 [#update-in-the-authorization-role]

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 [#instructions-for-the-new-features]

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

Do not add or modify monitored systems while applying the Service Pack.
After Service Pack deployment, use the Maintain Monitored Systems menu to modify monitored systems if necessary.
For newly added monitored systems, generate configurations only for those systems rather than regenerating all configurations. See Generating configurations for specific monitored systems for details.

Generating configurations for specific monitored systems [#data-provider-specific-monitor]

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.

When no System ID or Data Provider Name is entered, all data providers will be removed and regenerated.

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:

Launch program /NEWR/REP_INSTALL_REPLACING using transaction SE38
Keep "Transfer Stage" at 0 (do not modify)
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.

SAP monitoring

Tue, 23 Jul 2024 00:00:00 +0000

What's new in this version

Removal of Java Enterprise Connector

Starting from this version, New Relic Monitoring for SAP Solutions can connect to New Relic API endpoints without the need for Java Enterprise Connector. There will be no need for any installation activity on the operating system level. This makes this version capable of running on SAP's Private Cloud Edition (RISE).

For backward compatibility, the Java Enterprise Connector from version 2.5 may still be used with 3.0, but is no longer recommended.

Connecting to New Relic API endpoints is now managed with the ABAP Add-on in the following fashion:

New Relic endpoints are configured as External HTTP Destination (Type G) in SAP transaction SM59
New Relic accounts, applicable endpoint destinations and API Ingest Keys are configured in transaction /n/NEWR/CONNECT

New HANA database monitoring

Connect to HANA using ABAP database connection

HANA databases are now connected using native ABAP database connections. The following prerequisites must be satisfied to monitor the HANA database from the central monitoring system:

Connection to the HANA database

You must have one of the following:

HANA Client v2.0 (version needs to match the HANA server), or
HANA Client Lib file libSQLDBCHDB.so (Linux) and libSQLDBCHDB.dll (Windows) in the SAP Kernel folder (use SID Admin ID, e.g., sd1adm)

HANA database user with catalog read and monitoring access

Sample commands:

CREATE ROLE NR_AGENT_ROLE;
GRANT CATALOG READ TO NR_AGENT_ROLE;
GRANT MONITORING TO NR_AGENT_ROLE;
CREATE USER NRAGENT PASSWORD Xxxxxxxx NO FORCE_FIRST_PASSWORD_CHANGE;
GRANT NR_AGENT_ROLE TO NRAGENT;

Network access

The Central Monitoring System must have access to the HANA server and tenant DB port.

HANA database queries

The monitoring queries are now maintained using an ABAP transaction (/NEWR/DB_QUERIES). They can also be accessed via New Relic menu path Expert Mode > HANA DB Monitoring Queries in the menu /NEWR/INSTALL.

Each query line is limited to 192 characters, and the fields retrieved need to be prefixed with ~.

New installation menu

The installation menu (/NEWR/INSTALL) is updated with 5 major sections:

Install new release and patch

This section is used to install new release and/or service patches delivered from New Relic. The menu items in this section are intended to be executed in sequence to complete the installation process. It automatically detects the new release/patch to be installed.

Once the process is completed, the process cannot be repeated, unless the installation flag is reset. Please refer to the installation guide.

Maintain monitored systems

Use this section to add or remove monitored systems or change monitoring groups. The data provider registry configurations can be re-generated in this section as well.

Data provider registry maintenance

This is a convenient way to access the transaction /n/NEWR/REGISTRY.

Update configuration templates

Configuration changes for the data providers, including custom data providers, can be saved back to the template in this section. Once saved, the changes will not be lost when the configurations are generated again.

Expert mode

Here are advanced utilities to maintain the support tables for the installation process, including adding new database queries to monitor the HANA database. Details of these utilities are covered in the Administration Guide.

Supported SAP versions

New Relic Monitoring for SAP Solutions is compatible with the following SAP versions:

SAP_BASIS

SAP_ABA

ST_PI

740

SP14

750

740 SP14

750

75A

740 SP14

751

75B

740 SP14

752

75C

740 SP14

753

75D

740 SP14

754

75E

740 SP14

755

75F

740 SP14

756

75G

740 SP14

757

75H

740 SP14

758

75I

740 SP14

Install New Relic Monitoring for SAP Solutions v3.0

Installation packages included

There are two installation packages included:

K-300AOIINNEWR.SAR: For a fresh install of the New Relic Monitoring for SAP Solutions v3.0
K-300AOUINNEWR.SAR: For upgrade to the New Relic Monitoring for SAP Solutions v3.0 from v2.5

Upgrade from v2.5

If you are upgrading from v2.5, it is important to save any configuration changes before configuring the new v3.0. You can do this before or after the v3.0 ABAP Add-on is installed in client 000.

The configuration templates must be saved BEFORE copying the new template from client 000. Otherwise, the factory setting will override any changes made in the previous version.

To save the configuration template:

Open the menu /n/NEWR/INSTALL
Open Update or Save Configuration Template folder
Follow the steps

Update HANA database monitoring

If HANA database is monitored in v2.5, there are a few more steps required to convert from v2.5 JDBC-based database connection to v3.0 ABAP database connection:

Remove v2.5 HDB configuration template

From v2.5 to v3.0, New Relic Monitoring for SAP changes the way it monitors the HANA database from using the Java Enterprise Connector via JDBC to using SAP ABAP database connection. Because of this drastic change, to upgrade, you need to first remove the v2.5 configuration templates.

Steps:

Use transaction SE38 to execute program /NEWR/REP_DELETE_INS_TEMPLATE
Normally, no adjustment of the parameters is needed
Click on the execute button

Set up ABAP database connection

Follow the v3.0 installation guide to complete these tasks:

Set up HANA database connection in DBACOCKPIT
Configure connection to New Relic endpoints
Copy new configuration template from client 000

In the menu folder Install new releases and patches, execute the menu items in sequence.

Update the monitoring group for the monitored systems

In v2.5, because the database connection is handled by the Java Enterprise Connector, the HANA_DB monitoring group is normally set up separately from the rest of the data providers. In v3.0 this is no longer necessary. The separate configuration line connecting to Java Enterprise Connector (normally RFC destination NR_EI_AGENT) should be removed.

To complete the configuration, perform the following steps:

Remove the v2.5 HANA_DB monitoring configuration (row identified by the RFC destination NR_EI_AGENT)
Add the newly created database connection to the DB Connection field
Configure the monitoring group:
- Highlight the monitored system (e.g., SD2)
- Click on "Monitoring Group" button
- Turn on "HANA_DB"
- Click on the "Generate" button
Continue to the next step to re-generate the registry configuration

Re-generate the registry configuration

After updating the monitoring groups, complete the registry configuration regeneration to finalize the upgrade process.