Monitoring code location status #19734
-
I'm running a Kubernetes deployment with 3 code locations. Over the weekend, a scheduled job failed because the code location containing that schedule failed to load (due to a transient issue). I have Slack notifications enabled for when a job fails, though it did not work in this case because the job was never triggered (as the daemon would have no awareness of it). Is there a recommended means by which I could monitor the status of a code location? My current thought is I'd need to have an external process to periodically ping the Deployment tab of the UI and look for code locations that are showing as failed. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
You can query the webserver directly using GraphQL to get to the underlying information in the same way the UI does. You can reference the query that the UI does by observing it in the network tab of your browsers developer tools or locating the query in the dagster code base. https://docs.dagster.io/concepts/webserver/graphql#graphql-api |
Beta Was this translation helpful? Give feedback.
-
Dagster Cloud users can set up code location alerts policies |
Beta Was this translation helpful? Give feedback.
You can query the webserver directly using GraphQL to get to the underlying information in the same way the UI does. You can reference the query that the UI does by observing it in the network tab of your browsers developer tools or locating the query in the dagster code base.
https://docs.dagster.io/concepts/webserver/graphql#graphql-api