Observability Metrics setup and usage

Setup overview

Step	Description
Step 1: Book the Observability Metrics add-on	Contact your main sales representative to order the add-on and update your Transactional Email contract.
Step 2: Retarus prepares your setup	The Retarus Operations team sets up your dedicated Observability instance and endpoint.
Step 3: Receive credentials and endpoint	The Operations team provides you with the credentials and specific API endpoint for your Observability instance.

Remote read endpoint	Authentication method
`https://api.retarus.com/stable/retarus/metrics/1.0/[your_customer_number]`	Basic authentication

Name	Description
`temudr_count_total`	Running counter of all emails (per recipient).
`temudr_duration_seconds_sum`	Total processing time in the system for a single email.
`temudr_duration_seconds_count`	Number of data points capturing processing time. Used to calculate average processing time by dividing `temudr_duration_seconds_sum` by `temudr_duration_seconds_count` with the same label filters. This helps determine the average processing time for a specific type of event. CODE `rate(temudr_duration_seconds_sum{interface="$interface", status="$status",event_phase="$eventphase"}[$__rate_interval]) / rate(temudr_duration_seconds_count{interface="$interface", status="$status", event_phase="$eventphase"}[$__rate_interval])`

Name	Description	Possible values
`datacenter`	Indicates which Retarus datacenter processed and sent the message.	DE1, DE2, US1, US2, SG1, CH1
`event_phase`	Shows the phase in which the message reached its final processing status.	PRE_PROCESS, PROCESS, DELIVER, SMART_DELIVERY
`event_subtype`	Provides more detailed information about the final status of a message after processing.	VALIDATION_ERROR, INVALID_ADDRESS, FORBIDDEN_RECIPIENT, PROCESSING_FAILED, SUPPRESSED, PREVIOUSLY_BOUNCED, OK, HARD_BOUNCE, SOFT_BOUNCE
`interface`	Indicates the entry interface used to submit the message to the Transactional Email service.	rest, smtp
`status`	Gives general information about the final status of the processed message.	OK, ERROR
`status_code`	The SMTP status response code received by Transactional Email MTAs (Mail Transfer Agents).	See full list: SMTP response codes documentation
`substatus`	Used to group messages according to the three main expected outputs after submitting a JobRequest.	DELIVERED, BOUNCED, DROPPED
`tenant`	Indicates which tenant the Transactional Email Technical Account is assigned to.	multiple
`user_id`	The Technical Account ID under which the message was processed.	multiple

Use the provided federation endpoint (compatible with Prometheus federation) to retrieve metrics data.
Filter data using federation queries or process it locally on your own system.
Control how long you retain data within your own observability system.
Retarus can be integrated with any standard observability platform, including Dynatrace, New Relic, Grafana, Splunk, and Datadog.