monitored_jobs what are the parameters?

The

monitored_jobs

parameter is used in the context of Dagster's sensors, specifically for run failure sensors. According to the documentation,

monitored_jobs

accepts a list of jobs that the sensor will monitor. Here are the details of the

monitored_jobs

parameter: - monitored_jobs ( Optional [ List [ Union _[_[ JobDefinition](jobs#dagster.JobDefinition "dagster.JobDefinition") _,_[ GraphDefinition](graphs#dagster.GraphDefinition "dagster.GraphDefinition") , UnresolvedAssetJobDefinition , RepositorySelector , JobSelector , CodeLocationSelector ] ] ] ) – Jobs in the current code locations that will be monitored by this sensor. Defaults to None, which means the alert will be sent when any job in the code location matches the requested run_status. Jobs in external repositories can be monitored by using RepositorySelector or JobSelector. This parameter allows you to specify which jobs should trigger the sensor when they have a particular run status. If you do not specify any jobs, the sensor will default to monitoring all jobs within the code location for the specified run status. If you want to monitor jobs from external repositories, you can use

RepositorySelector

or

JobSelector

to specify those jobs. It's important to note that the

job_selection

parameter is deprecated in favor of

monitored_jobs

and will be removed in version 2.0 of Dagster.