You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
lobsterkatie
changed the title
Port DD interface from sentry to seer?
Figure out DD usage in Seer
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
toincr
.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.
The text was updated successfully, but these errors were encountered: