Preconfigured connectorsedit

You can preconfigure a connector to have all the information it needs prior to startup by adding it to the kibana.yml file.

Preconfigured connectors offer the following benefits:

  • Require no setup. Configuration and credentials needed to execute an action are predefined, including the connector name and ID.
  • Appear in all spaces because they are not saved objects.
  • Cannot be edited or deleted.

Preconfigured connectors exampleedit

This example shows a valid configuration for two out-of-the box connectors: Slack and Webhook.

      actionTypeId: .slack      
      name: 'Slack #xyz'        
        webhookUrl: ''
      actionTypeId: .webhook
      name: 'Email service'
        url: ''
        method: post
          header1: value1
          header2: value2
        user: elastic
        password: changeme

The key is the connector identifier, my-slack1 in this example.

actionTypeId is the action type identifier.

name is the name of the preconfigured connector.

config is the configuration specific to the connector type.

secrets is the sensitive configuration, such as username, password, and keys, specific to the connector type.

Sensitive properties, such as passwords, can also be stored in the Kibana keystore.

Built-in preconfigured connectorsedit

Kibana provides one built-in preconfigured connector:

View preconfigured connectorsedit

When you open the main menu, click Stack Management > Rules and Connectors. Preconfigured connectors appear on the Connectors tab, regardless of which space you are in. They are tagged as “preconfigured”, and you cannot delete them.

Connectors managing tab with pre-configured

Clicking a preconfigured connector shows the description, but not the configuration. A message indicates that this is a preconfigured connector.

Pre-configured connector view details