Ever wonder what a trace from a GitHub action looks like?
Well, as of this weeks release of v0.122.0 of the OpenTelemetry Collector, you can find out! The…
With more and more people adopting OpenTelemetry and specifically using the tracing signal, I’ve seen an uptick in people wanting to add the entire request and response body as an attribute. This isn’t ideal, as it wasn’t when people were logging the body as text logs. In this blog post, I’ll explain why this is a bad idea, what are the pitfalls, and more importantly, what you should do instead.
Attached: 2 images
Last week, I learned about default gems in Ruby with asdf. These are gems that you want to install whenever you install a new #ruby version. It turns out that default packages work with languages other than Ruby, too!
Here's how to do it in #golang and #python.
Good evening, folks. TIL that Go 1.24.0 has updated its runtime/debug package to automatically stamp apps with a version or pseudo-version at build time based on VCS information.
No need for complex build pipeline steps to inject version constants anymore. Just tag a release appropriately in Git and use 𝚍𝚎𝚋𝚞𝚐.𝙱𝚞𝚒𝚕𝚍𝙸𝚗𝚏𝚘.𝙼𝚊𝚒𝚗.𝚅𝚎𝚛𝚜𝚒𝚘𝚗 in your code.
https://github.com/golang/go/issues/50603#issuecomment-2181188811
This is a great feature that many people may have missed in the release notes:
https://tip.golang.org/doc/go1.24#:~:text=information.-,The,changes.
#go #golang
Alibaba, Datadog, and Quesma Join Forces on Go Compile-Time Instrumentation
Standards are only useful if they’re widely adopted, and adoption is only effective if the available tooling facilitates it. I imagine SI units would not have been too popular when they were introduced if you had to build your own scales to weigh things in Kilograms!
If you use OpenTelemetry in Go, you’ll be familiar with the challenges of configuring instrumentation libraries to automatically generate telemetry from well-known open source components. Due to the compiled nature of the language, you currently have two options1:
Observability: the present and future, with Charity Majors
In today's episode of The Pragmatic Engineer, I'm joined by Charity Majors, a well-known observability expert – as well as someone with strong and grounded opinions.
Overhauling PagerDuty’s data model: a better way to route alerts | Blog
PagerDuty has long been the go-to solution for reliable on-call management, but its aging data model and lack of innovation have become a challenge. In this post we explore how incident.io On-call offers a better, more flexible approach to alert routing and provide practical advice on how to migrate smoothly from PagerDuty.
Joe Stech on LinkedIn: I was chatting with some AWS cost optimization experts a couple weeks ago… | 17 comments
I was chatting with some AWS cost optimization experts a couple weeks ago at re:Invent, and they agreed that one of the things that makes them mildly gleeful… | 17 comments on LinkedIn
If you rely on Docker images (as in `docker.io/library/docker`) in CI or elsewhere: it looks like the images pushed yesterday on https://lnkd.in/gfgY3wQJ have…
Improve visibility into Amazon Bedrock usage and performance with Amazon CloudWatch | Amazon Web Services
In this blog post, we will share some of capabilities to help you get quick and easy visibility into Amazon Bedrock workloads in context of your broader application. We will use the contextual conversational assistant example in the Amazon Bedrock GitHub repository to provide examples of how you can customize these views to further enhance visibility, tailored to your use case. Specifically, we will describe how you can use the new automatic dashboard in Amazon CloudWatch to get a single pane of glass visibility into the usage and performance of Amazon Bedrock models and gain end-to-end visibility by customizing dashboards with widgets that provide visibility and insights into components and operations such as Retrieval Augmented Generation in your application.
Liz Fong-Jones on LinkedIn: This is why I strongly discourage people from writing data into CloudWatch…
This is why I strongly discourage people from writing data into CloudWatch and then reading it into Honeycomb; it is far far far better to directly send the…
Attached: 1 image Just discovered https://httpstat.us which returns a HTTP response you request. You can request by number, like: httpstat.us/404 Randomly from a range and/or list: httpstat.us/random/400-410,202,200 And you can set a timeout in ms: httpstat.us/200?sleep=3000