July, 2022 End Of Life Announcements

This quarter we are discontinuing capabilities and features across the following products. If you have questions or concerns, please comment below or reach out to your account management team.

Support ending July 2022:

  • Python agent 3.6
  • Certain frameworks & platforms

Support ending August 2022:

  • Pixie + NR Integration v1
  • Old synthetic private minion helm chart URL

Support ending September 2022:

  • Incident workflows (beta)
  • Pathways (old incident intelligence)
  • Service maps

Early Notice for January 2023

  • VictorOps (built-in alert notifications)
  • xMatters (built-in alert notifications)

1. Python agent 3.6

What is the impact? What will you experience?

  • Customers who don’t upgrade will still be able to use features, however, support will no longer be provided.

Why is this change being implemented?

  • Python 3.6 language version has low usage. Security support from the Python language community of this version ended Dec 2021 (after official EOL).

What do you need to do?

  • No action is required. The old version will no longer be supported after July 31, 2022.

2. Certain frameworks & platforms

What is the impact? What will you experience?

  • We will no longer support old versions of Centos 6 platform, 32-bit support, Free BSD, Cake 1.1, Joomla 1.5-1.6, Kohana 3.2-3.3, Silex 1.x-2.x, Symfony 1.x-2.x.

  • Customers who don’t upgrade will still be able to use features, however, support will no longer be provided.

Why is this change being implemented?

  • These are very old platform, and language runtime versions.

What do you need to do?

  • No action is required. The old versions will no longer be supported after July 31, 2022.

3. Pixie + NR Integration v1

What is the impact? What will you experience?

  • This integration allows customers to deploy Pixie alongside their Kubernetes agent install. Users can then view Pixie’s live views within the New Relic UI in the “Live Debugging” panes. The integration also exports HTTP, SQL, and JVM data to New Relic via OpenTelemetry for long-term data retention and use in New Relic’s native UIs. We have just released the Pixie + NR Integration v2 which uses the new Pixie Plugin system to handle data export from Pixie to New Relic.

  • Older versions are not expected to break anything, however, they will not be supported.

Why is this change being implemented?

  • Moving to the new integration version will allow us to easily pull Pixie data into New Relic, without any additional effort from users.

What do you need to do?

  • The requirement to switch from v1 to v2 is to reinstall the Pixie/NR integration by uninstalling or upgrading the Helm chart.

When do you have to make these changes by?

  • August 31, 2022

Resources:

4. Old synthetic private minion helm chart URL

What is the impact? What will you experience?

  • Customers who do not update their helm repo configuration may have installation/update failures. Private minion installations will not break and would only be impacted during upgrade attempts.

Why is this change being implemented?

  • Synthetics initially was not integrated into other helm charts and used a https://helm-charts.newrelic.com/charts URL. These charts are no longer updated. All New Relic helm charts are now maintained in a single location. Installation and configuration details both in the documentation and in the product have been updated to point to the new helm chart repo.

What do you need to do?

  • Update your helm configurations, using the new https://helm-charts.newrelic.com URL (the same as the rest of the New Relic platform) and the synthetics-minion folder as indicated in our in-product installation instructions.

  • Overall effort to update the configuration should be low.

When do you have to make these changes by?

  • August 31, 2022

Resources:

5. Incident workflows (beta)

Why is this change being implemented?

  • This product was the private beta version and is being replaced by workflows, which is available to all New Relic customers.

What do you need to do?

When do you have to make these changes by?

  • September 30, 2022

6. Pathways (old Incident Response)

What is the impact?

  • Pathways will no longer be supported

Why is this change being implemented?

  • This older incident intelligence feature is being replaced by workflows.

When do you have to make these changes by?

  • September 30, 2022

7. VictorOps, OpsGenie and xMatters (built-in alert notifications)

What is the impact? What will you experience?

  • The legacy notification channel integration is going away and will not be included in workflows as a built-in integration. In January, 2023, the payload will be migrated to a standard webhook in workflows, providing the same result.

What do you need to do?

  • There should be no work for you to do as part of the automatic upgrade process. We will convert VictorOps, OpsGenie, and xMatters channels into Webhook templates when we create the workflows.

When will these changes occur?

  • January 15 - 30, 2023

8. Service maps

What is the impact? What will you experience?

  • There may be some impact to dashboards with legacy service maps embedded.

Why is this change being implemented?

  • The legacy map experience for APM does not use entities or relationships.

When do you have to make these changes by?

  • September 30, 2022
2 Likes