Sherpa
AWS observability

See what's slow. Fix it first.

Sherpa brings your AWS metrics, logs, traces and page speed into one place, right next to what each service costs, so your team knows what to fix first.

Sign up Available in AWS Marketplace

After you sign up, a member of the Sherpa team contacts you within one business day to discuss your AWS environment and the right way to start.

Sherpa

What's slowing our customers down this week?

checkout-api is the slowest, and failing most.

Servicep95Error rateNext step
checkout-api 1.8 s 4.2% investigate in Automate
search 940 ms 0.6% investigate in Automate
orders-worker 620 ms 1.1% investigate in Automate
Sherpa mascot holding a camera
How it works

Your AWS data in, a clear answer out.

CloudWatch data from your AWS accounts and OpenTelemetry data from your applications flow into Sherpa. You ask questions or open dashboards. Sherpa writes a plan, and your team applies the fix.

Your team chooses what to collect. CloudWatch charges go on your own AWS bill, and Sherpa shows the estimated cost of each setting (off, daily or real-time) before you turn it on.

What you see

What can we see in Sherpa?

  • Metrics

    Health and performance for the AWS services you run, in one dashboard.

    • CloudWatch metrics for AWS services, from EC2, RDS and Lambda to ECS, EKS, load balancers, DynamoDB, SQS and Bedrock.
    • Search any metric across your AWS services and applications.
    • See the estimated monthly cost of collecting metrics before you turn collection on.

  • Logs

    Search every log line without learning a new query language.

    • Text search, filters and a histogram.
    • Live tail to watch new log lines as they arrive.
    • An overview of errors and severity, so problems stand out.

  • Traces

    Follow one request across every service it touches.

    • Trace search and a live stream from your OpenTelemetry data.
    • Span waterfall, critical path, and a flow diagram for each trace.
    • Request rate, error rate, and p50, p95 and p99 latency by service, plus the slowest operations.

  • Lambda

    All your functions in one place, ranked by what needs attention.

    • Invocations, errors, and average and p95 duration.
    • Your busiest functions at the top, with errors beside each.
    • Cold starts and init time, with the Lambda extension installed.

  • Browser performance

    What your users feel when a page is slow or breaks.

    • Page views, sessions and JavaScript errors, page by page.
    • Page load time and Core Web Vitals (LCP, FCP, TTFB, INP, CLS).
    • Load time and errors for each page.

  • Health at a glance

    One status for every service, so you know where to look first.

    • Each service marked by colour: healthy, needs attention or degraded.
    • An application catalog of the services you run.
    • Saved views and share links for your team.
From slow to fixed

What happens when a service is slow?

Example
Example: Sherpa shows checkout-api is degraded, the trace points to the payments call, and Automate writes a plan your team applies.

Sherpa never applies a fix; your team does.

The problem

Why does finding a slow service take so long?

69%

of companies run six or more tools just to watch their systems.

Source: Omdia, 2026.

  • Performance sits in one tool, the bill in another, security in a third.
  • Your engineers stitch them together by hand during every incident.
  • Sherpa shows all three side by side, and answers in one chat.
No surprises

What does monitoring data cost us?

  • CloudWatch data is billed to your own AWS account.
  • Sherpa shows the estimated monthly cost of each setting (off, daily or real-time) before you turn it on. Real-time needs your AWS Organizations management account connected.
Sherpa mascot working on a laptop

See your slowest service this week.

After you sign up, a member of the Sherpa team contacts you within one business day to discuss your AWS environment and the right way to start.

Sign up Available in AWS Marketplace
Questions

Questions we get asked.

Does Sherpa replace CloudWatch?

No. Sherpa reads your CloudWatch data and shows it next to your cost and security findings.

Do I need OpenTelemetry?

Not for CloudWatch metrics and logs. For traces from your own code, your team sends OpenTelemetry data from its collector or SDK with a Sherpa API key.

Does Sherpa send alerts?

Not today. Your team opens Sherpa, or asks it a question, when a service looks slow or errors rise.

How is this different from an APM tool?

Sherpa shows performance next to your AWS cost and security. Automate then writes a plan to fix the slow or failing service.

What does monitoring data cost?

CloudWatch data is billed to your AWS account. Sherpa shows the estimated cost of each setting (off, daily or real-time) before you turn it on.

Still have a question?

Contact us