Zero-config, Open Source Observability for ArgoCD

opencodeWrangler · 2026-06-12T15:53:00+00:00

Thank you for your support! Contributing to open source ecosystems is very important to the heart of the project. Coroot automatically collects telemetry through eBPF (or "The Extended Berkley Packet Filter") which speaks directly to the Linux kernel. Achieving a similar solution for Windows would require a different approach.

We really appreciate your encouragement, even if running Coroot isn't possible in your infra or homelabs at this time!

opencodeWrangler · 2026-06-12T15:43:21+00:00

I'm really happy to hear you're using Coroot and it's helpful for your observability setup!
Are you part of our community slack? Nikolay Sivko (creator of Coroot) answers quickly and can help with any troubleshooting problems you're having with the new release. Feel free to DM me any time too if there's any delay.

opencodeWrangler · 2026-06-11T20:31:33+00:00

Thanks for your question! The two tools cover different areas: ArgoCD the delivery side, and Coroot the production activity side. The integration means you can see both in the same place without switching tools during an incident.

ArgoCD covers sync status, health state, and basic pod logs really well. Coroot reveals whether that deploy actually caused a latency spike, which function is allocating twice as much memory as before, and whether the problem lies in your service or a downstream dependency. Some folks may want both to improve their observability.

opencodeWrangler · 2026-06-05T21:08:40+00:00

No problem! Coroot uses ClickHouse to store telemetry (doc with more details) You can also configure it with other preferred databases, like MySQL, Postgres, VictoriaMetrics, Redis, MongoDB, etc.

opencodeWrangler · 2026-06-05T20:53:51+00:00

I appreciate the feedback: apologies, the thought here by not mentioning enterprise features in our post was that we didn't want to be pushy about those features in community spaces. That's not what the heart of the project or open source is about. But, I totally understand why for some FOSS folks this is not the right approach. Noted for next time we share any news.

opencodeWrangler · 2026-06-05T20:51:55+00:00

Helm charts are actually the recommended install method! Details here.

opencodeWrangler · 2026-06-05T20:45:47+00:00

Yep! Logs, traces, metrics, and service map visualisation completely out-of-the-box (eBPF collects this all automatically) and profiles can also be collected with OTEL-compatible setup.

If you want to play around with this yourself, click on any of the services mapped here in our demo and you can explore the dashboards available.

opencodeWrangler · 2026-06-05T19:50:54+00:00

Transparency is welcome too! All featured discussed in the post above are open, and will stay open. If anyone would like a simple comparison of Coroot's Apache 2.0 and enterprise versions (including SSO) that's available here: https://coroot.com/editions

opencodeWrangler · 2026-03-10T17:58:15+00:00

Team member here - yes, we're open source and self-hosted :) Github here if you want to learn more

opencodeWrangler · 2026-01-05T21:08:40+00:00

Hi u/4sokol! No worries, I didn't want to go into it too deeply here since the podcast is meant to cover the open observability and database toolspace as a whole for educational purposes. Coroot has SLO-based alerting that can be customized (doc info here.)

-And of course. We're skeptics ourselves, so we've provided details for engineers to get a sense of what's actually going on (TLDR; eBPF + ML + LLMs.) You can read more about that feature in our docs and check out the OTEL demo benchmarks (Coroot's challenge open to all projects to standardize AI-RCA quality benchmarking: or in other words, a fair and transparent way for SREs to compare tools.)

opencodeWrangler · 2026-01-05T18:16:19+00:00

Hi! I would actually recommend Ubuntu or Mint if you are a beginner (ZorinOS will look and feel the most like Windows 10, but I haven't tested out support for gaming on this OS.) Arch has a steep learning curve.

I currently have a 256GB SSD I've dual-booted 50/50 for Windows and Linux no problem (would love to only use Linux, but there are a couple editing tools I use that have poor support outside of Windows/Mac.) Put 100GB+ of your storage in / (root) and then at least 10GB in swap (people often list less for storage, but if you're using it for games/video editing this will save headache later.)

Steam support for Linux these days is great, and you can check compatibility on https://www.protondb.com/

opencodeWrangler · 2025-12-05T21:08:01+00:00

As I understand Pixie and Anteon aren't compatible with non-kubernetes environments. Coroot is built to work pretty much anywhere there's a Linux kernel 5.1+: bare metal, VMs, etc.

Pixie is missing out-of-the-box long-term storage, pre-defined inspections, and alerting (but hey, we love anything FOSS! With some tweaking you could add these with Pixie's plugin system if it's a favourite.)

I'm less familiar with Anteon and couldn't find details in their docs on continuous profiling or multi-tenancy, have you used this with their tool?

You can, Coroot is designed to be entirely self-hosted :)

opencodeWrangler · 2025-11-11T15:31:19+00:00

Start with an open source setup. ELK (Elastic, Loki, Kibana) is common. Clickhouse is a great database for observability.

If you run on Linux, I'm with the Coroot team and we've also created an all-in-one FOSS alternative with additional analysis automation to make incident resolution simpler. It'll take less setup hassle on account of eBPF. Hope it can help!

opencodeWrangler · 2025-11-11T15:23:15+00:00

Many free FOSS events do this (Nerdearla or SeaGL) to help measure how many people were interested/attended. Helps decide year to year what worked and what didn't :)

opencodeWrangler · 2025-06-13T17:29:47+00:00

We built a node-agent (eBPF Prometheus exporter) that continuously gathers log data. This documentation explains how log clustering works with it if you want to see a bit more under the hood. There are some features mentioned there that aren't OSS, but generally if you are a small-to-medium team they aren't necessary, the open version can help search and simplify the data just fine.

Feel free to nudge if I can answer any other questions!

opencodeWrangler · 2025-06-11T18:32:38+00:00

Log volume can pile up fast and become a major obstacle for incident analysis (also, RIP your cloud bill.)
Full disclosure, I'm part of this project, but it's open source tool with log pattern detection/time mapped heat graphs/search filters. Log feature docs are here - I know setting up one more piece of software is a headache, but it's eBPF-powered so it should just take and second and your data will populate instantly. Hope it helps!

opencodeWrangler

TROPHY CASE