terraform-aws-jaeger VS docs

It's really not that intense. I basically set up my last co's telemetry infrastructure all by myself, using terraform, otel-python, jaeger, and AWS elasticsearch.

This TF project does most of the heavy lift. https://github.com/telia-oss/terraform-aws-jaeger

Once you've collected metrics with OpenTelemetry, you can export them using any supported OpenTelemetry exporter. To export them to Prometheus, we’ll add the .AddPrometheusExporter() method to the metric configuration. It works as a pull model, with a scrap date from the application. That means, an application should provide an endpoint with metrics for scrapping. To do that we need to add middleware app.MapPrometheusScrapingEndpoint(). Prometheus scrapes this /metrics endpoint at regular intervals to collect the application’s time-series data metrics:

Prometheus text exposition format is de-facto standard used in monitoring. It would be great building an official observability standard on top it. This format is much easier to debug and understand than OpenTelemetry for metrics. It is also more efficient, e.g. it requires less network bandwidth and less CPU for transfer than Otel for metrics.

[1] https://github.com/prometheus/docs/blob/main/content/docs/in...

I've set up prometheus to monitor kubernetes metrics by following the prometheus documentation.

It was added back to Prometheus.

https://github.com/prometheus/docs/blob/main/content/docs/in...

Exporters are third-party tools that send metrics to the Prometheus server. When Prometheus cannot access metrics, it uses exporters. These exporters export metrics from systems and send the metrics to the Prometheus server. There are official and non-official exporters in Prometheus' GitHub organization.

Now I'm looking for another energy monitor and I'm really struggling to find one! https://github.com/prometheus/docs/blob/main/content/docs/instrumenting/exporters.md

Metrics are exposed in a simple text-based format.