diff --git a/src/data/nav.yml b/src/data/nav.yml
index e8c34a840..356fc7b66 100644
--- a/src/data/nav.yml
+++ b/src/data/nav.yml
@@ -68,10 +68,12 @@
pages:
- title: Spin up Geek movie shop architecture
url: '/automate-workflows/error-inbox/spin-up-geek-movie'
- - title: Create a workload
- url: '/automate-workflows/error-inbox/create-a-workload'
- - title: Track and triage errors in error inbox
- url: '/automate-workflows/error-inbox/set-up-error-inbox'
+ - title: Set up errors inbox
+ url: '/automate-workflows/error-inbox/set-up-errors-inbox'
+ - title: Triage your errors
+ url: '/automate-workflows/error-inbox/triage-errors'
+ - title: Manage your triaged errors
+ url: '/automate-workflows/error-inbox/manage-errors'
- title: Build apps
icon: nr-build-apps
url: '/build-apps'
diff --git a/src/markdown-pages/automate-workflows/error-inbox/index.mdx b/src/markdown-pages/automate-workflows/error-inbox/index.mdx
index 5f96824f1..906959260 100644
--- a/src/markdown-pages/automate-workflows/error-inbox/index.mdx
+++ b/src/markdown-pages/automate-workflows/error-inbox/index.mdx
@@ -2,13 +2,13 @@
path: '/automate-workflows/error-inbox'
title: 'Resolve Errors Faster with Full Stack Error Tracking'
template: 'LabOverviewTemplate'
-description: 'Use New Relic to qucikly track errors in your application with the help of error inbox.'
+description: 'Use New Relic to qucikly track errors in your application with the help of errors inbox.'
---
You're a developer of an eCommerce website called Geek's movie shop. You made some recent changes in your site's architecture and introduced some new features. The changes are ready to go live. However, you know that it's hard to identify the blast radius of errors once the application is in production. Since the changes are going to impact thousands of your customers, you want to find out if these changes will have any negative effect on them before pushing it to production.
-To ensure a smooth experience for your customers, you can use Error Inbox to track errors across you stack and take action on them before they impact your customers.
+To ensure a smooth experience for your customers, you can use errors inbox to track errors across you stack and take action on them before they impact your customers.
@@ -27,8 +27,9 @@ Errors inbox is not available in the EU region.
In this lab, you:
- Spin up the infrastructure for Geek's movie shop
-- Create a workload in New Relic
-- Track and triage errors in error Inbox
+- Set up errors inbox
+- Triage your errors in errors inbox
+- Manage your triaged errors
diff --git a/src/markdown-pages/automate-workflows/error-inbox/manage-errors.mdx b/src/markdown-pages/automate-workflows/error-inbox/manage-errors.mdx
new file mode 100644
index 000000000..fb6929069
--- /dev/null
+++ b/src/markdown-pages/automate-workflows/error-inbox/manage-errors.mdx
@@ -0,0 +1,87 @@
+---
+path: '/automate-workflows/error-inbox/manage-errors'
+title: 'Manage your triaged errors'
+template: 'GuideTemplate'
+description: 'Managed your triaged errors in errors inbox'
+duration: 15
+procIdx: 4
+---
+
+
+
+This procedure is part of a lab that teaches you how to track full stack errors using errors inbox.
+
+Each procedure in the lab builds upon the last, so make sure you've completed the last procedure, [Triage your errors](/automate-workflows/error-inbox/triage-errors), before starting this one.
+
+
+
+## Change filter
+By default, errors inbox show all the unresolved errors on the main screen. Once the error status is updated to resolved or ignored, you no longer see the error on the main screen. However, you can change the filter to view these errors.
+
+The main screen of errors inbox has a filter pane right below the top nav.
+
+
+Click **Unresolved** to change the filter value.
+
+
+Here, you see three options in the dropdown. Select **Ignored**.
+
+
+Your errors inbox now show all the ignored error groups.
+
+
+## Optional
+
+### Connect errors inbox to Jira
+Connect errors inbox to jira to qucikly and easily create tickets containing error details and link to the stack trace. It allows you to collaborate and resolve errors faster.
+
+Connect your errors inbox to jira:
+
+
+
+Click on the Jira integration icon on the far right side of the error group you want to connect to Jira.
+
+
+
+
+Click **Add JIRA Workspace** from the dropdown.
+
+
+
+
+Fill in the fields on the next page and click **Test connection** to ensure that your details are correct. Then, click **Save destination**.
+
+
+
+
+Next, set up a template. Click the jira integration icon against the error group and select **Add New Template +**.
+
+
+
+
+Add **Jira destination**, **Project**, and **Issue type** on the next page and click **Update message** to save the template.
+
+
+
+
+Here, you can also click **Send test notification** to preview the ticket in your jira board before saving the template. Note that a test notification will create a jira ticket in your workspace.
+
+
+
+
+Now you can create jira ticket by clicking the jira integration icon on the far right side of the error group and selecting a template.
+
+
+
+You can also connect errors inbox with Slack and CodeStream. Read [our docs](https://docs.newrelic.com/docs/errors-inbox/errors-inbox/) to learn more about the supported integrations.
+
+
+
+# Summary:
+In this lab, you set up errors inbox to track and triage errors in your application. You also managed triaged errors in errors inbox and integrated your errors inbox with jira to help you effectively collaborate and resolve errors faster from across your stack.
+
+# Homework
+Now that you know how to track and triage errors using errors inbox, here are some other things to familiarize yourself even more with errors inbox.
+- Read our documentation on [errors inbox](https://docs.newrelic.com/docs/errors-inbox/errors-inbox/)
+- Read our blog [Collaborate and fix errors quickly with Errors Inbox and workloads](https://newrelic.com/blog/how-to-relic/track-errors-errors-inbox)
+- Read our blog [Error Tracking Across Your Entire Stack with New Relic Errors Inbox](https://newrelic.com/blog/how-to-relic/error-tracking-with-errors-inbox)
\ No newline at end of file
diff --git a/src/markdown-pages/automate-workflows/error-inbox/set-up-error-inbox.mdx b/src/markdown-pages/automate-workflows/error-inbox/set-up-error-inbox.mdx
deleted file mode 100644
index 4ccba3de3..000000000
--- a/src/markdown-pages/automate-workflows/error-inbox/set-up-error-inbox.mdx
+++ /dev/null
@@ -1,199 +0,0 @@
----
-path: '/automate-workflows/error-inbox/set-up-error-inbox'
-title: 'Track and Triage errors in error inbox'
-template: 'GuideTemplate'
-description: 'Set up error inbox to track and triage errors across your stack'
-duration: 15
-procIdx: 3
----
-
-
-
-This procedure is part of a lab that teaches you how to track full stack errors using Error Inbox.
-
-Each procedure in the lab builds upon the last, so make sure you've completed the last procedure, [Create a workload](/automate-workflows/error-inbox/create-a-workload), before starting this one.
-
-
-
-Error inbox provides a unified error tracking to detect and triage errors from across your stack. You analyze the errors in context of the full stack and resolve them with precision.
-
-In this procedure, you track and triage errors across your stack using error inbox.
-
-
-
-Errors inbox is not available in the EU region.
-
-
-
-# Set up error inbox
-
-Before you start tracking error in errors inbox, you need to set it up.
-
-Enable error inbox as follow:
-
-
-
-From [New Relic One](one.newrelic.com), select **Errors Inbox** from the top nav.
-
-
-
-
-Click **Select Workload** and select **error-inbox-lab** workload from the drop down.
-
-
-
-
-You see the error groups across your workload here.
-
-
-
-
-Your error inbox is now set and you can start proactively monitoring errors across your stack.
-
-# Triage errors
-
-You can triage error groups directly from the main screen. Triaging helps removing the noise from your error inbox so you focus on the high impact errors.
-
-## Error details
-
-By default, errors inbox shows all your unresolved errors on one screen. To understand the root cause of these errors, you need more details. For instance:
-
-Click on **pika.exceptions:ChannelWrongStateError** error.
-
-
-This takes you to error details page. You find full context of the issue here including **Occurances**, **Stack Trace** and others.
-
-
-Stack trace is especially important since it helps you narrow down the cause of the problem.
-Under **Stack Trace**, click **Show all** in bottom right corner.
-
-
-This shows you the full stack trace.
-
-
-By taking a closer look at the above trace, you know for sure that something is wrong in your payment service. Now you can fix it before pushing the changes to production.
-
-
-
-You can also integrate [CodeStream](https://newrelic.com/codestream) with your errors inbox. This allows you to explore the stack trace in your IDE on a click of a single button. Once you've configured CodeStream, click ** Open in IDE** button to navigate to your IDE and explore the error.
-
-
-
-## Change the error status
-
-Each error in errors inbox has **unresolved** status by defulat. But you can set your error status as resolved, or ignored and filter your inbox by status.
-
-### Set the error status as 'Resolved'
-Once you fixed the issue, you come back to errors inbox and change its status to resolved.
-
-Navigate to **Errors inbox** in New Relic One.
-
-
-You were told that another developer on your team has fixed **pika.exceptions:ChannelWrongStateError** but the errors inbox still has this issue marked as unresolved. Change it's status:
-
-Click **Unresolved** against the error.
-
-
-You see two options in the dropdown here. Select **Resolve**.
-
-
-Once the status is updated, you no longer see the error on the main screen. However, if the error still persists, then it'll automatically be marked as unresolved.
-
-### Set the error status as 'Ignored'
-Some errors are expected and part of the system as it operates. Set those errors as ignored:
-
-Navigate to **Errors inbox** in New Relic One.
-
-
-Take a quick scan of the errors here. There's one **builtins:AssertionError**.
-
-
-This error is expected since the payment was aborted by the user and there's nothing you can do about it. Ignore this error:
-
-Click **Unresolved** against the error and then select **Ignore** from the dropdown.
-
-
-Once the status is updated, you no longer see the error on the main screen until you stop ignoring or change the filter to include ignored error groups.
-
-## Change filter
-By default, errors inbox show all the unresolved errors on the main screen. Once the error status is updated to resolved or ignored, you no longer see the error on the main screen. However, you can change the filter to view these errors.
-
-The main screen of errors inbox has a filter pane right below the top nav.
-
-
-Click **Unresolved** to change the filter value.
-
-
-Here, you see three options in the dropdown. Select **Ignored**.
-
-
-Your errors inbox now show all the ignored error groups.
-
-
-## Assign errors
-Change the errors inbox filter to show all the unresolved errors.
-
-
-Oops! you were told that somebody fixed **pika.exceptions:ChannelWrongStateError** error but you still see it under unresolved errors. You don't know who fixed this error previously and there's no way for you to find that out. To avoid such situation in future, assign the error from inside errors inbox.
-
-Click the human icon on the far right side of the error group.
-
-
-Enter the email address of the person you want to assign error to, and click **+**.
-
-
-The error is now assigned and its now easier for you to keep a track of who worked on the error.
-
-
-
-Currently assigning an error group to a user does not send a notification. Notifications of assignment and changes to error groups will be coming soon.
-
-
-## Connect an inbox to Jira
-Connect errors inbox to jira to qucikly and easily create tickets containing error details and link to the stack trace. It allows you to collaborate and resolve errors faster.
-
-Connect your errors inbox to jira:
-
-
-
-Click on the Jira integration icon on the far right side of the error group you want to connect to Jira.
-
-
-
-
-Click **Add JIRA Workspace** from the dropdown.
-
-
-
-
-Fill in the fields on the next page and click **Test connection** to ensure that your details are correct. Then, click **Save destination**.
-
-
-
-
-Next, set up a template. Click the jira integration icon against the error group and select **Add New Template +**.
-
-
-
-
-Add **Jira destination**, **Project**, and **Issue type** on the next page and click **Update message** to save the template.
-
-
-
-
-Here, you can also click **Send test notification** to preview the ticket in your jira board before saving the template. Note that a test notification will create a jira ticket in your workspace.
-
-
-
-
-Now you can create jira ticket by clicking the jira integration icon on the far right side of the error group and selecting a template.
-
-# Summary:
-In this lab, you set up errors inbox to track and triage errors in your application. You also integrated your errors inbox with jira to help you effectively collaborate and resolve errors faster from across your stack.
-For more help
-
-# Homework
-Now that you know how to track and triage errors using errors inbox, here are some other things to familiarize yourself even more with errors inbox.
-- Read our documentation on [errors inbox](https://docs.newrelic.com/docs/errors-inbox/errors-inbox/)
-- Read our blog [Collaborate and fix errors quickly with Errors Inbox and workloads](https://newrelic.com/blog/how-to-relic/track-errors-errors-inbox)
-- Read our blog [Error Tracking Across Your Entire Stack with New Relic Errors Inbox](https://newrelic.com/blog/how-to-relic/error-tracking-with-errors-inbox)
\ No newline at end of file
diff --git a/src/markdown-pages/automate-workflows/error-inbox/create-a-workload.mdx b/src/markdown-pages/automate-workflows/error-inbox/set-up-errors-inbox.mdx
similarity index 79%
rename from src/markdown-pages/automate-workflows/error-inbox/create-a-workload.mdx
rename to src/markdown-pages/automate-workflows/error-inbox/set-up-errors-inbox.mdx
index 32f22d23e..176ce1b0b 100644
--- a/src/markdown-pages/automate-workflows/error-inbox/create-a-workload.mdx
+++ b/src/markdown-pages/automate-workflows/error-inbox/set-up-errors-inbox.mdx
@@ -1,26 +1,28 @@
---
-path: '/automate-workflows/error-inbox/create-a-workload'
-title: 'Create a workload in New Relic'
+path: '/automate-workflows/error-inbox/set-up-errors-inbox'
+title: 'Set up errors inbox'
template: 'GuideTemplate'
-description: 'Create a workload consisting of geek movie services'
+description: 'Set up errors inbox in New Relic'
duration: 15
procIdx: 2
---
-This procedure is part of a lab that teaches you how to track full stack errors using Error Inbox.
+This procedure is part of a lab that teaches you how to track full stack errors using errors inbox.
-Each procedure in the lab builds upon the last, so make sure you've [set your lab environment](/automate-workflows/error-inbox/spin-up-geek-movie), before starting this one.
+Each procedure in the lab builds upon the last, so make sure you've [set your lab environment](/automate-workflows/error-inbox/spin-up-geek-movie) before starting this one.
-
-You can group specific apps and services that you want to monitor in a workload. This allows you to get an aggregated view of health and activity of the entities in the workload. You can also use workloads with error inbox to detect issues and track errors across your entire stack.
+Your app is now running in a development environment and your goal is to use errors inbox to proactively debug your application before deploying it to production. To observe your application in errors inbox, you first create a workload.
-In this procedure, you create a workload with all the geek movie shop services.
+A workload groups specific apps and services that you want to monitor and provides an aggregated view of the health and activities of the entities in the workload.
+
+In this procedure, you create a workload with all the geek movie shop services and observe this workload in errors inbox.
-# Create a workload
+## Create a workload
+Before you observe your application in errors inbox, you need to create a workload.
@@ -33,7 +35,7 @@ Click **+ Create a workload** in top right hand corner.
-Name your workload as _error-inbox-lab_. Under **Select entities**, click **+ Add** for each of the geek shop services to include it in the workload.
+Name your workload as _error-inbox-lab_. Under **Select entities**, click **+ Add** for each of the following geek shop services to include it in the workload.
- geek-shop-cart-service
- geek-shop-catalogue-service
@@ -54,12 +56,37 @@ Click **Create a workload** once you've added all the services.
This creates a workload with all the geek-movie services for you and automatically redirects you to view the workload in New Relic.
-
+
+
+Read more about workloads in [our docs](https://docs.newrelic.com/docs/new-relic-one/use-new-relic-one/workloads/workloads-isolate-resolve-incidents-faster/).
+
+Now that you have created workload, you can set up errors inbox.
+
+## Set up errors inbox
+Set up errors inbox to start tracking errors across your workload.
+
+
+
+
+From [New Relic One](one.newrelic.com), select **Errors Inbox** from the top nav.
+
+
+
+
+Click **Select Workload** and select **error-inbox-lab** workload from the drop down.
+
+
+
+
+You see the error groups across your workload here.
+
+
+
-Now that you have created workload, you can set up error inbox.
+Your errors inbox is now set and you can start proactively monitoring errors across your stack.
-This procedure is part of a lab that teaches you how to track full stack errors using Error Inbox. Now that you've created a workload, continue on to next procedure [Track and triage errors in error inbox](/automate-workflows/error-inbox/set-up-error-inbox).
+This procedure is part of a lab that teaches you how to track full stack errors using errors inbox. Now that you've set up errors inbox, continue on to next procedure, [Triage your errors](/automate-workflows/error-inbox/triage-errors).
\ No newline at end of file
diff --git a/src/markdown-pages/automate-workflows/error-inbox/spin-up-geek-movie.mdx b/src/markdown-pages/automate-workflows/error-inbox/spin-up-geek-movie.mdx
index a79d95834..0905d76c6 100644
--- a/src/markdown-pages/automate-workflows/error-inbox/spin-up-geek-movie.mdx
+++ b/src/markdown-pages/automate-workflows/error-inbox/spin-up-geek-movie.mdx
@@ -9,11 +9,13 @@ procIdx: 1
-This procedure is part of a lab that teaches you how to track full stack errors using Error Inbox. If you haven't already, check out the [lab introduction](/automate-workflows/error-inbox).
+This procedure is part of a lab that teaches you how to track full stack errors using errors inbox. If you haven't already, check out the [lab introduction](/automate-workflows/error-inbox).
-Geek's Movie Shop (former Stan's Robot Shop) is a web application that consists of several interconnected microservices like cart, catalogue, payment, user, and more. These services are instrumented with New Relic for performance monitoring and full visibility across all layers. The application also has a loader service that generates traffic In this lab, we use New Relic's Error Inbox for full stack error tracking.
+Geek's Movie Shop is a web application that consists of several interconnected microservices like cart, catalogue, payment, user, and more. These services are instrumented with New Relic for performance monitoring and full visibility across all layers.
+The application is currently running in development environment and you're trying to catch any errors that you can before pushing the site to production. To test your application services, you're also generating load with a special service running in your docker network.
+In this lab, you use New Relic's Errors Inbox to track and triage errors across your stack.
## Set up your environment
@@ -29,7 +31,7 @@ git clone https://github.com/newrelic-experimental/error-inbox-lab-material.git
-Open the cloned repo in your IDE and create a _.env_ file from _env.template_ and set these variables:
+Open the cloned repo in your IDE and edit the _.env_ file to set these variables:
```
DOCKERHUB_USER=username
@@ -44,13 +46,13 @@ Here, NEW_RELIC_LICENSE_KEY is your liscence key for New Relic account. Your app
-Navigate to the root directory of your application and execute the _env.sh_ script to export these variables:
+Navigate to the root directory of your application and export these variables:
```bash
-./env.sh
+source .env
```
-This scripts takes all the variables you declared in _.env_ file and set them so you don't have to manually set all the environment variables to run your application.
+This sets all the environment variables needed to run your application.
Build and run the application:
@@ -92,6 +94,6 @@ Leave the application running so you could see the telemetry data in New Relic.
-This procedure is part of a lab that teaches you how to track full stack errors using Error Inbox. Now that you've set up your lab environment, continue on to next procedure [Create a workload](/automate-workflows/error-inbox/create-a-workload).
+This procedure is part of a lab that teaches you how to track full stack errors using errors inbox. Now that you've set up your lab environment, continue on to next procedure, [Set up errors inbox](/automate-workflows/error-inbox/set-up-errors-inbox).
diff --git a/src/markdown-pages/automate-workflows/error-inbox/triage-errors.mdx b/src/markdown-pages/automate-workflows/error-inbox/triage-errors.mdx
new file mode 100644
index 000000000..10bad100b
--- /dev/null
+++ b/src/markdown-pages/automate-workflows/error-inbox/triage-errors.mdx
@@ -0,0 +1,118 @@
+---
+path: '/automate-workflows/error-inbox/triage-errors'
+title: 'Triage your errors'
+template: 'GuideTemplate'
+description: 'Track and triage errors across your stack with errors inbox'
+duration: 15
+procIdx: 3
+---
+
+
+
+This procedure is part of a lab that teaches you how to track full stack errors using errors inbox.
+
+Each procedure in the lab builds upon the last, so make sure you've completed the last procedure, [Set up errors inbox](/automate-workflows/error-inbox/set-up-errors-inbox), before starting this one.
+
+
+
+Errors inbox provides a unified error tracking to detect and triage errors from across your stack. Since you want to ensure a smooth experience for your customers, you can use errors inbox to analyze the errors in full context and resolve them before they impact your customers.
+
+In this procedure, you track and triage errors across your stack using errors inbox.
+
+
+
+Errors inbox is not available in the EU region.
+
+
+
+## Triage your errors in errors inbox
+
+You can triage error groups directly from the main screen. Triaging helps removing the noise from your errors inbox so you focus on the high impact errors.
+
+### See error details
+
+By default, errors inbox shows all your unresolved errors on one screen. To understand the root cause of these errors, you need more details. For instance:
+
+Click on **pika.exceptions:ChannelWrongStateError** error.
+
+
+This takes you to error details page. You find full context of the issue here including **Occurances**, **Stack Trace**, and others.
+
+
+Stack trace is especially important since it helps you narrow down the cause of the problem.
+Under **Stack Trace**, click **Show all** in bottom right corner.
+
+
+This shows you the full stack trace.
+
+
+By taking a closer look at the above trace, you know for sure that something is wrong in your payment service. If this were your real world application, you could use this stack trace and other details from this view to fix the issue before pushing your code to production. As you're focused on using errors inbox in this lab, ignore this step.
+
+
+
+You can also integrate [CodeStream](https://newrelic.com/codestream) with your errors inbox. This allows you to explore the stack trace in your IDE on a click of a single button. Once you've configured CodeStream, click ** Open in IDE** button to navigate to your IDE and explore the error.
+
+
+
+### Set error statuses
+
+Each error in errors inbox has **unresolved** status by defulat. But you can set your error status as resolved, or ignored and filter your inbox by status.
+
+#### Set the error status as 'Resolved'
+Once you fixed the issue, you come back to errors inbox and change its status to resolved.
+
+Navigate to **Errors inbox** in New Relic One.
+
+
+You were told that another developer on your team has fixed **pika.exceptions:ChannelWrongStateError** but the errors inbox still has this issue marked as unresolved. Change it's status:
+
+Click **Unresolved** against the error.
+
+
+You see two options in the dropdown here. Select **Resolve**.
+
+
+Once the status is updated, you no longer see the error on the main screen. However, if the error still persists, then it'll automatically be marked as unresolved.
+
+#### Set the error status as 'Ignored'
+Some errors are expected and part of the system as it operates. Set those errors as ignored:
+
+Navigate to **Errors inbox** in New Relic One.
+
+
+Take a quick scan of the errors here. There's one **builtins:AssertionError**.
+
+
+This error occured because the service was aborted due to connection failure at user's end and there's nothing you can do about it. Ignore this error:
+
+Click **Unresolved** against the error and then select **Ignore** from the dropdown.
+
+
+Once the status is updated, you no longer see the error on the main screen until you stop ignoring or change the filter to include ignored error groups.
+
+### Assign errors
+You were told that somebody on your team fixed **pika.exceptions:ChannelWrongStateError** error and you marked it resolved. However, you come back to see the error is marked unresolved again.
+
+
+Oops! You don't know who fixed this error previously and there's no way for you to find that out. To avoid such situation in future, assign the error from inside errors inbox.
+
+Click the person icon on the far right side of the error group.
+
+
+You've decided you're going to take care of this error yourself. Enter your email address and click **+**.
+
+
+The error is now assigned to you.
+
+
+
+Currently assigning an error group to a user does not send a notification. Notifications of assignment and changes to error groups will be coming soon.
+
+
+Once you assign error in errors inbox, it keeps a track of who worked on the error.
+
+
+
+This procedure is part of a lab that teaches you how to track full stack errors using errors inbox. Now that you've triaged errors in errors inbox, continue on to next procedure, [Manage your triaged errors](/automate-workflows/error-inbox/manage-errors).
+
+
\ No newline at end of file