SAP release notes release notesRSS

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.

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:

1. 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
2. Data provider parameter ID now allows mixed upper and lower case
3. 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:

Schedule collection jobs

Use transaction SM36 to schedule 3 jobs:

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.

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:

1. 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
2. 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
3. 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
4. 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
5. Truncate leading zeros of numeric attribute values to fix NR integration errors
6. 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.

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.

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:

1. NR_SAP_WORKLOAD_COMPLETE (Event)
2. 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:

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:

1. Trace sending incorrect span timestamps
2. The user who runs the collection job has to use the system time zone
3. The collection manager dumps when HANA expensive statement data provider is not configured
4. 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:

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