Observability Metrics

Feature overview

Observability platforms help organizations gain control and automate workflows by providing real-time insights into the health, performance, and behavior of their applications, services, and infrastructure. These platforms collect data from logs, metrics, events, and traces, allowing both people and automated systems to identify issues before they affect customers.

With the Retarus Observability Metrics feature, integrating your data into observability platforms is straightforward. Retarus lets you pull real-time data in the Prometheus Exposition Format, making the process simple. The myEAS Dashboard uses this standardized data and displays it with pre-defined visual analyses. Retarus also allows you to access backend data directly within your own systems. This gives you the flexibility to gain insights you need, using the tools and workflows you’re already comfortable with.

📌 Gartner’s definition of observability platforms

Gartner defines observability platforms as tools that provide businesses with deep, real-time visibility into the health, performance, and behavior of their applications, services, and infrastructure. By collecting logs, metrics, events, and traces, these platforms allow both humans and automated systems to detect and address issues before they impact customers.

Benefits

Data is delivered directly to your preferred system (such as Splunk, Dynatrace, Datadog, Grafana, or Elastic) in a standardized, ready-to-ingest format. This streamlines operations and supports Retarus Transactional Email’s core principles:

• “Where are my emails?”

• “Is it working?”

You have real-time access to your email traffic, allowing you to quickly detect and respond to issues.

Requirements

Prometheus is flexible and lightweight for its primary use, but its requirements grow with the amount of data you collect from the Retarus Observability platform and how long you want to store it. Here are the main requirements:

• Host

  • You need to run a Prometheus server on your side.

  • Your prometheus.yml configuration file must include a remote_read section.

• Connectivity

  • Your system must be able to reach the Retarus Observability Metrics endpoint over a public HTTPS connection.