OpenTelemetry (OTel in short) is an open-source observability framework that provides a standard set of vendor-agonistic SDKs, APIs, and tools to connect with observability backends. It supports all major programming languages, including Java, Python, Node.js, and Go. However, Golang tracing by integrating OTel with Golang is particularly challenging due to several reasons.
gRPC (Google Remote Procedure Call) is a high-performance, open-source universal RPC framework that Google developed to achieve high-speed communication between microservices. gRPC has Protobuf (protocol buffers) by default which would format or serialize the messages to a specific format that will be highly packed, highly efficient data. By its virtue of being a lightweight RPC, gRPC is suited for many use-cases. gRPC can be considered a successor to RPC, which is light in weight.
OpenTelemetry can be used to trace Gin applications for performance issues and bugs. OpenTelemetry is an open-source project under the Cloud Native Computing Foundation (CNCF) that aims to standardize the generation and collection of telemetry data like logs, metrics, and traces. Gin is an HTTP web framework written in Go (Golang). It features a Martini-like API with much better performance -- up to 40 times faster. If you need smashing performance, get yourself some Gin!
In this article, learn how to setup application monitoring for Golang apps using an open-source solution, SigNoz. If you want to check our Github repo before diving in 👇 Scalability, Reliability, Maintainability... The list goes on for the benefits of microservices architecture in today's world. But along with these benefits also comes the challenges of complexity.
OpenTelemetry (OTel), the emerging industry standard for application observability and distributed tracing across cloud-native and distributed architectures, is becoming an essential tool for Go developers. However, implementing OTel with Go to send data to observability platforms is hardly a straightforward process. At Helios, we’re on a mission to help as many teams as possible adopt distributed tracing.
The developer experience just got so much better with the latest Platform.sh CLI release. Designed and engineered to help developers manage their daily work environments more efficiently, this incredible tool is ready to Go for our entire developer community, becoming language independent with no need to install PHP, and embracing the distribution standards. With the Platform.sh CLI, developers can easily use and manage their projects directly from their terminal.
We’ve got a lot of OpenTelemetry-flavored honey to send your way, ranging from OpenTelemetry SDK distribution updates to protocol support. We now support OpenTelemetry logs, released a new SDK distribution for OpenTelemetry Go, and have some updates around OpenTelemetry + Honeycomb to share. Let’s see what all the buzz is about this time! 🐝🐝
In the last couple of weeks, I spent a ton of time looking at different ways to send OpenTelemetry (OTel) data to Lightstep. In case the super-obvious title didn’t tip you off already, there are three different ways to do so: In this post, I will dig into each of these three approaches in detail, with code snippets which explain how to get data into Lightstep Observability. Let’s do this!
BindPlane OP is written in Go. It is a single http webserver, serving REST, Websocket, and Graphql clients. It includes embedded react applications for serving the user interface. Go provides us with the ability to produce a single binary program that has no external dependencies. The binary is not dynamically linked to external libraries, meaning it is easy to build, deploy, and run on any platform supported by the Go compiler. BindPlane OP officially supports Linux, Windows, and macOS.
