-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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.
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
Pre-configured Connectors #58914
Labels
Feature:Actions
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
Comments
peterschretlen
added
Feature:Actions
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
labels
Feb 28, 2020
Pinging @elastic/kibana-alerting-services (Team:Alerting Services) |
Related: #56433 "Default actions" for managed versions of the stack (ESS/ECE/ECK) would be implemented as pre-configured connectors |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Feature:Actions
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
Describe a specific use case for the feature:
Today, connectors for actions are created in the UI or via API. We’d like to add the ability to pre-configure connectors, before Kibana has even started:
Describe the feature:
A “preconfigured” connector would be different from a regular connector in the following ways:
Pre-configured connectors are defined in Kibana.yml or directly in code. Sensitive configuration like credentials can use either kibana.yml or the Kibana keystore.
Because these connectors have all the information they need to execute prior to startup, a saved object representation isn’t necessary. They can be stored in-memory on each Kibana server instance.
Example:
Say I’d like to provide 4 out of the box connectors:
Kibana.yml
These connectors would be setup in kibana.yml as follows. Note sensitive properties like passwords can also be stored in the Kibana keystore:
Creating an alert with a pre-configured connector
When a user attaches an action to their alert, they select from a list of available action types.
Select the Slack type. Even though I haven’t yet created a connector, because a pre-configured connector is installed, it’s automatically selected:
The dropdown is populated with other pre-configured slack connectors
The “pre-configured” label distinguishes them from space-aware connectors that use saved objects:
Managing pre-configured connectors
Pre-configured connectors appear in the connector list, regardless of which space the user is in. They are tagged as “pre-configured” and cannot be deleted. Note I've listed Server Log here as a pre-configured connector, it should be converted to one.
Clicking on a pre-configured connector will show the description but not any of the configuration. A message indicates that this is a pre-configured connector and cannot be edited.
When action types are registered, they can indicate if they can allow pre-configuration, configuration at runtime, or both. In this case, the “Server Log” and “System ABC” action types allow pre-configuration only, so are excluded from the list when creating new connectors:
The text was updated successfully, but these errors were encountered: