AppSignal APM
AppSignal is an APM and error monitoring platform purpose-built for Ruby, Elixir, and Node.js that collects errors, performance traces, custom metrics, and logs through a REST API and language-native agents.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
API token passed as query parameter is a security concern. No OAuth, no fine-grained scopes. TLS enforced on all endpoints.
⚡ Reliability
Best When
The stack is primarily Ruby on Rails, Phoenix, or Node.js and the team wants a low-configuration, all-in-one APM with errors, traces, logs, and metrics in one place.
Avoid When
The application is written in Go, Java, Python, or another language not supported by AppSignal's native agents, or the team requires a self-hosted APM solution.
Use Cases
- • Querying recent error incidents for a specific app to triage production issues
- • Fetching performance metrics (throughput, response time, Apdex) for a time range to detect regressions
- • Pulling log streams for a deployment window to correlate errors with a release
- • Creating or updating alert triggers programmatically when deploying new services
- • Retrieving host-level metrics (CPU, memory, disk) to correlate infrastructure issues with application errors
Not For
- • Polyglot stacks — deep instrumentation is limited to Ruby, Elixir, and Node.js (other languages lack native agents)
- • Full-stack distributed tracing across many microservices (Datadog or Jaeger is more capable at that scale)
- • Real user monitoring (RUM) or front-end JavaScript performance tracking
Interface
Authentication
API authentication uses a personal API token passed as a query parameter (?token=) or Authorization header. App-level push API keys are used by language agents for data ingestion. No OAuth or fine-grained scopes.
Pricing
Pricing is per app per month. Higher tiers unlock longer retention, more hosts, and advanced features like anomaly detection.
Agent Metadata
Known Gotchas
- ⚠ API token is passed as a query parameter in many examples, which risks token leakage in server logs
- ⚠ The REST API for reading data (errors, metrics) is separate and less documented than the data ingestion (push) API
- ⚠ App identifier (app_id) must be obtained through the dashboard before making most API calls — no discovery endpoint
- ⚠ Time ranges in queries use Unix timestamps and timezone handling is not clearly documented
- ⚠ Rate limit headers are not consistently returned, making adaptive throttling difficult for agents
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for AppSignal APM.
Scores are editorial opinions as of 2026-03-06.