Cloud servicesnext to the hoststhat call them.

CloudWatch, Azure Monitor and Google Cloud metrics arrive through the same agent as everything else. Managed queues, databases and load balancers stop being a separate tab and start being part of the request they slow down.

insight / cloud monitoringLIVE
SERVICELOADERRVAL
rds/orders-primary
88%
sqs/checkout-jobs
1.2k
alb/public-edge
0.4%
s3/asset-bucket
12 ms
elasticache/session
0.9 ms

Managed services on the same dashboards as the application traces that depend on them.

Collected fromTrademarks →
What you get

Included on every plan, including the free tier.

01

AWS CloudWatch, Azure Monitor and Google Cloud metrics in the same tenant as your own hosts.

02

Managed service metrics on the same dashboards as the application traces that depend on them.

03

One set of alert rules across cloud and self-hosted, so an on-call engineer watches one place.

04

EU data residency, and a bulk extract of your own data whenever you ask for it on Enterprise.

How it gets there

Three steps, then it is reporting.

01Assign the cloud receiver to an agent from the portal.
02Grant it read access in the provider account.
03Cloud metrics land beside your host metrics.
What you can ask

What that looks like as a query.

PROMQL

aws_rds_cpuutilization_average > 80

Managed databases under pressure.

PROMQL

aws_sqs_approximate_number_of_messages_visible_average > 1000

Queues backing up before consumers notice.

PROMQL

sum by (load_balancer) (rate(aws_applicationelb_httpcode_target_5xx_count_sum[5m]))

Which load balancer is returning errors.

Questions

What teams ask about cloud collection.

Something not here? Book thirty minutes with an engineer who works on the platform. Book a call →

Do we need an agent inside each cloud account?
No. The cloud receiver runs on an agent you already have and pulls from the provider API with read access you grant it.
Does this replace the provider console?
It puts cloud metrics next to your traces and logs, which the console cannot do. The console stays where you go to change things.
Where does our data live?
In the EU. You can read it back out through the same open APIs your dashboards query, and on Enterprise we run a bulk extract for you on request.
What drives the cost of cloud metrics?
Series count. Per-instance dimensions multiply quickly, so drop the dimensions nobody queries at the agent before they are billed.

Start on the free tier.

20K active series, 50 GB of logs and 50 GB of traces a month, 90-day retention, and the whole of Insights.