Closed jonom closed 1 year ago
I'd have to do some digging, but it doesn't look like Member data is being sent as a tag in Log/SentryLogger::factory()
. Also, (and this may surprise you) I've never known what that question-mark means, especially when all the data is sent and available in the "User" section.
Have you tried hacking the module's defaultTags()
method to include user-data? This is where all the tags are collected and pushed to Sentry. If that works, maybe I'll mod the module. I don't think there was a reason user data wasn't
made a tag, other than that there was already a specific place to set user data alongside tagged data as a Sentry context ala:
$adaptor = (new SentryAdaptor($client))
->setContext('env', $env)
->setContext('tags', $tags)
->setContext('extra', $extra)
->setContext('user', $user);
Looks like the issue is here - the array keys of the user data are incompatible with Sentry\UserDataBag so are added as metadata only when parsed here.
Bingo! I'll open a PR.
This might just be me, but for some reason Sentry isn't connecting the dots on the user information. It's visible as context info, but not as a user tag, which means I can't (easily) see if an issue is affecting multiple users. I couldn't see anything obvious in the module code about why this might happen. There's even a fancy question mark on the user context info 🤷♂️