-
Notifications
You must be signed in to change notification settings - Fork 68
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
Tracking of not delivered message #64
Labels
enhancement
New feature or request
Comments
Sound reasonable. It is not that easy to make proper tracking because of the retries and so on. So I am not sure if It can be solved in an easy way with APM as you could have 3 retries and 1 success event, leading to wrong interpretations. Perhaps we just have to talk about this. If it is a on a per-user base we can just query the notifications. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey,
I was wondering if it's possible to get more insights in notification confirmation.
In our current push system it's sometimes possible that a customers' push token gets invalid but for any reason the mobile app was not uploading a new one. So new messages can't be pushed to the customer.
With notifo and the confirmation handling it should be possible to get insights in how many notifications are not handled for a specific user. With this information we could investigate if there is an issue in uploading the tokens or user disabled push or something else. Maybe it would be also possible to user alerts for higher amounts of not confirmed messages over a specific time. But I guess this could be handled by an external tool like new relic if we have this data.
The text was updated successfully, but these errors were encountered: