Patch release v3.0 SP2

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.