Yes, it’s possible to include the Databricks job name in your Brooklyn audit tables, but it won’t happen automatically. Right now, only the job run ID is being logged, so you’d need to extend your audit logic a bit. One common approach is to pass the Databricks job name as a parameter or environment variable when the job triggers the dbt model, and then capture that along with the run ID in your audit insert. That way, both the run ID and the job name are stored in the Brooklyn fact/dim tables, and you can easily build dashboards that focus on Databricks jobs instead of just dbt models.