Skip to main content
Apitally integrates with your application through open-source SDKs built on OpenTelemetry. The SDKs send data directly to Apitally, without requiring a separate collector or agent, and can work alongside an existing OpenTelemetry setup.

SDK for Python

SDK for Node.js

SDK for Go

SDK for .NET

The SDKs include the following functionality:
  • Discovery of available endpoints in your application
  • Capture of request and response data, including traces
  • Capture of application logs associated with requests
  • Aggregation of request metrics and collection of application CPU and memory usage
  • Background export of collected data to Apitally
The SDKs are designed to be resilient to temporary network failures when communicating with Apitally and will retry sending data for up to 1 hour.

​
On startup

The SDK collects application metadata, such as endpoint details and version information, and sends it to Apitally in the background.

​
During runtime

As your application handles requests, the SDK captures the HTTP method, matched route and response status code. It also measures server-side response time and the sizes of request and response bodies. It aggregates this data locally into request metrics, grouped by endpoint, status code and consumer. Alongside these metrics, the SDK builds traces of individual requests, linking instrumented operations and captured application logs to the request. The collected data is buffered locally and sent to Apitally in the background, normally about once a minute.

​
Server side

When Apitally receives data from your application, it queues it for asynchronous processing. The data is normally processed and visible on the dashboard within a few seconds. Request metrics are retained at 1-minute resolution for 32 days and at 30-minute resolution for 13 months. Request logs and traces are retained for 15 days, with longer retention available on request.