Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: custom spans #2287

Merged
merged 17 commits into from
Nov 27, 2024
Merged

feat: custom spans #2287

merged 17 commits into from
Nov 27, 2024

Conversation

KishenKumarrrrr
Copy link
Contributor

Problem

This PR is a continuation of #2285. After previously removing the logging of the entire record objects, the ELB 502s during callback spikes continued to occur. While trying to debug the issue further, we realised that the existing traces in DD did not contain sufficient information.

In this PR, I manually add custom spans to the callback endpoint that we are interested in so that we can hopefully better understand where the bottlenecks in this endpoint lie.

💡 The newly created spans are still a little wonky. My guess is that this is due to the implementation of this endpoint where there are many overlapping asynchronous operations being executed at the same time.

Before

Screenshot 2024-11-26 at 11 24 16 AM

After (No DB calls in the SS because this is on staging, we will have them on production)

Screenshot 2024-11-26 at 11 24 33 AM

@KishenKumarrrrr KishenKumarrrrr self-assigned this Nov 26, 2024
Copy link
Member

@jia1 jia1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants