[API Monitoring] Extract query params from OTeL attributes

[shivanshuraj1333]

Epic: #6815

Today we extract host and port from the http.url, but as per the initial designed we decided to keep the query params in the endpoint, as there are some complications in doing pattern matching.

As a further improvement of the feature, we can extract out query params and rely on OTeL attributes (this is still evolving with depreciation of lot of attributes).

Today we are extracting the host and port and endpoint, endpoint can be further improved to extract the base API endpoint and query params.

[prateek041]

Hey @shivanshuraj1333, just for my proper understanding, can you please confirm if this is what you mean:

Current implementation:

For a URL like : http://example.com:8080/path?query=param, currently signoz holds information
in three distinct parts.

• Host: which turns out to be example.com.
• Port: turns out to be 8080.
• Endpoint: turns out to be path?query=param which is the combination of actual endpoint + query params.

For this feature, we wish to separate endpoint and query params, so that we can rely on Otel collector attributes to process
the query parameters?

[shivanshuraj1333]

new OTeL semantic convention has a split for endpoint and query params, but most of the agents and SDK still follow the older conventions where http.url contains the complete endpoint including the query param.

This issue is to support both.

One of the solution is to split the endpoint at ingestion and save the triplet http.url, endpoint, query_parms,
and for the new convention only store the endpoint, and query_params.

the feature right now uses http.url, but once this is done, it can rely on only endpoint, and query_params.

[prateek041]

sure, thanks for the context.

I would like to give this issue a try if no one has already picked it up.