The Settings page enables you to change which Heartbeat indices are displayed by the Uptime app, configure alert connectors, and set expiration/age thresholds for TLS certificates.
Uptime settings apply to the current space only. To segment different uptime use cases and domains, use different settings in other spaces.
- To access this page, go to Observability > Uptime.
To modify items on this page, you must have the
allprivilege granted to your role. The
allprivilege grants cluster administration operations, like snapshotting, node shutdown/restart, settings update, rerouting, or managing users and roles.
Specify a comma-separated list of index patterns to match indices in Elasticsearch that contain Heartbeat data.
The pattern set here only restricts what the Uptime app displays. You can still query Elasticsearch for data outside of this pattern.
Alerts work by running checks on a schedule to detect conditions. When a condition is met, the alert tracks it as an alert instance and responds by triggering one or more actions. Actions typically involve interaction with Kibana services or third party integrations. Connectors allow actions to talk to these services and integrations.
Click Create connector and follow the prompts to select a connector type and configure its properties. After you create a connector, it’s available to you anytime you set up an alert action in the current space.
For more information about each connector, see action types and connectors.
You can modify certificate thresholds to control how Uptime displays your TLS values in the Certificates page. These settings also determine which certificates are selected by any TLS alert you create.
A standard security requirement is to make sure that your TLS certificates have not been
valid for longer than a year. To help you keep track of which certificates you may want to refresh,
modify the Age limit value to