Can Data Observability be triggered?

 Hello ​@Albert de Ruiter ,

thank you for your question. There is a Manual Run option under the 3 dots. That triggers the following API:

mutation RunObservability($gid: GID!) {
  runObservability(sourceId: $gid) {
    success
    __typename
  }
}

variables:
{
  "gid": "5f463b19-0000-7000-0000-0000000518c7"
}

Checking the underlying jobs, it triggers many imports and profilings on the background, so it is not just one job where you can monitoring if it’s done. I would need to think about the solution here - if nothing else is running, you can simply ask for running jobs and wait until none is running. But that is usually not the case. There is an option of the email notifications so might be something that could be incorporated in your process.

As for obtaining details, I found this query:

query SourceObservabilityOverview($gid: GID!, $from: Timestamp!, $to: Timestamp!) {
  source(gid: $gid) {
    publishedVersion {
      systemOverview(timeRange: {from: $from, to: $to}) {
        generalStatistics {
          connectionsCount
          catalogItemsCount
          __typename
        }
        domainStatistics {
          profiledCatalogItemsCount
          termsCount
          termInstancesCount
          catalogItemsWithTermsCount
          catalogItemsWithObservedTermsCount
          observedCatalogItemsWithRulesOnAttributesCount
          newTermsCount
          newTermInstancesCount
          unresolvedIssueCount
          __typename
        }
        dqStatistics {
          totalCount
          monitoredItemsCount
          results {
            id
            name
            count
            __typename
          }
          unresolvedIssueCount
          __typename
        }
        anomalyStatistics {
          anomaliesCount
          catalogItemsWithAnomaliesCount
          unresolvedIssueCount
          __typename
        }
        volumeAnomalyStatistics {
          anomaliesCount
          catalogItemsWithAnomaliesCount
          unresolvedIssueCount
          __typename
        }
        schemaChangeStatistics {
          unresolvedIssueCount
          addedAttributes
          addedCatalogItems
          changedAttributes
          deletedAttributes
          deletedCatalogItems
          __typename
        }
        freshnessStatistics {
          configuredCatalogItemCount
          executedCatalogItemCount
          unresolvedIssueCount
          __typename
        }
        __typename
      }
      __typename
    }
    __typename
  }
}

Variables:

{
  "gid": "5f463b19-0000-7000-0000-0000000518c7",
  "from": "2025-07-24T07:47:50.566Z",
  "to": "2025-07-31T07:47:50.566Z"
}

Let me know if this is something that can help you. You can always tweek the queries using playground to find additional properties and options.

Kind regards,

Anna