FAQ
-
General
Can I use the old Audit Log API during the Public Preview?
Yes. From March until May 1st, 2026, both the old Audit Log API and the new Telemetry Router will be active. We strongly recommend using this overlap period to migrate your scripts and integrations.
Why is it called "Telemetry Router" if it only handles Audit Logs?
The name reflects our long-term vision for the product. While we are launching with Audit Logs exclusively, the Telemetry Router is built to eventually handle other observability signals, such as service logs and metrics, in future updates.
Where can I send my audit data with the new Telemetry Router?
The Telemetry Router offers flexible routing options. You can configure it to send audit data to STACKIT services (such as STACKIT Observability, STACKIT Logs, STACKIT Object Storage) or to external solutions (such as your own SIEM tools or third-party storage), giving you full control over where your data resides.
What data format/protocol does the Telemetry Router support?
For the initial release, the Telemetry Router exclusively supports the OTLP (OpenTelemetry Protocol) standard. This ensures broad compatibility with modern observability ecosystems. Please ensure your target destinations or integration scripts are compatible with OTLP.
Will my old audit data be automatically moved to the Telemetry Router?
The Telemetry Router is designed to process incoming streams of data. Historical data stored in the legacy Audit Log system will not be automatically transferred. Please ensure you have downloaded any required historical logs via the legacy Download API before May 1st, 2026.
What happens if I don't migrate by May 1st?
On May 1st, 2026, the legacy API endpoints will become unreachable, and the Audit Log screens in the Portal will disappear. If your applications rely on the old Download API, they will stop functioning.