Debug API issues faster
with request logs for Echo
Get the full picture by inspecting API request and response details alongside correlated application logs, all in one place. Highly configurable and with built-in data masking.
Discover & investigate: Drill down from API metrics to individual logged requests
Apitally bridges the gap between aggregated API metrics and request-level debugging. If you spot anomalies in your metrics, you can drill down to the relevant requests and understand exactly what happened.
The request logs include the full URL, headers and payloads of requests and responses (subject to configuration), helping you investigate and resolve issues faster.
Search & filter: Find and inspect any logged API request with ease
Pinpoint exactly what you're looking for with comprehensive search and filtering options, including by consumer, endpoint, status code, response times and more.
An interactive timeline graph allows you to easily zoom into specific periods during incident investigations.
Performance & privacy: Built for production with complete privacy control
Our SDKs handle logging asynchronously with negligible impact on the performance of your API. Log data is compressed and buffered to disk before being sent to Apitally in the background.
You can limit the data included in request logs, configure masking for sensitive information, and exclude requests from logging. The SDKs apply masking and exclusions in your application before sending log data to Apitally.
Other benefits: Made for developers and product owners
Testimonials: What our users are saying
Easy setup: Get started in 3 simple steps
import (
apitally "github.com/apitally/apitally-go/echo-v4"
"github.com/labstack/echo/v4"
)
func main() {
e := echo.New()
config := apitally.NewConfig()
config.WriteToken = "your-write-token"
config.Env = "dev" // or "prod" etc.
apitally.Init(e, config)
}
Pricing: Choose the right plan for you
Try Apitally free for 14 days, then decide which plan best suits your needs. No credit card required at sign up.
- 1 app
- 1 dashboard user
- 100 API consumers
- Unlimited API requests for metrics
- 1M request logs / month
- Application logs & traces
- Slack & Teams integration
- 3 apps
- 3 dashboard users
- 1,000 API consumers
- Unlimited API requests for metrics
- 5M request logs / month
- 20M logs & spans / month
- Slack & Teams integration
- 10 apps
- Unlimited dashboard users
- Unlimited API consumers
- Unlimited API requests for metrics
- 25M request logs / month
- 100M logs & spans / month
- Slack & Teams integration
Frequently asked questions: Learn more before you dive in
Can't find the answer you're looking for? Reach out via email or on Slack and we'll get back to you as soon as we can.
There's no limit on the number of API requests processed for metrics and analytics, since these features rely on aggregated data.
Request log ingestion is subject to monthly quotas, as detailed in the pricing section above.
If you exceed the API consumer limit for your plan, you'll enter a one-time grace period. During this time, you can either upgrade to a higher plan or reduce usage to stay within limits. If the grace period ends and you're still over the limit, Apitally will stop ingesting data from your apps.
If you exceed your monthly quota for request logs, Apitally will stop ingesting new requests until the quota resets at the start of the next month. This won't affect your API metrics. The same applies to application logs and traces.
On the Starter and Premium plans, you can enable usage-based billing for overages. If enabled, ingestion will continue beyond your quota, and you'll simply be charged for the extra usage.
For API metrics and analytics, the Apitally SDKs collect only non-sensitive metadata about your endpoints, requests, and responses. This includes HTTP methods, paths, status codes, timing, and payload sizes. Metrics are aggregated on the client side before being sent to Apitally.
For request logs, application logs, and traces, there are extensive configuration options to control what's collected and to mask or exclude sensitive data.
You can find more detailed information about what data is collected and how we handle it in our docs.
Apitally retains aggregated API metrics for 1 year, allowing you to analyze long-term trends in API usage, errors, and performance.
Request logs, application logs, and traces are retained for 15 days. Reach out if you require longer retention.
You can find more detailed information about data storage and retention in our docs.
Apitally currently supports the following web frameworks:
- AdonisJS (Node.js)
- ASP.NET Core (C#)
- BlackSheep (Python)
- Chi (Go)
- Django Ninja (Python)
- Django REST Framework (Python)
- Echo (Go)
- Elysia (Bun)
- Express (Node.js)
- FastAPI (Python)
- Fastify (Node.js)
- Fiber (Go)
- Flask (Python)
- Gin (Go)
- H3 (Node.js / Deno / Bun)
- Hapi (Node.js)
- Hono (Node.js / Bun)
- Koa (Node.js)
- Litestar (Python)
- NestJS (Node.js)
- Starlette (Python)
Please let us know if you're interested in using Apitally with a framework that is currently not supported.
Apitally supports Cloudflare Workers via a Logpush integration and our Serverless SDKs. These currently support Hono and FastAPI.
You can find more details in our setup guide for Cloudflare Workers.
Support for other serverless platforms may be added in the future based on user demand.
Apitally offers a CLI and agent skill that give AI agents like Claude Code, Cursor, and Codex full access to your API metrics and request logs. We chose this approach over MCP because it's more token-efficient and reliable, while giving agents richer investigation capabilities.
Read more about it in our blog post.