New Relic: APM PowerPack Release Notes version 104

Version 104 of the New Relic: APM PowerPack includes a security update, introduces a "universal" type credential, and updates for Python 3 compatibility.

  • Minimum Required SL1 Version: 11.3.0

  • Support Status: GA

Before You Install or Upgrade

Ensure that you are running version 11.3.0 or later of SL1 before installing "New Relic: APM" PowerPack version 104.

For details on upgrading SL1, see the relevant SL1 Platform Release Notes.

Installation and Upgrade Process

If you are currently using the Dynamic Applications in this PowerPack to monitor devices, collection errors might occur for one or two polling cycles during the installation of a new version. To prevent collection errors during an upgrade, you can optionally disable collection for monitored devices before performing the following steps and re-enable collection after the upgrade.

To install this PowerPack:

  1. Search for and download the PowerPack from the PowerPacks page (Product Downloads > PowerPacks & SyncPacks) at the ScienceLogic Support Site.
  2. In SL1, go to the PowerPacks page (System > Manage > PowerPacks).
  3. Click the Actions menu and choose Import PowerPack. The Import PowerPack modal appears.
  4. Click Browse and navigate to the PowerPack file from step 1.
  5. Select the PowerPack file and click Import. The PowerPack Installer modal displays a list of the PowerPack contents.
  6. Click Install. The PowerPack is added to the PowerPack Manager page.

After an upgrade from the New Relic: APM PowerPack version 100 to version 101 or later, a new Infrastructure Group device will be created. You will see Notice events indicating topology changes as each child server device migrated to the new Infrastructure Group device. Once all child server devices have migrated to the new Infrastructure Group, you may delete the old Infrastructure Group.

Features

This release includes the following features:

  • A "universal" type credential for discovering New Relic Services
  • Dynamic Applications that discover and collect data from New Relic Application Performance Monitoring (APM) service and infrastructure services.
  • Event Policies and corresponding alerts that are triggered when New Relic services meet certain status criteria.
  • Device Classes and Device Categories for each type of New Relic Service monitored.
  • A Sample Credential for discovering New Relic services.
  • A Device template for aligning Dynamic Applications.
  • Dashboards for viewing the status of your New Relic services.

Enhancements and Issues Addressed

The following enhancements are included in the PowerPack:

  • Updated the following Dynamic Applications to work with the New Relic "universal" credential type:
    • New Relic: APM Discovery & Collection Cache
    • New Relic: APM Events
    • New Relic: APM Infrastructure Group Discovery
    • New Relic: APM Application Summary Stats
    • New Relic: APM Applications Metric Index Config
    • New Relic: APM Database Stats
    • New Relic: APM End-User Stats
    • New Relic: APM Memcache Stats
    • New Relic: APM Memory Usage Stats
    • New Relic: APM Web Transactions Stats
    • New Relic: APM Infrastructure Discovery
    • New Relic: APM Infrastructure Config
    • New Relic: APM Infrastructure Stats
    • New Relic: APM Java Garbage Collection Stats
    • New Relic: APM Java Memory Usage Stats
    • New Relic: APM Java Threads Stats
  • Updated this PowerPack to be Python 3 compliant.  
  • Removed Discovery objects from the following Dynamic Applications to address an issue in which Dynamic Applications were causing mis-alignment to physical devices and to allow the "universal" type credential use.  
    • New Relic: APM Discovery & Collection Cache
    • New Relic: APM Events
    • New Relic: APM Infrastructure Group Discovery

Physical discovery is no longer available for this PowerPack. For more information, see the section on Creating a Virtual Device .

Known Issues

The following known issues affect version 104 of the New Relic: APM PowerPack:

  • Proxy authentication is not supported with New Relic: APM PowerPack.
  • The violations listed for the "New Relic: Events" Dynamic Application will not contain violations for devices that are not modeled by SL1. Alerts for these devices will be displayed as log messages for the root device.
  • There is a delay in Infrastructure Count reporting from the "New Relic: APM Discovery & Collection Cache" Dynamic Application, as it takes two to three collections cycles for the count to be collected, cached, read, and reported.