Daniel Tomes

Below is the code references to the issue and this will follow through to costs by cluster type in the gold layer. [isSQLAnalytics Boolean]( https://github.com/databrickslabs/overwatch/blob/993ea86e956e7e01453fc58de33e2543392ea957/src/main/scala/com/databricks/labs/overwatch/pipeline/SilverTransforms.scala#L443)

Query History was added in 0.7.0 endpoints and other dbsql dims will be coming soon.

Also, while you're deep in the weeds, if you have time, it'd be AWESOME to figure out why I'm having issues parallelizing the API calls. I don't want to serialize...

UPDATE: I found the issue that started this thought process. The issue was I made a change a while back to simplify the "cluster IDs with new states" logic and...

@Sriram-databricks -- looks like most of this will be removed and so won't be needed. Please review and close this with the new APICall implementation for clsuterEvents

I have the DB SQL metrics dim created in dev already. Hoping to get it released in 0.5.1 as a preview entity. That said, I believe the query history is...

This will be enabled after API Modernization #302

Related to #134

Hey @mohanbaabu1996 and @shravanshibu90 -- can you guys look at if there are any compatibility issues by using a newer version of hugo. We're on v76 and they're on 104....

confirmed, default_tags is not published by clusters service either. In fact, it appears that default_tags are not published to audit logs for any services -- confirmed by the snippet below....