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.

Sign up for GitHub

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

Jump to bottom

Small changes to doc #3233

Merged
merged 1 commit into from
Jul 22, 2021
Merged

Small changes to doc #3233

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
11 changes: 1 addition & 10 deletions ...frastructure/infrastructure-alert-conditions/alert-infrastructure-processes.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ redirects:
Use New Relic infrastructure's **Process running** [alert condition](/docs/infrastructure/new-relic-infrastructure/configuration/infrastructure-alerts-add-edit-or-view-host-alert-information) to be notified when a set of processes on your [filtered hosts](/docs/infrastructure/new-relic-infrastructure/filter-group/filter-sets-organize-your-infrastructure-hosts) stop running for a configurable number of minutes. This is useful, for example, when:

* Any of the processes on the hosts stop reporting
* A process you expected to start on a host (such as a new program) is not actually running
* A process is running too many instances on one host

This feature's flexibility allows you to easily filter what hosts and processes to monitor and when to notify selected individuals or teams. In addition, the email notification includes links to help you quickly troubleshoot the situation.

Expand Down Expand Up @@ -67,15 +67,6 @@ By applying filters to the hosts and processes that are important to your busine
**Solution:** Use the **At least one process is running** threshold.
</Collapser>

<Collapser
id="default-successful"
title="Validate that services started successfully"
>
**Problem:** When provisioning new hosts, you want to open a violation if a required service fails to successfully start up.

**Solution:** Use the **No processes are running** (default) threshold.
</Collapser>

<Collapser
id="multiple-runaway"
title="Watch for runaway processes or configuration problems"
Expand Down