Curious how close to 'ready for use' the Observabi...
# getting-started
b
Curious how close to 'ready for use' the Observability features mentioned in the Roadmap are?
b
Hi Nick! Did you hve a particular feature in mind? We've thus far released basic usage statistics for warehouses (Snowflake, BigQuery, with Redshift coming soon) along with a Profiling feature for all SQL dbs
They can and are both being used today, although they are early features so are likely subject to some refinement
l
the backend support for timeseries metadata is "ready for use". Like John said we have support for a few metrics (usage, profiles etc.)
we will continue to add more metrics (freshness, completeness etc.) and will add the ability to evaluate predicates and alert - this will come in Q4
b
Thanks for the fast feedback.
l
👍 would love to understand your use-cases
t
Hey guys, initial use cases are: * Postgres/Greenplum connectivity * Identifying volume changes that could indicate data acquisition issues or other issues within a 24 hour period? * Identifying negative trends in load times or completion times that might indicate an immanent problem with load SLAs? * General notifications - what are the general notification mechanisms, can it be customised to a group of users? * Role-based access to datasets * Configurable dashboards
l
Role-based access to datasets: this is already available cc @big-carpet-38439
Copy code
Identifying volume changes that could indicate data acquisition issues or other issues within a 24 hour period?
* Identifying negative trends in load times or completion times that might indicate an immanent problem with load SLAs?
We definitely want to tackle these as major use cases since we've heard from others too that they are important
general notification mechanisms: we will provide API and stream based consumption of notification events
t
ok thanks @loud-island-88694 - that helps ... so Q4 ETA for volume/freshness/alerting metrics?
l
yes
👍 2