-
Notifications
You must be signed in to change notification settings - Fork 114
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
6bb187b
commit ba93d28
Showing
37 changed files
with
402 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
55 changes: 55 additions & 0 deletions
55
src/markdown-pages/automate-workflows/error-inbox/create-a-workload.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,55 @@ | ||
--- | ||
path: '/automate-workflows/error-inbox/create-a-workload' | ||
title: 'Create a workload in New Relic' | ||
template: 'GuideTemplate' | ||
description: 'Create a workload consisting of geek movie services' | ||
duration: 15 | ||
procIdx: 2 | ||
--- | ||
|
||
<Callout variant="course" title="lab"> | ||
|
||
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 [set your lab environment](/automate-workflows/error-inbox/spin-up-geek-movie), before starting this one. | ||
|
||
</Callout> | ||
|
||
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. | ||
|
||
In this procedure, you create a workload with all the geek movie shop services. | ||
|
||
# Create a workload | ||
|
||
<Steps> | ||
<Step> | ||
|
||
Navigate to [New Relic One](one.newrelic.com) and sign in with your account. | ||
</Step> | ||
<Step> | ||
|
||
Click **+ Create a workload** in top right hand corner. | ||
![create a workload](../../../images/error-inbox/create-a-workload.png) | ||
</Step> | ||
<Step> | ||
|
||
Name your workload as _error-inbox-lab_. Under **Select entities**, scroll down to the geek shop services and click **+ Add** against each service to add it to workload. | ||
![add service to workload](../../../images/error-inbox/add-service-to-workload.png) | ||
</Step> | ||
<Step> | ||
|
||
Click **Create a workload** once you've added all the services. | ||
![create a workload with services](../../../images/error-inbox/create-a-service-workload.png) | ||
</Step> | ||
</Steps> | ||
|
||
This creates a workload with all the geek-movie services for you and automatically redirects you to view the workload in New Relic. | ||
![error inbox lab workload](../../../images/error-inbox/workload-ui.png) | ||
|
||
Now that you have created workload, you can set up error inbox. | ||
|
||
<Callout variant="course" title="lab"> | ||
|
||
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). | ||
|
||
</Callout> |
44 changes: 44 additions & 0 deletions
44
src/markdown-pages/automate-workflows/error-inbox/index.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,44 @@ | ||
--- | ||
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.' | ||
--- | ||
|
||
<Intro> | ||
|
||
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. | ||
|
||
</Intro> | ||
|
||
<Callout variant='important'> | ||
|
||
Errors inbox is not available in the EU region. | ||
|
||
</Callout> | ||
|
||
<div style="display: flex;"> | ||
|
||
<div style="flex: 1;"> | ||
|
||
## Learning Objectives | ||
|
||
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 | ||
|
||
</div> | ||
|
||
<div style="flex: 1;"> | ||
|
||
## Requirements | ||
|
||
- Create a free [New Relic account](https://newrelic.com/signup?utm_source=developer-site) | ||
- Install [Docker](https://www.docker.com/) | ||
|
||
</div> | ||
|
||
</div> |
Oops, something went wrong.