Skip to content

[DOC] Update docs for new monitoring alerts#80922

Merged
chrisronline merged 3 commits intoelastic:masterfrom
chrisronline:monitoring/alert_docs
Oct 21, 2020
Merged

[DOC] Update docs for new monitoring alerts#80922
chrisronline merged 3 commits intoelastic:masterfrom
chrisronline:monitoring/alert_docs

Conversation

@chrisronline
Copy link
Copy Markdown
Contributor

@chrisronline chrisronline commented Oct 16, 2020 •
edited by lcawl
Loading

@chrisronline chrisronline added review Team:Monitoring Stack Monitoring team v8.0.0 release_note:skip Skip the PR/issue when compiling release notes v7.10.0 v7.11.0 labels Oct 16, 2020
@chrisronline chrisronline self-assigned this Oct 16, 2020
@elasticmachine
Copy link
Copy Markdown
Contributor

elasticmachine commented Oct 16, 2020

Pinging @elastic/stack-monitoring (Team:Monitoring)

@chrisronline chrisronline requested review from a team and lcawl October 19, 2020 19:48
lcawl
lcawl approved these changes Oct 19, 2020
View reviewed changes
Copy link
Copy Markdown
Member

@lcawl lcawl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

@ravikesarwani
Copy link
Copy Markdown
Contributor

ravikesarwani commented Oct 19, 2020

Hi Chris,
I reviewed the doc changes and looks to be some discrepancies on the default values and also a typo in JMV description.

Disk usage threshold
Disk full average > 80% for the last 5 minutes

JVM memory threshold
This alert is triggered when a node runs a consistently high JVM memory usage.
JVM memory heap used percent > 85% average for the last 5 minutes

Missing monitoring data
* No data for last 15 minutes
* Alert re-notify interval => every 6 hour

Can we discuss?

@chrisronline
Copy link
Copy Markdown
Contributor Author

chrisronline commented Oct 20, 2020

@ravikesarwani

It looks like the code doesn't match that.

Disk usage threshold

Disk full average > 80% for the last 5 minutes
Code is > 90% for the last 5 minutes

Missing monitoring data

No data for last 15 minutes
No data for last 5 minutes
Alert re-notify interval => every 6 hour
interval => every 1d

We should open a ticket to change this in the code if this is unintended. WDYT?

@ravikesarwani
Copy link
Copy Markdown
Contributor

ravikesarwani commented Oct 20, 2020

Yes, we should change the code IMO. The default values I am talking about were documented and reviewed by the various field folks and we should start with that.

@chrisronline
Copy link
Copy Markdown
Contributor Author

chrisronline commented Oct 20, 2020

@ravikesarwani Done #81176

ravikesarwani
ravikesarwani suggested changes Oct 21, 2020
View reviewed changes
Copy link
Copy Markdown
Contributor

@ravikesarwani ravikesarwani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For "JVM memory threshold" typo needs to be fixed "when a node runs a consistently high JVM memory usage".

@chrisronline chrisronline merged commit 5aa197b into elastic:master Oct 21, 2020
@chrisronline chrisronline deleted the monitoring/alert_docs branch October 21, 2020 17:38
chrisronline added a commit to chrisronline/kibana that referenced this pull request Oct 21, 2020
@chrisronline
[DOC] Update docs for new monitoring alerts (elastic#80922)
0faa796 
* Update docs for new alerts

* PR feedback

* Fix bad copy/pate
@chrisronline chrisronline mentioned this pull request Oct 21, 2020
Merged
chrisronline added a commit to chrisronline/kibana that referenced this pull request Oct 21, 2020
@chrisronline
[DOC] Update docs for new monitoring alerts (elastic#80922)
e9d1d5d 
* Update docs for new alerts

* PR feedback

* Fix bad copy/pate
@chrisronline chrisronline mentioned this pull request Oct 21, 2020
Merged
@kibanamachine kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label Oct 23, 2020
@kibanamachine
Copy link
Copy Markdown
Contributor

kibanamachine commented Oct 23, 2020

Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync.

@kibanamachine kibanamachine removed the backport missing Added to PRs automatically when the are determined to be missing a backport. label Oct 23, 2020
chrisronline added a commit that referenced this pull request Oct 23, 2020
@chrisronline
[DOC] Update docs for new monitoring alerts (#80922) (#81365)
489fb4c 
* Update docs for new alerts

* PR feedback

* Fix bad copy/pate
chrisronline added a commit that referenced this pull request Oct 23, 2020
@chrisronline
[DOC] Update docs for new monitoring alerts (#80922) (#81364)
b0f7915 
* Update docs for new alerts

* PR feedback

* Fix bad copy/pate
@chrisronline
Copy link
Copy Markdown
Contributor Author

chrisronline commented Oct 23, 2020

Backport:

7.x: b0f7915
7.10: 489fb4c

@chrisronline chrisronline mentioned this pull request Nov 5, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@lcawl lcawl lcawl approved these changes

+1 more reviewer

@ravikesarwani ravikesarwani ravikesarwani approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@chrisronline chrisronline

Labels

docs release_note:skip Skip the PR/issue when compiling release notes review Team:Monitoring Stack Monitoring team v7.10.0 v7.11.0 v8.0.0

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

[Monitoring][Doc] Update out of the box alerting page

5 participants

@chrisronline @elasticmachine @ravikesarwani @kibanamachine @lcawl