Monitoring Assets in a FreshnessPolicy World

[askvinni]

Put simply, I'm wondering how we can monitor assets and pass the information to an external system (or use the external system to periodically query the dagster instance, either way works) once freshness checks are fully phased out in favor of the revamped FreshnessPolicyies.

I recall the old way when the now legacy freshness policies were first introduced was by pulling properties on the assets from the asset graph, but when I did some digging some weeks ago through the codebase, exported symbols, and properties attached to the asset graph, I couldn't find anything similar with the new APIs.

This is pretty important in ensuring that the assets conform to the SLAs we're setting, and I don't mind writing custom code and working with non-public exports, but am looking for some guidance in what the intended way is and where to look for the relevant information in the instance backend or asset graph state.

[cmpadden]

Hi @askvinni, one possible solution would be for you to use the underlying GraphQL query that we are also using in the UI:

• freshnessStatusInfo and internalFreshnessPolicy

Though I should mention, that as this is an internal API it may be subject to change. Hope this helps.

And if you're using Dagster+ you can observe and monitor all of the assets and set SLAs through the UI.