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

NSE not reporting UTD analytics to posthog? #2889

Open
BillCarsonFr opened this issue May 30, 2024 · 2 comments
Open

NSE not reporting UTD analytics to posthog? #2889

BillCarsonFr opened this issue May 30, 2024 · 2 comments
Labels
A-Analytics A-E2EE Encryption A-Notifications question Further information is requested T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements

Comments

@BillCarsonFr
Copy link
Member

It looks like the NSE target is not depending on posthog?

Does it means that if a decryption error occurs while doing a NSE sync it won't be reported to posthog?
If true, what would be effort to add reporting for UTD in NSE?

@BillCarsonFr BillCarsonFr added the question Further information is requested label May 30, 2024
@stefanceriu
Copy link
Member

Does it means that if a decryption error occurs while doing a NSE sync it won't be reported to posthog?

Of course, there's nothing automatically happening, nobody's pushing that event through from the NSE

If true, what would be effort to add reporting for UTD in NSE?

Couple of days if everything goes well

@stefanceriu
Copy link
Member

More importantly though, the withUtdHook is defined on SyncServiceBuilder which is not available/used in the NSE

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Analytics A-E2EE Encryption A-Notifications question Further information is requested T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements
Projects
None yet
Development

No branches or pull requests

3 participants