Enhanced API Traceability for Multi-Tenant AI Infrastructure

The need for tenant-aware API traceability

A single Netris deployment may perform network operations across many different customers and tenants. As more of those operations are initiated programmatically, operators need visibility into what API activity occurred, including the customer, tenant, or operation associated with it.

An operator managing infrastructure for both Customer Alpha and Customer Bravo may use the same underlying orchestration platform, but the network operations performed for each still need to be attributable to the correct customer.

In other words, if an API request is initiated for Customer Alpha, the operator should be able to distinguish and trace that request separately from activity associated with Customer Bravo.

Adding tenant context to API logs

Netris 4.15 enhances API traceability by adding optional trace information to individual API requests. API logs now include three new fields (see image below): Trace ID, Trace Span ID, and Trace Parent ID.

These fields allow an API consumer to associate a request with external context, such as a tenant ID, customer billing ID, or a specific operation being performed for a tenant. A Trace ID can also follow a complex provisioning operation spanning multiple API requests, allowing related activity to be traced across the API logs.

Why tenant context matters

As neoclouds and AI factories scale, so does the volume of tenant activity and API-driven network operations. When an operator needs to understand a network change for troubleshooting or for an audit, tenant-aware API traceability provides a clearer record of the activity associated with each environment.

Multi-tenancy requires more than keeping individual environments separated. Operators also need to understand the activity taking place within each environment. As more network operations are initiated programmatically, preserving tenant context in API logs gives operators greater visibility into those operations.