Request logging for Spring Boot
with privacy built-in
Find and inspect any API request by drilling down from analytics dashboards or through powerful filtering options. Configure exactly what is logged to meet your requirements.
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.
Flexible configuration options let you control exactly what gets logged. Mask sensitive data, exclude specific paths, and implement custom rules. All aspects of logging are opt-in by default.
Other benefits: Made for developers and product owners
Testimonials: What our users are saying
Easy setup: Get started in 3 simple steps
import org.springframework.boot.SpringApplication;import org.springframework.boot.autoconfigure.SpringBootApplication;import io.apitally.spring.UseApitally;@UseApitally@SpringBootApplicationpublic class Application {public static void main(String[] args) {SpringApplication.run(Application.class, args);}}
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
- 5 active app instances
- Unlimited aggregated API requests
- 500,000 logged API requests
(per month) - 100 API consumers
- 5 custom alerts
- Health checks
- Slack & Teams integration
- Data export & API access
- 3 apps
- 3 dashboard users
- 15 active app instances
- Unlimited aggregated API requests
- 2 million logged API requests
(per month) - 1,000 API consumers
- 15 custom alerts
- Health checks
- Slack & Teams integration
- Data export & API access
- 10 apps
- Unlimited dashboard users
- 50 active app instances
- Unlimited aggregated API requests
- 10 million logged API requests
(per month) - Unlimited API consumers
- Unlimited custom alerts
- Health checks
- Slack & Teams integration
- Data export & API access
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 API requests processed for metrics and analytics, since these features rely on aggregated data.
However, logged API requests are subject to monthly limits, as detailed in the pricing section above.
If you exceed the app instance or API consumer limits 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 logged API requests, Apitally will stop ingesting new logged requests until the quota resets at the start of the next month. This won’t affect your API metrics.
For API metrics and analytics, the Apitally SDKs collect only non-sensitive metadata about your endpoints, requests, and responses — such as HTTP methods, paths, status codes, timing, and payload sizes. Data is aggregated client-side before being sent to Apitally.
For request logging, you have full control over what gets logged, with built-in support for masking sensitive data.
Apitally retains aggregated API metrics for 1 year, allowing you to analyze long-term trends in API usage, errors, and performance.
Logged API requests are retained for 15 days.
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)
- Express (Node.js)
- FastAPI (Python)
- Fastify (Node.js)
- Fiber (Go)
- Flask (Python)
- Gin (Go)
- H3 (Node.js / Deno / Bun)
- Hono (Node.js / Bun)
- Koa (Node.js)
- Litestar (Python)
- NestJS (Node.js)
- Spring Boot (Java)
- Starlette (Python)
Support for more frameworks may be added based on feedback from the community. Please let us know if you're interested in using Apitally with a framework that is currently not supported.
No, Apitally currently doesn't work in event-driven serverless deployments, such as on AWS Lambda or Cloudflare Workers. This is because the Apitally SDKs require a long-running process to aggregate and send data to the Apitally servers in the background.
Apitally uses Stripe to manage subscriptions and payments. Stripe is a secure and PCI-compliant payment platform trusted by millions of businesses worldwide. Your payment details are handled exclusively by Stripe. Apitally never sees or stores your card information.