[Maps] Update asset tracking tutorial with production consideration for rule check interval (#158664)

Fixes #127289

## Summary

Updates the asset tracking tutorial docs with considerations for running
in production.

For a better demo experience the tutorial uses a 5 second interval for
rule checking, but a very low interval can be problematic for running in
production.

I'm suggesting backporting these doc changes to 8.3 which the first
release to have a **Circuit breakers** section in
https://www.elastic.co/guide/en/kibana/8.3/alerting-production-considerations.html
that is most relevant to the added note in this PR.

---------

Co-authored-by: gchaps <33642766+gchaps@users.noreply.github.com>
This commit is contained in:
Nick Peihl 2023-05-31 13:38:41 -04:00 committed by GitHub
parent bc041fd467
commit 9d7d6f9213
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -440,7 +440,9 @@ image::maps/images/asset-tracking-tutorial/construction_zones.png[]
[float]
==== Step 2. Configure an alert
Create a new alert by defining a rule and a connector. The rule includes the conditions that will trigger the alert, and the connector defines what action takes place once the alert is triggered. In this case, each alert will log a message to the Kibana log.
Create a new alert by defining a rule and a connector. The rule includes the conditions that will trigger the alert, and the connector defines what action takes place once the alert is triggered. In this case, each alert will log a message to the {kib} log.
NOTE: For this example, you will set the rule to check every 5 seconds. However, when running in production, consider setting a higher check interval (such as 1 minute) to avoid performance issues. Refer to <<alerting-production-considerations,Alerting production considerations>> for more information.
. Open *{stack-manage-app}*, and then click *{rules-ui}*.
. Click *Create rule*.