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.

Sign up for GitHub

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

Jump to bottom

Web Analytics: Research and Planning #756

Closed
3 tasks done
chouseknecht opened this issue Jun 29, 2018 · 0 comments
Closed
3 tasks done

Web Analytics: Research and Planning #756

chouseknecht opened this issue Jun 29, 2018 · 0 comments
Assignees
@mkrizek
Labels
area/backend priority/high type/enhancement
Milestone
3.1 Sprint 1

Comments

@chouseknecht
Copy link
Contributor

chouseknecht commented Jun 29, 2018 •
edited by newswangerd
Loading

Research and create a plan that answers the following:

  • How to extract HTTP request information from the Galaxy backend (i.e. Django views) in order capture data outlined on the 3.1 roadmap.
  • Where and how to store time series data coming from Galaxy. Is InfluxDB on AWS the right solution? Insights has their own InfluxDB stack, and they have offered to share it. Is that viable? Discuss with the Insights team to determine the pros and cons of each. Is there an alternative on AWS that we should consider?
  • How to aggregate and make time series data available for consumption by Galaxy backend
  • How to surface aggregated time series data in the Galaxy API

We can close this issue when:

  • Plan is documented and presented to the team
  • @tima, @cutwater, and @chouseknecht have approved the plan
  • Plan is organized into sprints and issues
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mkrizek mkrizek

Labels
area/backend priority/high type/enhancement
Projects
None yet
Milestone
3.1 Sprint 1
Development

No branches or pull requests
3 participants
@mkrizek @chouseknecht @newswangerd