cancel
Showing results for 
Search instead for 
Did you mean: 
Data Engineering
cancel
Showing results for 
Search instead for 
Did you mean: 

Does Databricks persist the alert results history?

Nick_Hughes
New Contributor III

Hi, this seems like a really basic feature to have, an alert is generated and spits out the email, but the URL doesn't take you to the events list that happened at that time but just the query in the editor (via the alert config screen). We're really struggling to make use out of this feature with no persisted history and no way seemingly to format the alert in to a table of results. Please can I request the persisting of historic alert events as a feature request or can someone let me know if im just not seeing it? Thank you

1 ACCEPTED SOLUTION

Accepted Solutions

Prabakar
Esteemed Contributor III
Esteemed Contributor III

@Nick Hughes​ I was looking at our ideas portal and could see an API feature was requested for the Alerts (DB-I-4289). To create an API for the alerts and pull data, we might need to keep the alert history persistent. So this feature should suffice your requirement.

You can refer to the below post:

https://community.databricks.com/s/question/0D53f00001SAWH5CAP/is-there-an-alerting-api-please

View solution in original post

9 REPLIES 9

Prabakar
Esteemed Contributor III
Esteemed Contributor III

Hi @Nick Hughes​ , for the feature request you can raise it in our ideas portal so that it will have direct visibility to the product team and develop in the future.

Nick_Hughes
New Contributor III

@Prabakar Ammeappin​ does this mean it's definitely not a current feature and history is lost?

Hubert-Dudek
Esteemed Contributor III

You mean alerts for jobs runs?

If yes you can write own script to handle that as API for jobs have information related to alerts like timeout or status failed https://docs.databricks.com/dev-tools/api/latest/jobs.html#operation/JobsRunsList

On Azure when you run databricks notebooks via Data Factory it have really nice feature to manage failure state and you can create own alerts (via Logic Apps)

Nick_Hughes
New Contributor III

Hiya,

No, not for job runs, for the business alerting feature off scheduled queries

Prabakar
Esteemed Contributor III
Esteemed Contributor III

@Nick Hughes​  Do you mean the dbsql queries and alerts?

Nick_Hughes
New Contributor III

This one @Prabakar Ammeappin​  -https://docs.databricks.com/sql/user/alerts/index.html

Hubert-Dudek
Esteemed Contributor III

aaa now I get it. The best option would be that Databricks add SQL alerts history to SQL API https://docs.databricks.com/sql/api/index.html

Prabakar
Esteemed Contributor III
Esteemed Contributor III

@Nick Hughes​  For Alerts, I don't think we have a persistent history. The SQL API mentioned by @Hubert Dudek​  works for the SQL query history like status, time range, endpoint, user id. But it won't give you the history of the alerts that you set. So for the SQL alert history, I would suggest you raise a feature request.

https://docs.databricks.com/sql/api/query-history.html#queryfilter

Prabakar
Esteemed Contributor III
Esteemed Contributor III

@Nick Hughes​ I was looking at our ideas portal and could see an API feature was requested for the Alerts (DB-I-4289). To create an API for the alerts and pull data, we might need to keep the alert history persistent. So this feature should suffice your requirement.

You can refer to the below post:

https://community.databricks.com/s/question/0D53f00001SAWH5CAP/is-there-an-alerting-api-please

Welcome to Databricks Community: Lets learn, network and celebrate together

Join our fast-growing data practitioner and expert community of 80K+ members, ready to discover, help and collaborate together while making meaningful connections. 

Click here to register and join today! 

Engage in exciting technical discussions, join a group with your peers and meet our Featured Members.