[Alerting][Docs] adds documentation on NTP based synchronization #90747
Conversation
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
gmmorris
added
Feature:Alerting
Team:ResponseOps
|
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
|
Pinging @elastic/kibana-docs (Team:Docs) |
gmmorris
added
the
release_note:skip
4 tasks
pmuellr
reviewed
Feb 9, 2021
| @@ -6,6 +6,7 @@ | |||
|
|
|||
| * *Persistence*: all task state and scheduling is stored in {es}, so if {kib} is restarted, alerts and actions will pick up where they left off. Task definitions for alerts and actions are stored in the index specified by `xpack.task_manager.index` (defaults to `.kibana_task_manager`). It is important to have at least 1 replica of this index for production deployments, since if you lose this index all scheduled alerts and actions are also lost. | |||
| * *Scaling*: multiple {kib} instances can read from and update the same task queue in {es}, allowing the alerting and action load to be distributed across instances. In cases where a {kib} instance no longer has capacity to run alert checks or actions, capacity can be increased by adding additional {kib} instances. | |||
| * *Synchronization*: {es} and {kib} instances use the system clock to determine the current time. To ensure schedules are triggered when expected, you should synchronize the clocks of all nodes in the cluster using a time service such as http://www.ntp.org/[Network Time Protocol]. | |||
There was a problem hiding this comment.
The description of this is fine, but the context seems wrong. This isn't a benefit, AFAIK, it's a requirement. :-)
If it does happen to be a benefit, then the sentence above needs to be changed to
This has THREE major benefits:
There was a problem hiding this comment.
Good point, I missed that 😬
There was a problem hiding this comment.
|
Jenkins, test it |
gmmorris
added a commit
to gmmorris/kibana
that referenced
this pull request
Feb 11, 2021
…stic#90747) Adds docs on usage of NTP to sync nodes in a prod setting for alerting.
gmmorris
added a commit
to gmmorris/kibana
that referenced
this pull request
Feb 11, 2021
* master: [Alerting][Docs] adds documentation on NTP based synchronization (elastic#90747)
gmmorris
added a commit
that referenced
this pull request
Feb 11, 2021
) (#91101) Adds docs on usage of NTP to sync nodes in a prod setting for alerting.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Part of #89997
Adds documentation on NTP based synchronization to the Alerting docs.
I've kept the description close to the Watcher one on purpose: https://www.elastic.co/guide/en/elasticsearch/reference/current/trigger-schedule.html
Checklist
Delete any items that are not applicable to this PR.