| Thanks for the feedback! >- Are there any recommendations for scaling (e.g. benchmarks) on how many spans/s are supported on what hardware? With Uptrace, I was able to achieve 10k spans / second on a single core by running the binary with GOMAXPROCS=1. That is 1-3 terrabytes of compressed data each month which is more than most users need. Practically, you are limited by the $$$ you are willing to spend on ClickHouse servers, not by Uptrace ingestion speed. So my recommendation is to scale Uptrace vertically by throwing more cores at it. That will allow you to go very very far. >- Is there support for SSO for self-hosted installation? So far the only way to add news users is via the YAML config. We are considering to add a REST API or a CLI tool for the same purpose, but it is not clear how that would work with the YAML. Regarding the SSO, it would be nice if you can provide an app that already does that so we can better estimate the complexity. But so far we don't have such plans. >- Can I easily disable certain features? (e.g. alerting) Yes, most YAML sections just can be removed / commented out to disable the feature. |
I have no other good examples for SSO than Grafana.
But something I would love to see more for logins are Application Tokens. We use Cloudflare Access for Team related logins, which will send such a token in the header, so the application can use it to authorize a user and by which group a user is in it can enable/disable features
https://developers.cloudflare.com/cloudflare-one/identity/au...
This solved our needs for multiple sign in options, as all is now managed through Cloudflare access, but this is obviously not a solution for everyone