- Nothing yet
- Remove protocol URL in template when enabling tracking (scheme is now provided by
PIWIK_SCHEME
) #289
- [BREAKING] Remove metrics computation with Matomo as a source (cf below) #273
- Replace mongo legacy image in CI #266
- Upgrade test and develop deps #284
Up until this version, metrics were tentatively computed from Matomo for pretty much every object of a udata instance. We found this method to be pretty inaccurate, since Matomo limits the number of records stored to roughly the most visited 1000 for a given "namespace". There's a way around that by using the data from the Live module of Matomo but it's not enabled on our instance for privacy reasons. We also needed to count hits that Matomo could not know of: resources (files) downloads made directly on our server.
Thus, this module now only does three things:
- inject the Matomo tracking code in the templates
- process events for tracking the API usage in Matomo
- process events for tracking some Matomo goals
Metrics computation is now handled by https://github.com/opendatateam/udata-metrics and does not use Matomo as a source.
piwik-update-metrics
piwik-current-metrics
piwik-yesterday-metrics
- Change udata-gouvfr dependency to udata-front following renaming #249
- Ensure compatibility with udata-front and removed goals mechanism #245
- Pin influx docker image version to prevent usign Influx v2 #239
- Add specific query for each model metrics #203
- Remove object's id in error log message in order to have a cleaner message #195
- Changed metrics system #185:
- Metrics are now stored into InfluxDB before being injected in udata's objects
- Udata piwik accesses influxDB throught udata-metrics
- The periodic job
piwik-update-metrics
needs to be scheduled in addition to existing jobs, in order to retrieve the views metrics in udata's objects - The command
update-metrics
was added to trigger the metrics injection manually
- [fix] Do not expect a json response from tracking api #192
- Do not expect a json response from tracking api #190
- Fix JS syntax when subscribing to goals #174
- Independant Matomo site ids for front and api tracking
⚠️ breaking change, you need to setPIWIK_ID_FRONT
andPIWIK_ID_API
in settings (they can be the same) #173
- Improve detect_by_url error handling #171
- Fix bulk handling of unicode URLs #139
- Add
PIWIK_SCHEME
config support #104
- Ensure JS goals handling waits for
uData
object to be present #91
- Advanced search tracking: display results count and categories (datasets, reuses, organizations) #88
- Lower jobs piriority to
low
#90 - Depends on
udata>=1.6.1
- Simpler and more reliable metrics computation #54
- Handle multiple resources for same url #49
- Refactor
counter.handle_downloads
- fix #1421 - Switch to
flask-cli
and endpoint-based commands (requiresudata>=1.3
) #33 - Expose the new
udata.tasks
endpoint #39 - Expose the new
udata.views
endpoint #41 - Add content tracking options in configuration paramaters #42
- Fix version number
- Fix README on pypi
- Fix packaging issue
- Add (automated) tests against a Piwik instance #20
- Handle download count on latest url for (community) resources #30
- Add a timeout to
analyze()
#19
- Add a timeout to
track()
#18
- Fix build and packaging
- First published release