Introduction to Go Custom Metrics with Logz.io RemoteWrite SDK from Logz.io

We recently announced the release of our RemoteWrite SDK to support custom metrics from applications using several different languages – The first SDKs allow shipping of metrics from Golang (Go), Python, Java, Node.js, and.NET. This tutorial will cover the Golang SDK. The SDKs cover not just Logz.io, but can be used by any platform that supports the Prometheus remote write endpoint.


Get fine-grained access control of your server with AblyD

It’s fairly common to want to have a server running a process, be it a website, a calculation, or anything else you can imagine. Often outside of the device’s core functionality though, there are many other things you may be interested in. Information on if the process is still running, what server(s) are running, what errors are occurring in the process, and general information being available externally are common examples of this.


Packet Capture Without "tcpdump" for Go Apps in Kubernetes

Every developer knows there are some utilities that are completely indispensable from their workflows. The programmer’s toolbelt, if you will. These toolbelts are usually different from person to person, but if there is one tool that everyone should use or at least know how to use, it is tcpdump. If you are unfamiliar, tcpdump is a tool that allows you to dump and inspect live network traffic being observed on a network interface.


Scalable event streaming with Redis and Golang

A common problem that our customers have is event streaming spikey traffic to their clients. For example, imagine a server which needs to stream details on cryptocurrency trades. The quantity of trades happening each second is likely to fluctuate, sometimes nothing could happen, other times perhaps thousands. In order to ensure reliable communication, it’s important that rate limits are in place on how many messages are to be sent to subscribed clients.


Real-time distributed tracing for Go and Java Lambda Functions

Serverless applications streamline development by allowing you to focus on writing and deploying code rather than managing and provisioning infrastructure. To help you monitor the performance of your serverless applications, last year we released distributed tracing for AWS Lambda to provide comprehensive visibility across your serverless applications.

The painful simplicity of context propagation in Go

Context propagation is fundamental distributed tracing and modern observability. We're going to deep dive into how Context management works in OpenTelemetry, using Go as an example. I love programing in Go, and I appreciate the dedication to simplicity and readability. But sometimes "we fear magic" can drift into "we fear cameras will steal our souls." Is the explicit way that Go handles context propagation actually *too* simple?