Kode-1
Observability assessment

Find out what you can see in production, and what it costs to see it

We map the services that matter most against the logs, metrics and traces they emit, the tools that collect them, the alerts that fire on them and what it costs to keep them. You get a plain account of where you are blind, where you pay twice, and what to fix first, before anyone recommends a tool.

Trusted by
Westpac
Syrah Resources
Beyond Blue
BDO
Triple Zero
Praemium
Velrada
McMillan Shakespeare
Nufarm
Seek
QUT
UNE
Jim's Group

Most monitoring grew one incident at a time

A team adds a tool after an outage. Another team picks a different one for its platform. An acquisition brings a third. Each tool sends its own agent to the same servers, keeps its own copy of the logs and raises its own alerts. Years later there are dashboards nobody opens, alerts that page people for things customers never notice, and services customers do notice that have no instrumentation at all. The telemetry bill keeps rising and no one can say which part of it earns its keep. An assessment puts all of that on one page, so you make the next decision on evidence.

Signs it is time to assess

If two of these are true, start with an assessment.

Customers report outages first

The service desk hears about a slow checkout or a failed login before any alert fires.

Several tools, no shared view

Each team trusts its own dashboard, and an incident starts with an argument about whose numbers are right.

A bill nobody can explain

Telemetry costs rise with every new service, and the renewal arrives before anyone knows what is queried.

AI in production, unseen

Models and agents answer customers, and nobody can trace a wrong answer back to the prompt, retrieval or tool call behind it.

The regulator wants evidence

CPS 230 asks for critical operations monitored against tolerance levels, and a quarterly report does not show that.

A platform decision is coming

A renewal, a migration or a new cloud platform forces a tooling choice, and you want the facts before the sales calls.

What we look at

Coverage

  • Your critical services and the user journeys that depend on them
  • Which applications, AI workloads and infrastructure emit logs, metrics and traces, and which emit nothing useful
  • Where application performance monitoring is in place and where a request disappears between services

Tools and alerting

  • Every monitoring, logging and tracing tool in use, the agents each one installs and where they overlap
  • Dashboards and who uses them
  • Alerts: how many fire, who they page and whether they track anything a customer would feel

Reliability

  • Which services have an agreed objective for availability and latency
  • Whether alerting follows those objectives or fixed thresholds
  • How incidents are detected, handled and reviewed

Cost and obligations

  • Telemetry volume, retention and spend by source and by tool
  • Data collected and kept that nobody queries
  • The floor your obligations set, such as the ISM's twelve months of searchable logs, so savings never cut below it

Security telemetry

  • Which network, platform and application signals reach your security operations centre
  • Where operations and security collect the same data twice
  • Where neither team has the signals it needs

AI workloads

  • Whether prompts, model calls, retrieval and tool calls are traced
  • Whether latency, token cost and answer quality are measured per request
  • Whether the evidence AI governance asks for is produced as the system runs

How the assessment runs

Three steps, with the people who run your services and respond to incidents.

  1. 01

    Map

    We list the services and user journeys that matter most, and get read access to the tools in use and what they cost.

  2. 02

    Measure

    For each service we check coverage, alerting, reliability and spend, including AI workloads and the signals your security team relies on.

  3. 03

    Prioritise

    We rank the gaps by what customers feel first and by cost, and take your leadership team through the findings.

See where you stand before the next renewal

Scope and fee are fixed at a free scoping conversation.

Request an Observability Assessment

What you leave with

Findings

  • A coverage map of your critical services against logs, metrics and traces
  • The tools, agents, dashboards and alerts in use, and where they duplicate each other
  • A reliability view: which services have objectives and whether alerts follow them
  • Telemetry volume, retention and spend, set against what you must keep

Priorities

  • A ranked list of gaps, starting with the services customers feel first
  • Where cost can come out without going below what you must keep
  • Where AI workloads and security signals need tracing or routing
  • The questions the observability strategy has to answer

Why assess before choosing a tool

Much of the observability advice on offer comes attached to a platform, and the assessment that comes with it tends to conclude that the platform is the answer. We start from what you already run and what each tool costs, so the findings may say keep, consolidate or retire, and sometimes that the tool is fine and the gap is instrumentation or ownership. Collecting telemetry through an open standard keeps that choice open later, because changing tools no longer means instrumenting every application again.

Observability assessment

Start with a conversation

A partner replies within one business day.

Common questions

Before you enquire

Read access to the monitoring, logging and tracing tools in use, the telemetry and licence costs, a list of the services that matter most, and time with the people who run them and respond to incidents.

Yes, as one of the consumers of telemetry. We look at which network, platform and application signals reach your security operations centre, where the same data is collected twice for operations and security, and where it is missing for both. The detection rules themselves belong to the cyber work.

Only if the evidence says so. The findings set out what each tool covers, what it costs and where it overlaps another. Often the answer is to consolidate, to change what is collected and kept, or to fix instrumentation and ownership, and the existing tools stay.

The prioritised gaps feed the observability strategy: the target architecture, tooling decisions, service level objectives and a telemetry cost policy. You can take the findings forward yourselves, or ask us to set the strategy and then implement it. Scope and fee for each step are fixed at scoping.