A complete solution for open data platforms, enterprise data catalogs, data lakes and data management. Open source, mature, fully-featured and production ready.

DataHub

image.png

Screenshot 2023-06-06 at 3.32.17 PM.png

Hi team, we encounter a case when a graphql request that is usually running very fast takes more than 5 min to execute based on opentelemetry traces.

The first screenshot shows the usual scenario for this GraphQL request (less than 10ms to execute); however, for the same GraphQL query, the request can be timed out at 30s (_refer to the second screenshot_). And there’s a long period (&gt; 5 min) of hiatus based on the traces.

Anyone has any idea why this can happen? :bow:

i have challenges to locate where the spans are configured in the code for `/graphql` and `query &lt;operation name&gt;` (in our case, query getSchemaClassification). Those seems not configured via @WithSpan. Any tip on that will be great too

Hi <@U01GCJKA8P9> might be able to provide some insight here