Performance has always been an important focus for us in Omega 365 — and we know it’s something we need to maintain every day. While many parts of the platform now perform very well, we also know there may still be applications or instances where there’s room for improvement.

To help us with this, we’ve put more structure and effort into performance monitoring — using solid data and better tooling to guide our work across all solutions.

The main KPI: Response Rate

One of our most important KPIs is Response Rate, which tracks how many requests are completed within 1 second. It’s a clear, measurable indicator of how responsive the system feels for our users — and it helps us stay focused on what matters

And what is a request?

A request is any interaction a user has with the system — such as opening an app, sorting a column, retrieving a list of organizational units, opening a report, or uploading a file. Every time a user clicks or performs an action, a request is sent, and the system responds.

The Response Rate shows the percentage of those requests that complete within one second — which means users get the result quickly. Tracking this metric allows us to monitor real-world system responsiveness across all parts of Omega 365.

We monitor this both hourly and daily, which makes it easier to spot trends or dips before they become real issues.

Hourly response rates — a useful view on short-term spikes or slowdowns.

The daily view gives us a broader perspective over time. In this case, we can clearly see a period with performance challenges leading up to March 26th. A dedicated effort to identify and address the root cause led to significant improvements in system performance.

Granular Insights

We monitor performance at the URL and application level, so we can spot bottlenecks quickly — even down to specific endpoints. This level of detail helps our teams respond proactively.

Debug Tracing for Full Transparency

We’ve also got debug tracing in place to drill into specific cases. Whether it's an occasional internal server error or a background process taking longer than expected, we can pinpoint the root cause fast.

A Shared Monitoring Approach Across All Solutions

We’ve worked to apply the same monitoring setup across all Omega 365 solutions. This gives us a consistent and unified view, no matter which module or environment we're working in — making it easier to catch issues early and improve performance where it matters most.

In Summary

We know that delivering good performance is not something you solve once — it requires ongoing attention, the right tools, and a willingness to learn and improve.

With a clear focus on response time, consistent monitoring across all solutions, and access to detailed metrics, we feel well-equipped to identify and resolve issues quickly.We’ll keep pushing to make Omega 365 faster and more responsive — for all users, in all parts of the platform.

If you experience areas where performance could be better, we’d really appreciate your feedback.