SLA status API
The service only supports the latest version of the SLA, published at maestra.io/documents/sla for US accounts or maestra.io/documents/eu/sla for EU accounts)
The SLA status API shows how Maestra Platform is performing against its SLA for your account, broken down by feature. It returns data in Prometheus format, so you can add it to the monitoring and alerting you already use.
Connect to PrometheusYou can scrape the service directly from Prometheus. Add it as a scrape target using the
scrape_configsection ‚see the Prometheus configuration docs.
Endpoint
GET https://sla.maestra.io/v1/clientAuthentication
The service uses Basic authentication. Pass any API endpoint from your Maestra account as the credentials:
| Credential | Value | Required |
|---|---|---|
username | The API endpoint's external ID | Yes |
password | The API endpoint's secret key | Yes |
Join them as username:password, encode the string in Base64, and send it in the Authorization header.
GET https://sla.maestra.io/v1/client
Authorization: Basic <base64 encoded string>Response
The response is a set of Prometheus metrics ‚ one sla_violation gauge per feature. The tenant label holds your account's system name.
# HELP sla_violation
# TYPE sla_violation gauge
sla_violation{feature="CalculationDiscounts",tenant="your-account"} 0
sla_violation{feature="CalculationDiscountsDegradation",tenant="your-account"} 0
sla_violation{feature="DisplayingWidgets",tenant="your-account"} 0
sla_violation{feature="MailingsSendingSpeed",tenant="your-account"} 0
sla_violation{feature="OrderProcessing",tenant="your-account"} 0
sla_violation{feature="OrderProcessingDegradation",tenant="your-account"} 0
sla_violation{feature="PersonalArea",tenant="your-account"} 0
sla_violation{feature="PersonalAreaDegradation",tenant="your-account"} 0
sla_violation{feature="Personalization",tenant="your-account"} 0
sla_violation{feature="TransactionalWorkflow",tenant="your-account"} 0How to read each value:
0‚ the SLA for that feature is being met.1‚ the SLA for that feature is being violated right now.
What the service monitors
For now, the service only reports SLA violations for synchronous integrations ‚that is, operations you call in sync mode.
| Feature | What it covers |
|---|---|
Personalization | Synchronous calls to personalization operations |
CalculationDiscounts | Synchronous calls that calculate discounts and points in the cart |
CalculationDiscountsDegradation | Synchronous calls that calculate discounts and points in the cart (degradation) |
PersonalArea | Synchronous calls to operations that power your customer-facing interfaces |
PersonalAreaDegradation | Synchronous calls to operations that power your customer-facing interfaces (degradation) |
OrderProcessing | Synchronous calls to order processing operations |
OrderProcessingDegradation | Synchronous calls to order processing operations (degradation) |
DisplayingWidgets | Displaying recommendation widgets |
MailingsSendingSpeed | Bulk campaign sending speed |
TransactionalWorkflow | Transactional messages sent from flows after an order |
CalculationDiscountsDegradationandOrderProcessingDegradationmap to this SLA clause: the Error Rate of synchronous requests for API methods exceeds 0.005 at T = 4 seconds per twenty-four hours, or an Error code 500 or 503 occurs ‚for calculating discounts and bonus points in the cart, and for operations that process orders. See the full terms in the SLA.
Updated 28 days ago

