Found 279 bookmarks
Newest
Metric cardinality limits in OpenTelemetry: a practical guide
Metric cardinality limits in OpenTelemetry: a practical guide
OpenTelemetry metrics are designed to be safe to use in production. One part of that safety is the cardinality limit in the metrics SDK. The limit protects your process from unbounded memory growth when a metric receives too many unique attribute combinations. That protection is useful, but it has a consequence many users do not expect: when a metric stream overflows, the total value remains correct, while queries that filter or group by attributes can undercount. This can affect dashboards, service-level objectives (SLOs), and alerts that looked correct before overflow started.
·opentelemetry.io·
Metric cardinality limits in OpenTelemetry: a practical guide
Dotan Horovits (@horovits@fosstodon.org)
Dotan Horovits (@[email protected])
What if #OpenSearch could natively ingest #OpenTelemetry data without a collector/agent? I'm really happy to see this PoC by #SAP for 𝚘𝚙𝚎𝚗𝚜𝚎𝚊𝚛𝚌𝚑-𝚘𝚝𝚕𝚙-𝚛𝚎𝚌𝚎𝚒𝚟𝚎𝚛 plugin for a native OTLP endpoint to ingest into OpenSearch cluster https://github.com/SAP/opensearch-otlp-receiver @OpenSearchProject @opentelemetry #OpenSearchAmbassador #observability #devops #ingestion #otlp #otel
·fosstodon.org·
Dotan Horovits (@[email protected])
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 […]
·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

·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
·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
·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.
·mas.to·
Michael Stapelberg 🐧🐹😺 (@[email protected])
qdot (@qdot@buttplug.engineer)
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
·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. ...
·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.