Skip to content

BuildNot yet confirmed elsewhere1 publisher3 min readPublished Updated

OllyGarden's $4 million bet moves telemetry fixes into the pull request

OllyGarden raised $4 million as its Rose agent moves upstream to propose baseline instrumentation in code. Founder Juraci Paixao Kroehling says AI-written code is pushing telemetry volume up, so the fix belongs in code before teams pay to store it.

The Engineer · Build desk

How we use AISend a correction

Photograph accompanying OllyGarden's $4 million bet moves telemetry fixes into the pull request
Photo: tech.eu
Rose's fixes reach code reviewers before storage bills Who OllyGarden's Rose agent reaches, and how, as it moves telemetry fixes into source code and pull requests.

Review teams must review and merge each Rose pull request. Engineers and coding agents get a shared baseline. Repos without instrumentation can get a guided baseline. Teams paying for storage face less excess data. Strategic investors: Datadog, Grafana Labs and Dash0.

Rose's fixes reach code reviewers before storage bills
WhoHowKindClaim
Human review teamsRose delivers source-code fixes as pull requests, leaving a human team to review and merge each change.cost11
Engineers and coding agentsA deliberate baseline means each new service does not add data without a shared standard.constraint13
Uninstrumented repositoriesWhere instrumentation is missing, Rose can guide a baseline instead of only flagging problems.capability10
Teams paying to store dataAims to cut excess data before the observability backend, so teams sort through or pay to store less.exposure14
Datadog, Grafana Labs, Dash0Made strategic investments in OllyGarden.decision7

What happened

  • Rose works on source code and delivers its fixes as pull requests, leaving a human team to review and merge each change.
  • Kroehling's 2021 OpenTelemetry Governance Committee profile says he maintained Jaeger from 2018, created the OpenTelemetry Operator in 2019 and approved Collector changes from 2020.
  • Datadog, Grafana Labs and Dash0 joined the round as strategic investors, Tech.eu reported.

Why it matters

  • cost Any cut in storage spend is paid for first in reviewer time, because each baseline or fix is a pull request someone has to read and merge.
  • constraint A shared baseline limits how much telemetry each new AI-written service can add before anyone has agreed on a standard for it.
  • decision Telemetry quality becomes a development-team responsibility as well as an observability one, so engineering leads have to decide where the standard lives and who approves changes to it.

Rose, OllyGarden's AI OpenTelemetry Engineer, works on source code and ships its changes as pull requests for a human to merge [8][11]. Before this release, Rose analyzed existing instrumentation and suggested improvements [9]. Minimum Viable Instrumentation covers the repository with nothing to analyze. When instrumentation is missing, Rose can now guide a baseline instead of only flagging problems in what exists [10]. OllyGarden says the goal is consistent practice across teams, repositories and pull requests without producing unnecessary data [12].

The case for moving upstream is volume. According to the runtimewire report, AI coding tools can increase the amount of telemetry, while missing or noisy signals still leave engineers without useful context [16]. Kroehling told Tech.eu that growing use of AI-generated code has contributed to rising telemetry volumes and made critical information harder to find [15]. MVI is meant to give coding agents and engineers a deliberate baseline, so each new service does not add data without a shared standard [13]. I think the pull request is the right delivery format for that. A baseline written by an agent goes through the same human review as the code beside it [11], so a team can reject one that drops a signal it relies on.

The argument predates the AI-code pitch. The founders' 2025 launch post said automated instrumentation can gather much more data than teams actually need, driving up costs and burying the signals that are useful [18]. Kroehling told Tech.eu, "More instrumentation is not better instrumentation. It's about surfacing only the information and data that's useful and actionable: no more, no less." [17]

The 85% claim needs a careful read [19]. Identified is the verb to read twice. It describes findings in those codebases over the past year. The figure is a company-reported maximum, and the report does not include a sample size or a methodology [20]. At that ceiling a team would keep 15% of its log volume [23]. For the number to transfer, another team's logs would need the same share of excess as OllyGarden's best case, and its reviewers would need to merge the changes. The company says it works with businesses in retail, financial services and enterprise software [21].

Kroehling's OpenTelemetry history comes from his own 2021 governance committee candidate profile, and those details are self-reported [3]. The same profile says he worked at Red Hat before joining Grafana Labs to help build an OpenTelemetry-focused team [4]. He co-founded OllyGarden with Yuri Oliveira Sa, an SRE and OpenTelemetry specialist [5].

Next Frontier Capital, Grand Ventures and ACTAI Ventures backed the $4 million round, and existing investor DIG Ventures participated, Tech.eu reported [1][6]. The three strategic investors back a product whose stated aim is less excess data for teams to sort through or pay to store [7][14].

What to watch

  • OllyGarden publishing the sample size and methodology behind the 85% figure, or a named customer reporting reductions after merging Rose's changes.
  • A public description of what an MVI baseline contains for a given service, and whether coding agents consume it before they write code.
  • Whether strategic investors Datadog, Grafana Labs and Dash0 ship any integration with Rose.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence35
Adoption12
Hype gap+25
Incentives60
Confidence40
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    OllyGarden raised $4 million in venture funding, Tech.eu reported on October 9.

    ReportedSupportedSource: Tech.eu, via runtimewire2 sources— create a free account to open themView cited source
  2. [2]

    In his 2021 OpenTelemetry Governance Committee candidate profile, Kroehling said he had maintained Jaeger since 2018, contributed to OpenTelemetry since 2019, created and maintained the OpenTelemetry Operator since 2019 and Collector Builder since 2021, and served as an approver for Collector Contrib and Collector core since 2020.

    ReportedSupportedSource: Kroehling's 2021 candidate profile, via runtimewire2 sources— create a free account to open themView cited source
  3. [3]

    The profile details come from Kroehling's own submission and are not independently documented.

Sources

1 independent publisher whose own reporting we read for this story.

  1. runtimewire.com

    1 article · October 8, 2026

    OllyGarden raises $4M to fix telemetry before it reaches monitoring systems

Share your take

Let Clarity write the post for you.

Signed-in readers get a short post drafted on this story in the register they choose — narrative, analytical, or a direct position — editable to the last word before it goes anywhere. The share buttons at the top of this story work without an account.

Topics and entities

Follow any of these and your For You feed starts watching them — no settings page required.

Entities

Loading related stories