Rafert
Joined 13 years ago
Joined 13 years ago
1: https://news.ycombinator.com/item?id=44194082 2: https://clickhouse.com/use-cases/observability
Sounds like there’s no EDR running on the dev machines? You should have more to investigate if Sentinel One/CrowdStrike/etc were running.
I would not call this “generally discouraged” when APIs generally surface a created_at timestamp in their responses. A real life example are Stripe IDs which have similar properties (k-sorted) as UUIDv7: https://brandur.org/nanoglyphs/026-ids#ulids
After some research on available alternatives that don't break the bank, we decided to deploy a self-hosted instance of Metabase[0]. This took only a few minutes to set up using their Docker image[1] and it has much better graphing capabilities and you can easily put a custom layout together for dashboards. Upgrading is similarly easy (just redeploy). Also easy to configure: additional data sources, hiding or changing the data type of a column, G Suite sign-in for our domain. It has 'models' as sources of truth to build other queries in - eg a single definition of an 'active user'.
In short, moving from Blazer to Metabase was a huge win for us. Highly recommend it if you need anything more than Blazer's table output.
[0]: https://github.com/metabase/metabase [1]: https://docs.render.com/deploy-metabase
The chances of that seem extremely low at this point. The contents of a version 7 UUID have not changed since work started on RFC 4122 bis in October 2022: https://author-tools.ietf.org/iddiff?url1=draft-ietf-uuidrev...