# Collector

Published articles for Collector.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## OpenTelemetry everywhere: Migrating a metrics platform at scale

DevFeed: [OpenTelemetry everywhere: Migrating a metrics platform at scale](<https://devfeed.tech/articles/opentelemetry-everywhere-migrating-a-metrics-platform-at-scale-41279.md>)

Original publisher: [Read original article](<https://www.cncf.io/blog/2026/09/17/opentelemetry-everywhere-migrating-a-metrics-platform-at-scale/>)

Author: Iris Grace Endozo, Farzad Vazirnia and Albert Kerr, Atlassian

Published: 2026-09-17T11:00:00Z

Content type: article

Language: en

Sources: [Cloud Native Computing Foundation](<https://devfeed.tech/sources/cloud-native-computing-foundation.md>)

Topics: [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [migration](<https://devfeed.tech/topics/migration.md>), [observability](<https://devfeed.tech/topics/observability.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [atlassian](<https://devfeed.tech/topics/atlassian.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [atlassian](<https://devfeed.tech/tags/atlassian.md>), [blog](<https://devfeed.tech/tags/blog.md>), [collector](<https://devfeed.tech/tags/collector.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [migration](<https://devfeed.tech/tags/migration.md>), [observability](<https://devfeed.tech/tags/observability.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [scale](<https://devfeed.tech/tags/scale.md>), [sidecar](<https://devfeed.tech/tags/sidecar.md>)

### AI overview

Atlassian describes replacing a large-scale gostatsd metrics pipeline with OpenTelemetry while preserving the existing StatsD interface for service teams. The migration uses purpose-built OpenTelemetry Collector distributions across collection, ingest, aggregation, and forwarding stages, with support for both StatsD and OTLP during the transition.

### Source excerpt

Why we did this at all For most of the last decade our metrics pipeline ran on gostatsd, the open-source StatsD implementation we maintain. It primarily did two jobs: as sidecar on every host and the...

## Size-Specialized Memory Allocation

DevFeed: [Size-Specialized Memory Allocation](<https://devfeed.tech/articles/size-specialized-memory-allocation-31550.md>)

Original publisher: [Read original article](<https://go.dev/blog/size-specialized-allocations>)

Author: Michael Matloob

Published: 2026-09-16T00:00:00Z

Content type: article

Language: en

Sources: [The Go Blog](<https://devfeed.tech/sources/the-go-blog.md>)

Topics: [Go](<https://devfeed.tech/topics/go.md>), [optimize](<https://devfeed.tech/topics/optimize.md>)

Tags: [collector](<https://devfeed.tech/tags/collector.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [go](<https://devfeed.tech/tags/go.md>), [performance](<https://devfeed.tech/tags/performance.md>), [spans](<https://devfeed.tech/tags/spans.md>)

### AI overview

Go 1.27 introduces size-specialized allocation functions for allocations smaller than 80 bytes. The change makes those allocations up to 20-30% faster and can improve allocation-heavy programs by up to 1%.

### Source excerpt

Go 1.27 improves performance of small allocations using size-specialized allocation functions.

## nixos-telemetry: A NixOS flake for opt-in observability pipelines

DevFeed: [nixos-telemetry: A NixOS flake for opt-in observability pipelines](<https://devfeed.tech/articles/nixos-telemetry-flake-31359.md>)

Original publisher: [Read original article](<https://discourse.nixos.org/t/nixos-telemetry-flake/79704>)

Author: palo

Published: 2026-08-23T08:27:36Z

Content type: article

Language: en

Sources: [Announcements - NixOS Discourse](<https://devfeed.tech/sources/announcements-nixos-discourse.md>)

Topics: [telemetry](<https://devfeed.tech/topics/telemetry.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [Tooling](<https://devfeed.tech/topics/tooling.md>), [log management](<https://devfeed.tech/topics/log-management.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>), [Grafana Alloy](<https://devfeed.tech/topics/grafana-alloy.md>)

Tags: [announcements](<https://devfeed.tech/tags/announcements.md>), [collector](<https://devfeed.tech/tags/collector.md>), [config](<https://devfeed.tech/tags/config.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-alloy](<https://devfeed.tech/tags/grafana-alloy.md>), [loki](<https://devfeed.tech/tags/loki.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [prometheus](<https://devfeed.tech/tags/prometheus.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>)

### AI overview

A discussion introduces nixos-telemetry, a NixOS flake that uses an OpenTelemetry collector to connect opt-in scrapers, storage, and visualization components. It supports local stacks, remote forwarding, and fan-out to multiple sinks through a unified option tree.

### Source excerpt

Hi everyone, I'd like to share nixos-telemetry, a NixOS flake that makes setting up observability in your infrastructure easy. An OpenTelemetry collector sits at the center of each machine. Scrapers, storage, and visualization are all opt-in. You enable what you need; the collector wires the pipeline together automatically. Why? Wiring up telemetry in NixOS today means gluing together Telegraf, Prometheus, Loki, Grafana, Alloy, each with its own config format, ports, and inter-service dependencies. nixos-telemetry puts all of that behind a single telemetry.* option tree: Turn on the system with telemetry.enable = true. Every app is opt-in. Nothing starts that you didn't ask for. The collector starts automatically once a complete pipeline exists, a matching source and sink for the same signal type. No sink? It waits. Forward to a remote collector, run a full local stack, or both. Fan-out to multiple sinks is supported. What it looks like Full local stack on one machine: { telemetry.enable = true; telemetry.telegraf.enable = true; # host metrics telemetry.alloy.enable = true; # journald logs telemetry.prometheus.enable = true; # metrics storage telemetry.loki.enable = true; # logs storage telemetry.grafana.enable = true; # visualization (datasources auto-provisioned) } Forward to a remote collector: # machine 1 { telemetry.enable = true; telemetry.telegraf.enable = true; telemetry.opentelemetry.exporter.endpoints.remote = "100.64.0.1:4317"; } # machine 2 { telemetry.enable = true; telemetry.opentelemetry.receiver.endpoint = "0.0.0.0:4317"; } Full option reference: OPTIONS.md Thanks! Regarding Discourse LLM Policy : I must disclose that substantial parts of this project are llm generated. And because I coppied parts of the README in this post, substantial parts of this announcmement too. 27 posts - 7 participants Read full topic

## How to Turn a List of Flat Elements into a Hierarchy in Java, SQL, or jOOQ

DevFeed: [How to Turn a List of Flat Elements into a Hierarchy in Java, SQL, or jOOQ](<https://devfeed.tech/articles/how-to-turn-a-list-of-flat-elements-into-a-hierarchy-in-java-sql-or-jooq-28945.md>)

Original publisher: [Read original article](<https://blog.jooq.org/how-to-turn-a-list-of-flat-elements-into-a-hierarchy-in-java-sql-or-jooq/>)

Author: lukaseder

Published: 2023-03-24T15:45:28Z

Content type: tutorial

Language: en

Sources: [jOOQ](<https://devfeed.tech/sources/jooq.md>)

Topics: [Java](<https://devfeed.tech/topics/java.md>), [SQL](<https://devfeed.tech/topics/sql.md>), [Jackson](<https://devfeed.tech/topics/jackson.md>), [JSON](<https://devfeed.tech/topics/json.md>), [Library](<https://devfeed.tech/topics/library.md>)

Tags: [code](<https://devfeed.tech/tags/code.md>), [collections](<https://devfeed.tech/tags/collections.md>), [collector](<https://devfeed.tech/tags/collector.md>), [collectors](<https://devfeed.tech/tags/collectors.md>), [hierarchical-sql](<https://devfeed.tech/tags/hierarchical-sql.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [jackson](<https://devfeed.tech/tags/jackson.md>), [java](<https://devfeed.tech/tags/java.md>), [jooq-development](<https://devfeed.tech/tags/jooq-development.md>), [json](<https://devfeed.tech/tags/json.md>), [nested-collections](<https://devfeed.tech/tags/nested-collections.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [recursive-sql](<https://devfeed.tech/tags/recursive-sql.md>), [sql](<https://devfeed.tech/tags/sql.md>)

### AI overview

A tutorial on converting flat parent-child data into hierarchical structures using SQL, Java, or jOOQ. It compares a recursive PostgreSQL query with jOOQ 3.19 and a reusable pure-Java Collector, and discusses JSON serialization with Jackson and type inference considerations.

### Source excerpt

Occasionally, you want to write a SQL query and fetch a hierarchy of data, whose flat representation may look like this: The result might be: |id |parent_id|label | |---|---------|-------------------| |1 | |C: | |2 |1 |eclipse | |3 |2 |configuration | |4 |2 |dropins | |5 |2 |features | |7 |2 |plugins | |8 |2 ... Continue reading How to Turn a List of Flat Elements into a Hierarchy in Java, SQL, or jOOQ ->

## The Many Different Ways to Fetch Data in jOOQ

DevFeed: [The Many Different Ways to Fetch Data in jOOQ](<https://devfeed.tech/articles/the-many-different-ways-to-fetch-data-in-jooq-28962.md>)

Original publisher: [Read original article](<https://blog.jooq.org/the-many-different-ways-to-fetch-data-in-jooq/>)

Author: lukaseder

Published: 2022-05-19T07:29:09Z

Content type: tutorial

Language: en

Sources: [jOOQ](<https://devfeed.tech/sources/jooq.md>)

Topics: [jooq](<https://devfeed.tech/topics/jooq.md>), [Java](<https://devfeed.tech/topics/java.md>), [SQL](<https://devfeed.tech/topics/sql.md>)

Tags: [collections](<https://devfeed.tech/tags/collections.md>), [collector](<https://devfeed.tech/tags/collector.md>), [convenience](<https://devfeed.tech/tags/convenience.md>), [fetching](<https://devfeed.tech/tags/fetching.md>), [java](<https://devfeed.tech/tags/java.md>), [jdbc](<https://devfeed.tech/tags/jdbc.md>), [joo-f6a0c60d3d07](<https://devfeed.tech/tags/joo-f6a0c60d3d07.md>), [jooq](<https://devfeed.tech/tags/jooq.md>), [jooq-in-use](<https://devfeed.tech/tags/jooq-in-use.md>), [optional](<https://devfeed.tech/tags/optional.md>), [r2dbc](<https://devfeed.tech/tags/r2dbc.md>), [reactive-streams](<https://devfeed.tech/tags/reactive-streams.md>), [sql](<https://devfeed.tech/tags/sql.md>), [stream-api](<https://devfeed.tech/tags/stream-api.md>), [streams](<https://devfeed.tech/tags/streams.md>)

### AI overview

This tutorial explains several ways to fetch data with jOOQ, including eager result-set fetching, external and internal iteration, single-record retrieval, optional results, and resource-managed fetching for large data sets.

### Source excerpt

The jOOQ API is all about convenience, and as such, an important operation (the most important one?) like fetch() must come with convenience, too. The default way to fetch data is this: It fetches the entire result set into memory and closes the underlying JDBC resources eagerly. But what other options do we have? Iterable ... Continue reading The Many Different Ways to Fetch Data in jOOQ ->