Open telemetry standards

OpenTelemetry in Argentina for interoperable observability.

We design OpenTelemetry instrumentation and pipelines to produce, process and export metrics, traces and logs with consistent conventions. Architecture retains flexibility to choose backends according to each need.

Implementation in ArgentinaIntegration with your stackDocumented operation
Technology we integrate
OpenTelemetry logo
Grafana logo
Prometheus logo
OpenTelemetry Argentina
OpenTelemetry logo
01 / In context

OpenTelemetry as a common instrumentation layer.

OpenTelemetry is a framework and toolkit open source, supplier agnostic, to generate, collect and export telemetry. It is not a storage or display backend: it standardizes APIs, SDKs, protocols, conventions and components such as the Collector.

It is valuable when there are multiple languages, runtimes, clouds or observability tools and the organization needs to reduce inconsistencies. Design should include sampling, attributes, privacy, processing and destination of data.

Expected results

What we solve with OpenTelemetry.

The tool is configured around the service, risks and decisions that each team needs to make.

01

Common instrumentation

Shared conventions for metrics, traces and logs between equipment and applications.

02

Flexible Pipelines

Collectors who receive, process and export telemetry to different backends.

03

Lower dependency

An interoperable capture layer that makes it easy to evolve tools and destinations.

04

Correlating context

Attributes and propagation designed to connect behavior between services.

Phased implementation

How we work with OpenTelemetry.

First we validate the context. Then we expand coverage with evidence, accountability and measurable criteria.

  1. 01

    Architecture

    We map services, languages, runtimes, current telemetry and backends.

  2. 02

    Conventions

    We define resources, attributes, names, propagation and sensitive data.

  3. 03

    Pipeline

    We configure SDKs, instrumentation and Collectors with controlled processing.

  4. 04

    Validation

    We measure coverage, quality, volume, latency and research utility.

Frequently Asked Questions

About OpenTelemetry Argentina.

Responses to assess scope, integration and next steps.

Does OpenTelemetry store metrics, traces or logs?

No. OpenTelemetry generates, collects, processes and exports telemetry; storage, analysis and visualization are handled by other backends.

Can OpenTelemetry be adopted in stages?

Yes. It is important to prioritize critical services, define conventions and validate a pipeline before extending instrumentation to the entire organization.

Does OpenTelemetry avoid relying on a provider?

It helps to decouple the instrumentation of a specific backend, although each destination can retain its own functionality, queries and costs.

What is the function of the OpenTelemetry Collector?

It can receive, process and export telemetry. Its topology, resources, security and availability must be designed according to volume and destinations.

Let's talk about your operation.

We evaluate how to integrate OpenTelemetry into your operation.

We review coverage, sources and risks to propose a clear scope, integrated with your technological reality.

✓ Initial evaluation✓ Custom-made scope✓ Specialist response
You can also write to us by WhatsApp
WhatsApp