20 | GSoC 2026 @ MetaCall | i do stuff that makes no sense | you can hire me
Joined November 2024
- Tweets307
- Following55
- Followers93
- Likes3.2K
Pinned Tweet
Your OpenTelemetry Collector config is untested code.
One wrong processor and passwords leak into your observability backend. Nobody notices until prod.
So I built Tracelet: unit tests for Collector configs, written in Rust.
How do you test yours today?
I kept missing hackathon deadlines because the page changed and I never noticed.
So I built Linkwatch: paste an opportunity link, it finds the dates, you confirm and it reminds you before they close. If a deadline moves, it tells you.
What's the last deadline you missed?
Free beta, try it with a real link: linkwatch.tracelet.xyz
Tell me if it gets the dates wrong
got rejected from my first inbound internship opportunity.
couldn’t explain parts of my own resume when it mattered. lesson:
if you can’t explain it, it’s not really yours yet.
back to building things by hand. fundamentals first.
nice question btw so its like otelbin checks your config is valid and shows the pipeline and tracelet checks it does what you meant like it runs the real collector, sends test telemetry through and asserts on what comes out. like a config can be valid and still leak a password.
Docs, demo and install: tracelet.xyz
Source: github.com/SATVIKsynopsis/Tr…
Feedback welcome, especially configs it can't handle yet.
what i did in october:
1. contributed to zed and got a PR merged.
2. contributed to FFmpeg a got a PR merged.
3. made fp (a video compression tool on top of FFmpeg) and got 50+ downloads and 16 stars on github.
4. made nvidia ptaxs for emmy hackathon.
