Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Daily release/09 27 24 morning #18783

Merged
merged 21 commits into from
Sep 27, 2024
Merged
Changes from 1 commit
Commits
Show all changes
21 commits
Select commit Hold shift + click to select a range
c524b5b
chore: minor corrections/typos
brnhensley Aug 29, 2024
4dec8d9
chore: cleanup and minor fixes
brnhensley Aug 29, 2024
68a6ed0
chore: add language identifier
brnhensley Aug 29, 2024
6590194
Update src/content/docs/accounts/accounts-billing/new-relic-one-prici…
brnhensley Sep 19, 2024
7c416bd
fix: typo
brnhensley Sep 19, 2024
8573ccf
fix: typo
brnhensley Sep 19, 2024
4314df6
Merge branch 'develop' into patch-2
brnhensley Sep 24, 2024
643d2c4
chore: add lang identifier
brnhensley Sep 26, 2024
a34bfb6
Update src/content/docs/alerts/create-alert/create-alert-condition/cr…
brnhensley Sep 26, 2024
2312ebc
Update src/content/docs/alerts/create-alert/create-alert-condition/cr…
brnhensley Sep 26, 2024
4b3cab5
Update src/content/docs/alerts/create-alert/create-alert-condition/cr…
brnhensley Sep 26, 2024
498a578
Update src/content/docs/alerts/create-alert/create-alert-condition/cr…
brnhensley Sep 26, 2024
d334840
Update src/content/docs/alerts/create-alert/create-alert-condition/cr…
brnhensley Sep 26, 2024
5f3d8c2
Update src/content/docs/alerts/create-alert/create-alert-condition/cr…
brnhensley Sep 26, 2024
34fd43e
Update src/content/docs/alerts/create-alert/create-alert-condition/cr…
brnhensley Sep 26, 2024
b59cca6
Update src/content/docs/alerts/create-alert/create-alert-condition/cr…
brnhensley Sep 26, 2024
9efb44a
fix(alerts): Reformatted some queries
rhetoric101 Sep 26, 2024
ecea9a3
fix(alerts): Format snippets with WHERE inside SELECT.
rhetoric101 Sep 26, 2024
dcc09fb
fix(alerts): Add more snippet formatting
rhetoric101 Sep 26, 2024
56aad66
fix(alerts): Fix indentation of subquery again
rhetoric101 Sep 26, 2024
dee427f
Merge pull request #18524 from brnhensley/patch-2
rhetoric101 Sep 26, 2024
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
fix: typo
Co-authored-by: Rob Siebens <rsiebens@newrelic.com>
  • Loading branch information
brnhensley and rhetoric101 authored Sep 19, 2024
commit 8573ccf77347d520a1eb071ef2705ca5f6aa0279
Original file line number Diff line number Diff line change
@@ -733,7 +733,7 @@ Loss of signal settings include a time duration and a few actions.
</DNT>
Once a signal is considered lost, you have a few options:
* Close all current open incidents: This closes all open incidents that are related to a specific signal. It won't necessarily close all incidents for a condition. If you're alerting on an ephemeral service, or on a sporadic signal, you'll want to choose this action to ensure that incidents are closed properly. The GraphQL node name for this is [`closeViolationsOnExpiration`](/docs/apis/nerdgraph/examples/nerdgraph-api-loss-signal-gap-filling/#loss-of-signal).
* Open new incidents: This will open a new incident when the signal is considered lost. These incidents will indicate that they are due to a loss of signal. Based on your incident preferences, this should trigger a notification. The graphQL node name for this is [`openViolationOnExpiration`](/docs/apis/nerdgraph/examples/nerdgraph-api-loss-signal-gap-filling/#loss-of-signal)
* Open new incidents: This will open a new incident when the signal is considered lost. These incidents will indicate that they are due to a loss of signal. Based on your incident preferences, this should trigger a notification. The graphQL node name for this is [`openViolationOnExpiration`](/docs/apis/nerdgraph/examples/nerdgraph-api-loss-signal-gap-filling/#loss-of-signal).
* When you enable both of the above actions, we'll close all open incidents first, and then open a new incident for loss of signal.
* Do not open "lost signal" incidents on expected termination. When a signal is expected to terminate, you can choose not to open a new incident. This is useful when you know that a signal will be lost at a certain time, and you don't want to open a new incident for that signal loss. The GraphQL node name for this is [`ignoreOnExpectedTermination`](/docs/apis/nerdgraph/examples/nerdgraph-api-loss-signal-gap-filling/#loss-of-signal).

Loading
Oops, something went wrong.