There have been some major improvements in the audit functionality in API Connect v10.0.8.3. It has always been possible to capture the audit events in API Manager and send that data to external systems, but now in v10.0.8.3 that feed of audit events now encompasses the whole APIC platform including other subsystems such as analytics and the developer portal. All auditable actions throughout the whole of API Connect are now visible in a single data stream.

That stream of events can now also be sent to APIC Analytics itself. This allows the data to then be offloaded to any of the remote systems which analytics offload supports (e.g. Noname Security), and also allows it to be stored internally within analytics.

If they are stored in analytics, then Audit events are stored in distinct indices away from the gateway API events (the transactional data that analytics has traditionally stored), and they have their own retention policy. This policy can be customised in the usual way and defaults to 30 days.

Audit UI

If you opt to store audit events in analytics then there is also a new page in the UI to browse and filter through them. This makes it far simpler to see what is happening in your APIC platform. There’s a very good blog post on this new UI available here: https://community.ibm.com/community/user/blogs/abhishek-kumar3/2025/07/29/introducing-the-audit-events-ui-in-api-connect

Engagement

Since analytics now has the audit events available it can also make use of that data as a datasource in Engagement. This allows rules to be created that are based on lifecycle actions within the APIC platform rather than based on transactional API events in the gateway. This is covered in a recent blog post on engagement: https://community.ibm.com/community/user/blogs/chris-dudley1/2025/08/01/business-engagement-platform-now-available-in-lts

#IBMAPIConnect #analytics #audit