Migrate guide content #1952
Migrate guide content #1952
Conversation
| - The `Environment` where your code is deployed and running in which you'd like the alert rule applied. | ||
| - The `Actions` that should be taken when the associated conditions are met. Mainly -- where you'd like to channel this alert. | ||
|
|
||
| #### **Creating a good set of alert rules means:** |
There was a problem hiding this comment.
guessing we're bolding these for styling? technically we shouldn't need to do that when its a header
| A tag-based condition can be used as the sole condition for an alert rule or in conjunction with additional conditions to fine tune the rule: | ||
|
|
||
|  | ||
| > In this rule we're leveraging custom tags that our developers added through the Sentry SDK, telling Sentry to notify us via our _#sentry-urgent_ **Slack** channel when _Enterprise_ customers are experiencing errors in critical parts of our application. |
There was a problem hiding this comment.
out of habit im almost always put newlines between blocks just to ensure it doesnt do something weird. i haven't used this syntax before though so as long as you verified its rendering it should be fine.
|
|
||
| ``` | ||
| An event's tags match {key} {match} {value} | ||
| ``` |
|
|
||
| Sentry provides two threshold conditions based either on the event occurrence or number of affected users: | ||
|
|
||
| ``` |
There was a problem hiding this comment.
any reason to not use a list? seems odd to put in a codeblock
|
|
||
| Every Issue in Sentry has a defined state - _Unresolved_, _Resolved_ or _Ignored_. Read about [Issue States](/workflow/notifications/#issue-states) for more information. | ||
|
|
||
| #### **1. Regression Alert** |
There was a problem hiding this comment.
i dont think we should use numerical prefixes in headers, especially in this kind of case
|
|
||
| - **Issue Resolved** - When a new issue is spotted in your code, it's marked with an `unresolved` state. The state changes to `resolved` when a project team member resolves it (either by manually changing its state in the UI or by [submitting a fix](/workflow/releases/?platform=browser#after-associating-commits)) or when the project’s auto-resolve feature is configured. Once the state changes to resolved, an email is sent to all project team members. | ||
|
|
||
|  |
There was a problem hiding this comment.
indentation might break things, but if you verified its fine. either way i would just not indent when its not supposed to be
|
|
||
| Configuring the release version ID on the SDK will associate every error that happens in your application runtime with a specific release version of your code. This way you know exactly when an error was introduced into your source code. It also unlocks these powerful features and workflows: | ||
|
|
||
| 1. **Suspect Commits & Suggested Assignee** - With a release in place, Sentry can suggest suspect commits that might have an introduced the error to your code and through that commit also suggest the author as an assignee. |
| @@ -0,0 +1,119 @@ | |||
| [Getting started](/error-reporting/quickstart/?platform=node) with Sentry error monitoring is easy and straightforward. In this post, we will provide the recommended ToDos checklist for setting up your Sentry organization account and making the most of it. | |||
|
|
|||
| ## 1. Enable Single Sign-On Access | |||
There was a problem hiding this comment.
more numbers in headers makin me sad
|
|
||
|  | ||
|
|
||
| ### > **What's in a Project?** |
There was a problem hiding this comment.
do we really need this > notation here?
| 2. Set the match logic and its fingerprint for it, in your Project's Settings. | ||
|
|
||
|
|
||
| ### 1. Identify Match Logic |
| ## Best Practices | ||
|
|
||
| * [Set up your Sentry Account](/guides/getting-started/) | ||
|
|
There was a problem hiding this comment.
not sure whhat this does with the empty line, but might mess up rendering
There was a problem hiding this comment.
also future note: we need to make it so we can auto generate child toc
I've migrated the guides and tutorials to Gatsby. Visual inspection completed. Looks like all the images and formats are working properly.