Asset 20 8 2
Does AI recommend your business? Run the free check →

Join 15,000 business owners, marketers and entrepreneurs. The Sunday newsletter you'll be annoyed only arrives once a week.

Article

Application Performance Monitoring Tools: Nine to Shortlist

A hosted APM with distributed tracing is the safe first buy for a team running several services, while a language-focused APM suits a single Rails, Django or Node.js app better and costs less effort to set up. Open-source, self-hostable platforms make sense when you have the people to run them and want firm control over data costs.

An APM tool chosen badly tends to fail in one of two ways. Either it's too small, and the first serious outage involves three services and a database it can't see across. Or it's too big, and the bill grows every month because it's charging for data, hosts or seats nobody planned for. Both are avoidable with a handful of questions asked up front, and those questions make up the bulk of this page.

What APM tools watch, and what decides the bill

Application performance monitoring sits inside your running code. It records each request as it moves through your services, timing the slow database query, the external API call and the function that suddenly takes twice as long after a release. Alongside that you get error tracking, service maps showing which parts depend on which, and alerts when response times drift.

The category has three broad types. Full observability platforms combine APM with logs, metrics and infrastructure monitoring in one product. Language-focused APM tools concentrate on a set of frameworks and aim to be useful within minutes of installing an agent. Open-source, self-hostable platforms, often built on OpenTelemetry, can run on your own servers or as a managed cloud service. The bill follows different units for each: hosts, seats, gigabytes of data ingested, or requests per month.

Application performance monitoring tools to shortlist

Datadog APM

Distributed tracing and code-level performance data, sitting inside the wider Datadog monitoring platform alongside its other products.

New Relic

An observability platform whose APM product links application performance to what customers experience, priced on the data you send in.

Elastic Observability

Part of the Elastic stack, run hosted or self-managed, with Elastic APM tracing requests as they cross microservices.

Honeycomb

Built for asking questions of live systems, with service maps and a BubbleUp feature that surfaces what's behind unusual behaviour.

AppSignal

Error tracking and APM in one for Ruby, Elixir, Node.js, Python and other stacks, billed on request volume.

Scout APM

Rails, Django, Laravel, Phoenix and Node.js teams get application monitoring and error tracking aimed squarely at those frameworks.

SigNoz

Open source and also available hosted, this observability platform brings APM, logs and traces together under usage-based billing.

Uptrace

OpenTelemetry-based APM with a service graph, tracing, metrics and alerting, offered hosted or for running on your own servers.

Work with me

Want AI doing the heavy lifting in your marketing?

I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.

OpenObserve

Logs, metrics and traces in one open-source platform, with APM, real user monitoring and error tracking, self-run or managed.

A starting point for each kind of team

For a single web app on one framework, I'd start with a language-focused APM: you'll have useful traces the same afternoon. For a growing set of services, a full observability platform or an OpenTelemetry-based tool earns its keep the first time an incident crosses three of them. For teams with tight data budgets and the skills to run infrastructure, an open-source platform you can self-host is worth a serious look. APM doesn't replace checks from outside the app, so pair it with one of the website monitoring tools, and when the trouble sits in the machines rather than the code, look at server monitoring tools too. The questions below cover the details behind each pick.

Do you make application performance monitoring or observability tools? Tool makers can ask to be considered for a featured place on this list.

Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.

Frequently asked questions

What does an APM tool show that logs and uptime checks don't?

Logs tell you what happened in one place; uptime checks tell you whether the site answers at all. APM joins the dots inside a request. When a checkout page takes four seconds, a trace shows you that the bulk of the time went on one slow database query in a payment service, not on the page itself. It also groups errors by cause, maps which services call which, and shows how performance changed after each release. You'll still want uptime checks from outside the app. APM is the layer that explains why a page is slow once those checks have told you it's slow.

How is application performance monitoring priced?

Several billing units are in use, and the unit matters more than the headline figure. Big suites can charge by host or by seat. Some platforms charge by gigabytes of data ingested, often with a free monthly allowance before charges start. Some language-focused tools charge by the number of requests your app handles each month. Open-source platforms with a managed cloud may bill per gigabyte of logs and traces plus a separate rate for metrics, and some state plainly that there's no charge for seats or hosts. Each vendor's pricing page lists the current rates. Before comparing, estimate your monthly requests, your data volume and the number of hosts and people involved, then price the same workload everywhere.

Is open-source APM good enough to run on our own servers?

For many teams, yes, with one condition: someone has to run it. Open-source observability platforms cover APM, traces, logs and metrics, and you control where the data lives and how long it's kept. The cost moves from a vendor bill to your own servers, storage and staff time, and storage for traces grows quickly on a busy app. A sensible route is to start on the vendor's managed cloud version, learn how much data you produce, and only then decide whether self-hosting saves money. Where a tool is built on OpenTelemetry, the instrumentation in your code doesn't need to change when you move between hosted and self-run.

Do we need a full observability platform, or is a language-focused APM enough?

Count the moving parts. A monolith on one framework, a database and a cache is well served by a language-focused tool: setup tends to be quick, the defaults match your framework, and the screens speak its language. Once you're running several services, queues and third-party APIs, problems start to cross boundaries, and you'll want traces, logs and infrastructure metrics joined in one place. That's the job of a full platform. The trade is complexity and, usually, a larger bill. And when the trouble usually starts at the machine rather than the code, server monitoring may fill the gap more cheaply.

What difference does OpenTelemetry make when picking an APM tool?

OpenTelemetry is an open standard for collecting traces, metrics and logs from your code. Instrument with it, and the data can be sent to any backend that accepts it, rather than being tied to one vendor's agent. That lowers the cost of changing your mind later, which is exactly what you want in a category where prices and needs shift. Some tools on this list are built around OpenTelemetry from the start; others accept it alongside their own agents. When you shortlist, ask each vendor whether every feature works with OpenTelemetry data or whether some screens still expect their proprietary agent.

How can we trial an APM tool in an afternoon?

Pick one service that matters and one slow request you already know about. Install the tool's agent or an OpenTelemetry setup on that service only, in a staging environment if you can. Generate some traffic, then try to find the slow request without looking at the code. Note how long it takes to reach the slow span in a trace, whether errors arrive grouped by cause, and whether the service map shows the database and external calls you expected. Finally, check the usage screen to see how much data the afternoon produced, then multiply up to estimate a month. That last step tells you more about the real bill than any plan comparison.

Published and maintained by the Lilach Bullock team, covering marketing, AI and business growth.
Your buyers are asking AI who to use. Does it say you?

See for free whether ChatGPT, Claude, Perplexity, Gemini and Google name you, and get the plan to become the answer.

Check my AI visibility →
Sundays only

Get the Sunday newsletter.

One email a week. AI experiments, marketing tactics, and the workflows Lilach is building right now in her own business.

Subscribe free

Let’s get your marketing running on AI.

Book a free 30-minute call

We figure out what you need, where AI fits in, and what working together would look like.

Book the call →

Or take the 30-second calculator

You’ll see the hours and the money quietly leaking out of your week, and the three workflows worth building first.

Take the calculator →

Or grab the free AI resource library

Prompt packs, templates, checklists, and swipe files. The exact tools I build for paying clients. Yours, free.

Get the library →
Keep reading

More from the blog.