Job webhook alerts are not sending authorization headers

[564824]

Hi,

I have set up a webhook which will send the event to a lambda in AWS. I validate the event through the credentials given while creating the webhook but sometimes the event that is being sent from databricks does not contain authorization in the headers so the alert is not coming through. I would like to know how to resolve this.

Thank you,

Muthu

[Anonymous]

@Muthu Kumaran​ :

If the event being sent from Databricks to your Lambda function sometimes does not contain authorization headers, you may need to modify your webhook configuration or Lambda function code to handle this situation. Here are a few suggestions:

1. Check the webhook configuration: Make sure that you have configured the webhook to include the authorization header in the event payload. You can do this by specifying the appropriate header fields in the webhook configuration.
2. Check the Databricks job configuration: If the event is being triggered by a Databricks job, make sure that the job is configured to include the authorization header in the event payload. You can do this by specifying the appropriate header fields in the job configuration.
3. Modify the Lambda function code: You can modify the code of your Lambda function to handle the situation where the authorization header is missing from the event. For example, you can check if the authorization header is present in the event headers, and if not, you can use a default or fallback value.
4. Use a middleware layer: You can use a middleware layer to intercept the event before it is sent to the Lambda function. The middleware can then add the authorization header if it is missing before forwarding the event to the Lambda function.

Overall, it's important to ensure that the authorization header is consistently included in the event payload. This can help prevent issues with missing headers and ensure that your alerting system works as expected.

[564824]

Hi,

Thanks for replying. I checked the webhook configuration and the credentials I set are still there. We have a fallback value in case but it would be better if the event has the authorization headers consistently from a security point of view. For the same job, we are sometimes getting the authorization details in the event but sometimes we are not getting the authorization details in the event.