Skip to content

Monitoring code location status #19734

Answered by alangenfeld
stevenmurphy12 asked this question in Q&A
Discussion options

You must be logged in to vote

periodically ping the Deployment tab of the UI and look for code locations that are showing as failed

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

Replies: 2 comments 1 reply

Comment options

You must be logged in to vote
1 reply
@garethbrickman
Comment options

Answer selected by stevenmurphy12
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
area: code-locations Related to Code Locations and Definitions
3 participants