Bitbucket Pipeline Datadog should also have endpoint variable

[Nataraj]

This integration assumes that the datadog endpoint is https://app.datadoghq.com/ but the user endpoint is  https://us5.datadoghq.com/ then the integration fails to work .

DataDog endpoints could be housed in

US1 :  https://app.datadoghq.com/

US3:   https://us3.datadoghq.com/

US5:   https://us5.datadoghq.com/

etc

- pipe: atlassian/datadog-send-event:1.1.3

variables:

API_KEY: '<STRING>'

TITLE: '<STRING> '

# TEXT: '<string>' # Optional.

# PRIORITY: '<string>' # Optional.

# ALERT_TYPE: '<string>' # Optional.

# TAGS: '<string>' # Optional.

# DEBUG: '<boolean>' # Optional.

# EU_ENDPOINT: '<boolean>' # Optional.

Thanks

Nataraj

[Nataraj]

This integration assumes that the datadog endpoint is https://app.datadoghq.com/ but the user endpoint could be  https://us5.datadoghq.com/ then the integration fails to work .

DataDog endpoints could be housed in any of the regions 

https://docs.datadoghq.com/getting_started/site/

ITE SITE URL SITE PARAMETER LOCATION

US1 https://app.datadoghq.com datadoghq.com US

US3 https://us3.datadoghq.com us3.datadoghq.com US

US5 https://us5.datadoghq.com us5.datadoghq.com US

EU1 https://app.datadoghq.eu datadoghq.eu EU

US1-FED https://app.ddog-gov.com ddog-gov.com US

The EU_ENDPOINT could be renamed to DATADOG_SITE (i leave this to you) so that the user could point them to a specific endpoint or site 

- pipe: atlassian/datadog-send-event:1.1.3

variables:

API_KEY: '<STRING>'

TITLE: '<STRING> '

# TEXT: '<string>' # Optional.

# PRIORITY: '<string>' # Optional.

# ALERT_TYPE: '<string>' # Optional.

# TAGS: '<string>' # Optional.

# DEBUG: '<boolean>' # Optional.

# EU_ENDPOINT: '<boolean>' # Optional.

DATADOG_SITE :  https://app.datadoghq.com or https://us5.datadoghq.com

Thanks

Nataraj