Modern Go services generate telemetry – metrics, logs, traces – using instrumentation embedded directly in code. Typically, this is a code-first approach, where developers call APIs (counters, loggers, tracers) and attach key-value attributes on the fly. This works, but at scale it can lead to fragmented data and missing context. Schema-first telemetry flips this paradigm: you define upfront a schema (like an IDL file) for your telemetry data, including its semantic metadata, and use generated code to emit telemetry.

Using Go for make nice terminal UI with Bubble Tea

Terramate seeks to complement Terraform by providing additional structure and tools for managing multiple Terraform stacks, environments, and configurations more effectively. It is engineered to ease the pain points associated with large-scale Terraform deployments, including dependency management, stack management, and environment differentiation

How make W3Context work for your application in Go Gin Framework

Most programming languages don’t have basic settings for HTTP made to run in production.

Bubble Tea - how to make better terminal UI

OpenTelemetry as best way how to instrument your CICD pipeline. Talk cover observability CICD tools and show demo how instrument Github Action using Honeycomb buildevents and manual instrumentation in project using Dagger.io for pipelines.

Disclaimer: I work for Pure Storage, which provides and sells flash storage for enterprise customers. We have a PDS (Portworx Data Services) service that offers stateful services (PostgreSQL, Kafka, Cassandra, MongoDB, Consul, Mysql, Redis, Elasticsearch, Couchbase, RabbitMQ, ZooKeeper) with a single operator for the deployment of all these services. We have a few other operators for backup and operations. All are based on the Portworx Kubernetes storage solution, and PDS will work in a cloud or on-premise Kubernetes cluster.

Talk is about new Dagger Go SDK

Talk is about new Fuzzing function in Go 1.18