Using Errors Inbox in APM gives you an added layer of convenience, allowing you to triage errors without switching screens.

Here are some best practices for using Slack with your current workflows.

Set up an Errors Inbox for each team

Setting up an Errors Inbox for each team ensures that your teams can proactively monitor new and recurring errors that affect their work. In Errors Inbox, create a separate workload for each team based on the apps and services that the team is responsible for. Then, tie the workload to a separate Slack channel for that specific team to monitor. The team will get notifications when a new error appears or when a resolved error is reopened.

For example, a mobile team can create a workload that includes their mobile app and all the backend services the mobile app uses. If there are any errors, the mobile team will get automatic notifications in Slack. If needed, the mobile team can send a notification to other affected teams via Slack.

Track your deployments

You can create separate workloads for your staging and production environments, then tie each environment to separate Slack channels. Any errors that occur during deployment windows will be grouped by environment and sent to the corresponding Slack channel, allowing you to see exactly when and where the error occurred. This helps you ensure your code is working properly before and after deployments so your customers have a great experience.

Attachments

  • Original document
  • Permalink

Disclaimer

New Relic Inc. published this content on 16 September 2021 and is solely responsible for the information contained therein. Distributed by Public, unedited and unaltered, on 16 September 2021 15:11:03 UTC.