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

Figure out DD usage in Seer #1660

Open
lobsterkatie opened this issue Dec 18, 2024 · 0 comments
Open

Figure out DD usage in Seer #1660

lobsterkatie opened this issue Dec 18, 2024 · 0 comments

Comments

@lobsterkatie
Copy link
Member

lobsterkatie commented Dec 18, 2024

Tillman has confirmed with ops that the DD agents/SDK/whatever are active for Seer, so now we have to decide how we want to interact with them.

Option 1: Use them directly (see how we use the self.stats object in the file linked below for examples).

Option 2: Port the wrappers we have in sentry over to Seer. (They are here.) Mostly what they seem to do is add in a bunch of tags automatically (we'd have to see where it's actually initialized to figure out exactly what, but I assume it's things like region, hostname, etc.). They also sub in timer for distribution for some reason, and change the API for incrementing from increment to incr.

So it's worth figuring out if we want those tags and if we want the timer/distribution sub to match the data that's flowing from sentry, or if we don't care about any of that, in which case we can just port the initialization (maybe already done, if ops is saying stuff is running?) and use DD directly.

Note that this task has increased in priority now that we're working on getting AI grouping running in ST, since we can't redash into ST instances and instead have to rely solely on DD.

@lobsterkatie lobsterkatie changed the title Port DD interface from sentry to seer? Figure out DD usage in Seer Dec 18, 2024
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

No branches or pull requests

1 participant