Observability maturity test

How mature is your observability setup? Take the test to find out if your observability setup delivers the visibility and insights your business needs.

Take the test

Modern digital services generate enormous amounts of operational data. But data alone does not create value. The real advantage comes when you gain full visibility across your systems, understand performance in real time, and turn technical data into insights the business can act on.

Our Observability Maturity Test helps you understand where your organisation stands today.

By answering 12 quick questions, you will assess how mature your organisation is when it comes to observability practices, tools, and ways of working.

The test takes just 5–8 minutes to complete. Once finished, you will receive an overview highlighting your strengths, identifying potential gaps, and pointing to the areas where you can create the biggest improvements.

Step 1 of 15

Name(Required)

First Last

Email(Required)

Company Name

Select your closest Conscia office(Required)

Please consent to our privacy policy before we proceed(Required)

By submitting this test, Conscia will store your personal information and be able to follow up with you regarding your inquiry. Read more about the purpose and legal basis in our privacy policy.

I agree to the privacy policy.

Newsletter

Yes, I would like to sign up for Conscia’s newsletter.

We do not send out email communication at fixed intervals, but you can expect a few emails from us per month. You can revoke your consent by clicking on the unsubscribe link in any email communication from us. Please read all the terms and how your data is handled here.

Which role best describes you in your current job?(Required)

Please enter your job role here.

To what extent do you use KPIs/SLOs to determine anomalies and alerting on these?

– No KPI’s defined: System issues are usually reported by end users to the service desk.

– Full KPI strategy: A complete KPI plan is in place for the entire IT system, aligned with business goals, which triggers proactive alerts before problems affect users.

To what extent do you use KPIs/SLOs to determine anomalies and alerting on these?(Required)

0= No KPIs defined | 10 = Full KPI strategy

To what extent are your current KPIs based on business requirements?

To what extent are your current KPIs based on business requirements?(Required)

0= Not aligned w/ business | 10 = KPI strategy w/ business

Do you have quality gateways in place to ensure that changes do not negatively impact production?

Do you have quality gateways in place to ensure that changes do not negatively impact production?(Required)

Quality gateways ensures that certain predefined criteria are met before moving on to production

Yes

To what extent are quality targets measured and validated, manually or automatically, to prevent deployment if they are not met?

To what extent are quality targets measured and validated, manually or automatically, to prevent deployment if they are not met?(Required)

0= Manual quality gateway | 10 = Auto quality gateway

To what extent do you use KPIs/SLO as quality gateways before implementing changes?

Ex. KPIs based on real-time data of errors, performance, saturation and traffic thresholds.

To what extent do you use KPIs/SLO as quality gateways before implementing changes?(Required)

0= Never use KPIs/SLOs | 10 = Always use KPIs/SLOs

To what extent is observability established to support stability and performance across the organisation?

To what extent is observability established to support stability and performance across the organization?(Required)

0= None/team based option | 10 = Across all IT silos

To what extent does your organisation formally report across functional domains and management levels?

To what extent does your organisation formally report across functional domains and management levels?*(Required)

The IT department keeps performance data private and doesn’t share it with other teams.

Performance data is shared outside IT, but it’s mostly in reports and isn’t really used much.

Different teams formally share and discuss performance data, focusing on stability and performance.

Performance data is shared across the whole company and regularly communicated, serving as the main source of truth.

Do you report key availability and performance metrics in real-time using flexible role-based dashboards?

Do you report key availability and performance metrics in real-time using flexible role-based dashboards?*(Required)

Yes

To some extend

How are you using observability tools in your test environment?

How are you using observability tools in your test environment?(Required)

Select the statement that matches your situation best.

No diagnostic tools are available in the test environment. Problems are returned to development and infrastructure teams for investigation using developer tools, which makes collaboration between teams ineffective.

Comprehensive diagnostic visibility or code analysis is implemented retrospectively only when tests cannot be completed properly. The type of diagnostic information requested by developers determines the instrumentation attempted.

Most critical tests are instrumented with adequate diagnostic visibility, covering most of the supporting environment and other pertinent information (such as system logs). Tests may often need to be re-executed to attempt to reproduce the fault.

During testing, it’s essential to monitor and record diagnostic data for all transactions. This includes tracking all application components to a code-level, as well as system performance metrics such as CPU usage, memory and logs.

Which statement fits your organisation the most, when it comes to incident response?

Which statement fits your organization the most, when it comes to incident response?(Required)

Select the statement that matches your situation best.

We use basic monitoring tools to react to incidents, but the focus is primarily on fixing issues after it comes up. Incidents are often discovered by customers or end-users before internal teams.

We are beginning to use real-time data to inform the incident response team, but this is not yet fully integrated. There is manual analysis needed to determine root causes.

We are using real-time data to identify and resolve issues quickly, and we have a proces for monitoring and responding to incidents before they significantly affect customers.

We use advanced tools and techniques to monitor our systems proactively, discover potential issues before they become critical, and we continuously improve based on incident post-mortems.

To what extent is you organisation managing your monitoring tools to avoid overlap and ensure each one provides unique value?

To what extent is you organization managing your monitoring tools to avoid overlap and ensure each one provides unique value?(Required)

0= Tool overlap/ no control | 10 = Strategic tool mgmt.

To what extent has your organisation consulted independent observability advisors to be successful in your observability strategy?

To what extent is you organization managing your monitoring tools to avoid overlap and ensure each one provides unique value?(Required)

0= No independent advisory | 10 = Incorporated advisory