https://signoz.io logo
#support
Title
# support
u

Upesh Jindal

08/11/2022, 3:39 AM
Hi, is there any way to ignore certain endpoints?
p

Pranay

08/11/2022, 3:40 AM
@Upesh Jindal can you share in a bit more detail on what you mean and the use case? Do you want the application page to not show certain end points?
s

Srikanth Chekuri

08/11/2022, 3:41 AM
This should be configureable at the instrumentation level mostly. Which framework are you using?
u

Upesh Jindal

08/11/2022, 3:43 AM
Using FastAPI
And I need a streaming endpoint ignored
because the request almost never ends so latency is shown in minutes/hours
s

Srikanth Chekuri

08/11/2022, 3:43 AM
You should be able to achieve this by using
OTEL_PYTHON_EXCLUDED_URLS
env.
u

Upesh Jindal

08/11/2022, 3:43 AM
This is a usecase for all services where you would use Server sent events
I will try that. Is it a comma separated list variable, Srikanth?
s

Srikanth Chekuri

08/11/2022, 3:44 AM
Yes, comma separate regex that matches with endpoint
u

Upesh Jindal

08/11/2022, 3:46 AM
Copy code
["/endpoint1.*", "/endpoint2.*"]
Something like this?
s

Srikanth Chekuri

08/11/2022, 3:47 AM
No just a simple string with comma separated values. Here the config doc https://opentelemetry-python-contrib.readthedocs.io/en/latest/instrumentation/fastapi/fastapi.html#configuration. That should help.
u

Upesh Jindal

08/11/2022, 3:47 AM
Or if you can point me to documentation somewhere, I'll dig it myself
a

Ankit Nayan

08/11/2022, 4:32 AM
@Srikanth Chekuri Is this part of opentelemetry semantics? If yes, then we would have a generic env variable that should work across all languages and frameworks
s

Srikanth Chekuri

08/11/2022, 4:39 AM
No, it's not part of semantics. Semantics part is limited to just the quality of telemetry data.
This is the official list of env that should be supported by all SDKs. Since the instrumentation is still early and not streamlined they have flexibility to make their own env as mentioned here.