Filtering Layer7 OTEL traces

Products

• CA API Gateway

Issue/Introduction

Our team is working on connecting the Layer7 gateway to our observability cluster using the Opentelemetry SDK in version 11.1.0 of the Layer7 gateway.

However, we have seen through a performance test that this has a significant impact on gateway performance.

Applying a filter to exclude some of the assertions has led to better performance, but now we do not receive any information about the routing.

It is true that our routing assertion is deeply embedded in our policy logic, within included fragments and “all”/”one” assertions, so nested.

How can we adjust the OTEL filter to only send routing traces that are deeply embedded in the policy logic?

This is the current assertion filter:

"assertions" : { "include": [".*Route.*", "Framework -.*", ".*-v.*", "Include Policy Fragment"] }

 

Resolution

At this point, we will not create spans for included assertions that are nested in excluded assertions.

At a minimum, you would have to include the assertions in which your route assertions could be nested in your filter.

For example, this filter would include route assertions, at least one assertions and include policy fragment assertions:

And would provide this trace (minus all of the other assertions in the API policy or policy fragment):