Go

unomaly

Golang Ingestion Library for Unomaly's Ingest HTTP API

Logs are generated everywhere, ranging from the printer in the corner of your office to your new application architecture running docker containers on top of Kubernetes — Regardless, to analyze any of those logs, you need to send these logs over your network to Unomaly. Traditionally, shipping logs over the network involved using the syslog protocol. While syslog still is a great standard.

firehydrant

Developing a Go app with Docker Compose

Writing Go applications in an isolated environment with Docker comes with some great advantages. You get a clean GOPATH, the bare essentials for developing, and you can easily change which Go version you’re developing against. In this quick tutorial, we’re going to show you how to structure a Go application with Docker Compose as your development environment.

datadog

How to collect, standardize, and centralize Golang logs

Organizations that depend on distributed systems often write their applications in Go to take advantage of concurrency features like channels and goroutines (e.g., Heroku, Basecamp, Cockroach Labs, and Datadog). If you are responsible for building or supporting Go applications, a well-considered logging strategy can help you understand user behavior, localize errors, and monitor the performance of your applications.

thundra

Announcing OpenTracing Compatibility for Go Agent

Since its announcement by AWS Lambda, Golang has become a great alternative to the already existing runtimes. In addition to its rapid growth among the community, now Golang preserves this growth also in the serverless world. In the fight against the villain of the serverless applications, cold-starts; Golang seems to perform better than the other compiled languages available in AWS Lambda.

elastic

Inside the Elastic APM Go Agent

Earlier this year we introduced beta support in Elastic APM for Go application performance monitoring. In this blog post we’ll dive into some of the details of the agent. Some of what we’ll be covering is specific to the code branch for the upcoming "Generally Available" (GA) version of the agent, which uses a revised intake protocol and data model. You can read more about the new intake protocol here.