Skip to content

MySQL storm_analytics Update
Compare
Choose a tag to compare
@ATawzer ATawzer released this 30 Apr 20:45
· 92 commits to master since this release
v2.1.0
2a91895
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
  • Adds in a storm_analytics DB into the process for examination and eventually ML. This will require a user to setup both a MongoDB and a MySQL database to process the storm fully. In a future release these will be optional components
  • Playlist History view for monitoring playlist evolution
  • Playlist Info for seeing current information about playlists
  • Run history view for seeing storm runs and their performance
  • Track info view for seeing track information
  • storm_analytics pipeline created via the StormAnalyticsController class, which leverages the logic of the StormViewGenerator class to move and aggregate data from MongoDB to MySQL database for reporting (and ML planned for v2.2.0)
  • analytics_pipeline will now fire after all storm runs are complete if called from Storm
Assets 2
Loading