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

Improve Pinpoint notification docs #84

Closed
palpatim opened this issue Nov 2, 2018 · 1 comment
Closed

Improve Pinpoint notification docs #84

palpatim opened this issue Nov 2, 2018 · 1 comment

Comments

@palpatim
Copy link
Member

palpatim commented Nov 2, 2018

From PR #82, @undefobj commented:

I think this is good however one thing I would like to add in the next pass is a "How it works" for the Pinpoint Analytics stuff. For instance in the Kinesis section we talk about why we stream to disk with a PutRecord but we don't talk about the same in Pinpoint. We do talk about managing sessions but we don't really talk about why they're useful aside from "Indicate when and how often users open and close your app" which isn't completely accurate as sessions can be impacted by backgrounding, or another app (like a text message) popping up. Also for both the Pinpoint and Kinesis stuff if we are batching to disk, when does the record actually get sent up to the service? Is it when network connectivity resumes or at another scheduled time?

@mutablealligator
Copy link
Contributor

I am trying summarize the ask from @undefobj here. Add explanation for the following questions:

  1. How does batching work when recordEvent is called? What is the condition that needs to be met for the events to be sent to Pinpoint?

  2. How is session management useful and how does it work?

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

4 participants