Elastic Cloud integration

Observation:

All the following steps must be done after the External Integration (Custom) has already been configured by the ElvenWorks team and the following data has been provided: API URL, Header (HEADER) and Payload. Request integration via chat on the platform or on the website.


1 – In your Elastic Cloud, go to Stack Management:



2 – In the Alerts and Insights part, click on Connectors:

 

3 – Click on Create Connector and select Webhook. Configure it with the data that was generated by External Integration:

 

Connector Name: Name of the Connector you want to create

Method: POST

URL: <API_URL generated when creating the External Integration>

Authentication is not required and the option can be unchecked


Check the ADD HTTP HEADER option:

Key: User-Agent

Value: 1PcustomAuth/1.0

 

Click on Save & Test.

4 – On the next screen, paste the payload generated by External Integration into BODY:

 

title: Title of the Incident that will appear on 1P

description: Description of the Incident that will appear on 1P

external_aggregate_key: Incident Identifier (If you want to have N Monitors for the same integration)

action: Type of action (Alarmed or Resolved)

organization: 1P Organization ID

 

Once configured, click Run.


Ready, your Elastic Cloud + 1P integration is created and a Test Incident notification will arrive on the Platform. Remembering that this Connector configuration in Elastic Cloud follows the configurations that are in your Alerting Rules.

Observation:

All the following steps must be done after the External Integration (Custom) has already been configured by the ElvenWorks team and the following data has been provided: API URL, Header (HEADER) and Payload. Request integration via chat on the platform or on the website.


1 – In your Elastic Cloud, go to Stack Management:



2 – In the Alerts and Insights part, click on Connectors:

 

3 – Click on Create Connector and select Webhook. Configure it with the data that was generated by External Integration:

 

Connector Name: Name of the Connector you want to create

Method: POST

URL: <API_URL generated when creating the External Integration>

Authentication is not required and the option can be unchecked


Check the ADD HTTP HEADER option:

Key: User-Agent

Value: 1PcustomAuth/1.0

 

Click on Save & Test.

4 – On the next screen, paste the payload generated by External Integration into BODY:

 

title: Title of the Incident that will appear on 1P

description: Description of the Incident that will appear on 1P

external_aggregate_key: Incident Identifier (If you want to have N Monitors for the same integration)

action: Type of action (Alarmed or Resolved)

organization: 1P Organization ID

 

Once configured, click Run.


Ready, your Elastic Cloud + 1P integration is created and a Test Incident notification will arrive on the Platform. Remembering that this Connector configuration in Elastic Cloud follows the configurations that are in your Alerting Rules.

Experimente agora, grátis!