Dear Geof
thanks for your suggestion. Fair point, and I understand the intention to open a support ticket.
That said, for a premium service like Roon, relying on users to repeatedly report outages doesn’t align with modern software development practices.
Today, platforms typically operate with end-to-end observability and proactive operations, meaning:
- Continuous telemetry across clients, core, and third-party integrations;
- Synthetic monitoring to simulate real user journeys (e.g. playback sessions);
- Distributed tracing to pinpoint issues across the stack;
- Centralized logging and metrics with SLI- and SLO-based alerting;
- Automated detection of degraded user experience at scale.
In a modern DevOps / SRE setup, incidents are identified and addressed proactively, often before users even notice.
For me, opening tickets for recurring service interruptions feels like a legacy, reactive model. I would expect a service at this level to be self-monitoring and managed accordingly.
I also understand this is not in the hands of you as the forum moderators. Hence, I hope senior management at Roonlabs reads along here from time to time and start acting accordingly.
Regards, Stefan