SRE

SRE

More
Agents will make your telemetry explode. You are not ready. – shipping bytes
Agents will make your telemetry explode. You are not ready. – shipping bytes
I have operated systems at scale long enough to know that the scariest failures are not the ones that blow up immediately. They are the ones that accumulate quietly, in the background, until the night you realize you cannot see what is happening anymore. Agents are going to do that to your observability stack. Vercel […]
#otel#ai/ml
·shippingbytes.com·
Agents will make your telemetry explode. You are not ready. – shipping bytes
Dotan Horovits #CNCFAmbassador (@horovits@fosstodon.org)
Dotan Horovits #CNCFAmbassador (@[email protected])

Attached: 1 image

W00t #OpenTelemetry voted for moving to a graduated project by the Cloud Native Computing Foundation (CNCF) 's Technical Oversight Committee! 🥳

I covered it on a recent episode of OpenObservability Talks 🎧 : https://horovits.medium.com/the-state-of-opentelemetry-insights-from-otel-unplugged-europe-e00f219f7460#1606

Great work to all involved @opentelemetry 👏

cncf #graduation #stabilization

#open_telemetry
·fosstodon.org·
Dotan Horovits #CNCFAmbassador (@[email protected])
BetaFold3/tfstate-audit: Terraform state history indexer for audits: local SQLite + search/diff across S3, GCS, Azure Blob, and HCP Terraform (with secret redaction).
BetaFold3/tfstate-audit: Terraform state history indexer for audits: local SQLite + search/diff across S3, GCS, Azure Blob, and HCP Terraform (with secret redaction).
Terraform state history indexer for audits: local SQLite + search/diff across S3, GCS, Azure Blob, and HCP Terraform (with secret redaction). - BetaFold3/tfstate-audit
#terraform#terraform_state_backend
·github.com·
BetaFold3/tfstate-audit: Terraform state history indexer for audits: local SQLite + search/diff across S3, GCS, Azure Blob, and HCP Terraform (with secret redaction).
Filippo Valsorda (@filippo@abyssdomain.expert)
Filippo Valsorda (@[email protected])
Dependabot security alerts have terrible signal-to-noise ratio, especially for Go vulnerabilities. That hurts security! Just turn it off and set up a pair of scheduled GitHub Actions, one running govulncheck, and the other running CI against the latest version of your dependencies. Less work, less risk, better results! https://words.filippo.io/dependabot/?source=Mastodon
#dependabot
·abyssdomain.expert·
Filippo Valsorda (@[email protected])
Michael Stapelberg 🐧🐹😺 (@zekjur@mas.to)
Michael Stapelberg 🐧🐹😺 (@[email protected])
Attached: 4 images PSA: Did you know that it’s **unsafe** to put code diffs into your commit messages? Like https://github.com/i3/i3/pull/6564 for example Such diffs will be applied by patch(1) (also git-am(1)) as part of the code change! This is how a sleep(1) made it into i3 4.25-2 in Debian unstable.
#github#git#gotcha
·mas.to·
Michael Stapelberg 🐧🐹😺 (@[email protected])
qdot (@qdot@buttplug.engineer)
qdot (@[email protected])
inspired by CLAUDE.md, I’ve started putting markdown files named after coworkers into work code repos so I can remind them to stop doing shit to the codebase that annoys me for some reason they’re all mad at me now, which means ill be adding commands to JEREMY.md for an attitude adjustment
#lol
·buttplug.engineer·
qdot (@[email protected])
JB63134/bash_ct: ct (Command Trace) is a Bash command resolution tracer that explains how Bash resolves a command and what the kernel ultimately executes. Exposes shadowing and overridden commands.
JB63134/bash_ct: ct (Command Trace) is a Bash command resolution tracer that explains how Bash resolves a command and what the kernel ultimately executes. Exposes shadowing and overridden commands.
ct (Command Trace) is a Bash command resolution tracer that explains how Bash resolves a command and what the kernel ultimately executes. Exposes shadowing and overridden commands. ...
#bash#tracing
·github.com·
JB63134/bash_ct: ct (Command Trace) is a Bash command resolution tracer that explains how Bash resolves a command and what the kernel ultimately executes. Exposes shadowing and overridden commands.
Release v0.7.0 · ruby/net-http
Release v0.7.0 · ruby/net-http
Breaking Changes Default Content-Type Removed The default behavior of automatically setting the Content-Type header to application/x-www-form-urlencoded for requests with a body (e.g., POST, PUT) w...
#ruby_gem#breaking_change
·github.com·
Release v0.7.0 · ruby/net-http
Contributing the Unroll Processor to the OpenTelemetry Collector Contrib
Contributing the Unroll Processor to the OpenTelemetry Collector Contrib
The idea for unrolling bundled logs inside the OpenTelemetry Collector didn’t start with a processor. By “unrolling,” I mean taking a single log record that contains multiple logical events—for instance, a JSON array with ten log entries—and expanding it into ten separate log records, one for each event. This lets you work with individual log entries rather than bundled payloads. When the Collector SIG first discussed the problem of how to handle logs that contain multiple logical events in a single body, like a JSON array, the initial instinct was to solve it with an OTTL (OpenTelemetry Transform Language) function inside the transform processor.
#otel_collector#logs
·opentelemetry.io·
Contributing the Unroll Processor to the OpenTelemetry Collector Contrib