Skip to content
Logmetry
What we solve
SIEM and log costClean data for AI agentsCoverage, audit and PIIVendor independenceSIEM migrationObservability modernizationAll problems we solve
Who it’s for
For the CISOFor the CIO and CTOFor the CFOFor Architects
Platforms
SplunkMicrosoft SentinelCrowdStrikeElasticDatadogDynatraceSplunk ObservabilitySolarWindsCriblOpenTelemetryA Data LakeCompare the options
The Blueprint
The whole methodPhase 01 · FoundationPhase 02 · AI triagePhase 03 · RemediationPhase 04 · FootprintEverything as codeAI native
JournalAbout
About LogmetryYour teamTrust and securityStep one and the proofWhere we fit
Book the review

Your team

Led by a Fortune 500 director of observability. Built as code you keep.

Zbigniew Gajuk has run every kind of monitoring and security platform for 26 years. Senior engineers build to his design.

Platforms he has run, a few of many

Network monitoring
HP OpenView, Nagios, SolarWinds
SIEM
Splunk, Microsoft Sentinel, CrowdStrike
APM and observability
Datadog, Dynatrace, Grafana
Pipelines and collection
Cribl, OpenTelemetry
Book the architecture reviewWho runs it after go-live ↓

01The founders

Who leads it, and who you call.

Together, the founders understand the most complex hybrid estates and telemetry at enterprise scale: Zbigniew the logs, telemetry and security on every vendor platform, Christopher the AI-native side and the custom builds. Delivered as code in your repository, or on the platforms you already run, as you choose.

Zbigniew Gajuk

Co-founder, chief observability and security architect

Experience

Understands every log source an enterprise runs: what each one means, what it is worth, and how to combine and enrich them. Director of observability and telemetry at a Fortune 500 healthcare and life-sciences organization, where he ran observability end to end and owned the business problems and the technical ones. He led the observability redesign and the Cribl implementation there, which changed how the organization controlled the value of its telemetry and where it lands, and began its control of what the pipeline ingests. 26 years running monitoring, observability and security across every generation of platform: network monitoring from HP OpenView and Nagios to SolarWinds, SIEMs from Splunk to Microsoft Sentinel and CrowdStrike, APMs from Datadog to Dynatrace and Grafana, and the pipelines in front of them, Cribl and OpenTelemetry.

In your project

Leads the engineers who build your pipeline. Designs it source by source, writes the reduction and enrichment rules, and proves every detection still fires before a source is cut over. Your named security contact from the first meeting to handover.

Zbigniew on LinkedIn →

Christopher Gajuk

Co-founder, director of operations, sales and go-to-market

Experience

AI agent and automation expert. Understands how AI agents reason step by step and what they need to read: the runbooks and skills they follow, the token cost of every field they are handed, the observability of the agents themselves, and the steps from triage to remediation. Has set up and migrated SIEMs in an enterprise estate, hands-on with Splunk, CrowdStrike, Datadog and Dynatrace and the data pipelines in front of them, and decides with Zbigniew what to enrich and what to drop, so the data an agent reads is worth reading. Understands custom, in-house builds as well as vendor platforms, everything as code with CI/CD on AWS and Azure.

In your project

Your point of contact and escalation point from the first call to handover. Leads operations, sales and go-to-market, and helps Zbigniew lead the team, while Zbigniew, as the architect, leads the engineers who build it.

Christopher on LinkedIn →

The lead architects who scope your engagement lead it to handover, and are named in the contract as key personnel. Senior engineers do the build, under the founders, following their design and instructions. The founders understand every change they make, and review it.

02The engineers

Senior engineers who build to one design.

Our lead consultants and architects lead and oversee every engagement. Senior engineers in telemetry engineering, pipeline design and agentic AI, who worked in Fortune 500 and enterprise environments, build under their direction. The founders choose who works on your engagement, review every change, and answer for it.

  • Telemetry engineering

    On your engagement

    Gets every source in and keeps it whole: the collection agents and forwarders, the parsing and field normalization, and the tests that prove each detection still fires on the reshaped data before a source is cut over.

  • Pipeline design

    On your engagement

    Builds the routes, the reduction and enrichment rules, and the full raw copy into your own account, all as code in your repository, with the tests and the deploy your team runs after handover.

  • Agentic AI

    On your engagement

    Later, and only when you choose AI triage: the read-only agent on the lake copy, the model you approve running in your own account, and the review step where a person on your team signs off every exception. Step one puts none of your data into any AI model.

03Yours to keep

Everything as code. Your IP from day one.

That is our philosophy. You keep us because the work is good, never because you cannot leave. Everything we build lives in your repository from the first commit, so your team or any partner you choose can take it over whenever you want.

  • Your repositoryEvery pipeline, route and rule, as code, each change reviewed in a pull request.
  • Your testsThe checks that prove each detection still fires, run in your pipeline, not ours.
  • Your runbooksThe tasks your team will do, and a written record of every design decision and the reason for it.
  • Your peopleYour engineers work beside ours during the build, so the handover is a date, not a project.

04Day two

Your team runs it, or we do, by agreement.

Logmetry designs and builds it: our lead architects lead every engagement, and senior engineers build under their direction. Day two is run by your own team, or by Logmetry if you want that. After-hours cover comes with every engagement, from your systems integrator or Logmetry, with the response window in the statement of work.

Who responds at 1 a.m.

  1. 1The design keeps data movingPipeline workers run as a group behind a load balancer, so one failed worker does not stop the flow. If your SIEM slows or goes offline, the pipeline holds the data in a queue on disk and delivers it when the SIEM recovers, instead of dropping it.
  2. 2The platform vendor’s supportTakes defects in its own software, on the hours of your subscription plan.
  3. 3After-hours coverComes with every engagement, from your systems integrator or from us, with the response window written into the statement of work. The written window is our commitment, and we promise nothing beyond it.

The escalation path

  1. 1The engineer on your ticket.
  2. 2The founder leading your engagement, the same business day.
  3. 3The pipeline vendor’s support, for a defect in its software, opened with you under your subscription.
  4. 4Christopher, as our executive sponsor, for anything commercial or unresolved.

The pipeline vendor supports its own software, under your own subscription. Your systems integrator holds the relationship and, if you prefer, the contract. It does not run the pipeline.

How the design removes the dependency on us →

See your architecture drawn, with the costs, before you spend anything.

Our lead architects draw your SIEM feed from your diagrams: where the cost sits, what step one would change, and where it would not pay. If it pays, the next step is a two-week proof on your noisiest source.

Book the architecture reviewOr take the Blueprint as a PDF →

Free. No system access. No obligation. You keep the drawing.

What you get

  • Your architecture today, drawn
  • The waste map
  • Costs before and after, with estimates
  • Your target architecture
  • Options for your business problem

What it costsNothing