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

Socket Connection Report #12

Open
larrymason opened this issue Mar 16, 2016 · 3 comments
Open

Socket Connection Report #12

larrymason opened this issue Mar 16, 2016 · 3 comments

Comments

@larrymason
Copy link
Contributor

We now capture socket connection information in the database. We capture connections id, the client-ip address, start time and end time. So we can have a report that shows unique IP connections, by day and how long the user stayed connected. We need a report format that could be added to the stats page.

@larrymason
Copy link
Contributor Author

this issue may have been overtaken by events, we have added Google Analytics which may give us everything we need to know... this method can eat up the database after a while also, so may remove soon

@huberf
Copy link
Member

huberf commented Mar 26, 2016

You can export all the database information regularly and then delete the copy in the cloud. This could be effective for preventing the space from being consumed in the DB while we keep this method in use.

@granteous
Copy link
Collaborator

The mongodb has been set up on Simple Helix and is capturing the same information mentioned above by @larrymason. Once we get the production environment set up for the the trolley tracking app on simple helix (along with CI) I will then set up the mongodb to capture data in the production setting instead of dev.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants