19913d85-f662-4518-a9a1-7adc1793dfd4.png){kind=small}
Channels
announcements
dagster-airbyte
dagster-airflow
dagster-bigquery
dagster-cloud
dagster-cube
dagster-dask
dagster-dbt
dagster-de
dagster-ecs
dagster-feedback
dagster-kubernetes
dagster-machine-learning
dagster-noteable
dagster-releases
dagster-serverless
dagster-showcase
dagster-snowflake
dagster-spatial
dagster-support
dagster-wandb
dagstereo
data-platform-design
events
faq-read-me-before-posting
gigs-freelance
github-discussions
introductions
jobs
random
tools
豆瓣酱帮
Title
j
Jose Estudillo
12/28/2022, 5:37 PMHi Team, I’m trying to get a solution to monitor sensors that fail (for example when they run the checks to decide which jobs to run). I haven’t found things like
hooksrun_failure_sensorI’m trying to do a grahql query, not having much luck either:
query RunsQuery {
sensorsOrError(repositorySelector: {
repositoryName: "*",
repositoryLocationName: "*"}
) {
__typename
... on Sensors {
results {
name
}
}
}
}d
daniel
12/28/2022, 5:47 PMHey Jose - the query that powers the tick history in Dagit for a particular sensor looks something like this (the naming is a bit odd - "instigation/instigator" includes both schedules and sensors and refers to things that can instigate runs)
instigationStateOrError(instigationSelector: $instigationSelector) {
__typename
... on InstigationState {
id
instigationType
nextTick {
timestamp
}
ticks(dayRange: $dayRange, limit: $limit, cursor: $cursor, statuses: $statuses) {
id
status
timestamp
cursor
skipReason
runIds
error {
message
}
}
}
}j
Jose Estudillo
12/28/2022, 5:49 PMThanks Daniel, so there is no better solution than just having a sensor running that query and checking for errors?
d
daniel
12/28/2022, 5:50 PMThat's what we currently expose, yeah - and because of the nature of what you're monitoring, you may want to use something other than a sensor to run the query?
Kind of a 'who watches the watchmen' situation
j
Jose Estudillo
12/28/2022, 5:51 PMyeah I get you, was thinking the same, just didn’t want to introduce anything new if I could avoid it
but in this case you kind of have to
thanks again for your help!
:condagster: 1
@daniel I’m struggling to get anything to match
can I use wildcards in these expressions?
instigationStateOrError(instigationSelector: {
repositoryName: "default",
repositoryLocationName: "default",
name:""
})to match anything,
*d
daniel
12/28/2022, 6:15 PMThat query can only refer to a specific individual sensor
If supporting hooks for sensor/schedule failures in a more built-in way would be helpful then you could also file a feature request issue