-
Bug
-
Resolution: Fixed
-
Low
-
None
Currently, even if analytics has been disabled and/or the privacy policy update has not been acknowledged, Atlassian Analytics will still attempt to call out to S3 to download the most up-to-date blacklist & whitelist for Stash.
This does not involve sending out any data from the instance, just reading some flat lists of events that we do or do not want to collect (which are completely anonymous).
However, it makes sense to simply not download these at all if the user has opted to disable analytics, or has not yet acknowledged the privacy policy update.
Sample message in the log:
2014-09-23 17:06:07,569 WARN [localScheduler_Worker-1] c.a.a.client.s3.AnalyticsS3Client Couldn't download the remote list file config/allowedwords.dict, detailed message: Unable to execute HTTP request: Connect to btf-analytics.s3.amazonaws.com:443 timed out
Form Name |
---|
[BSERV-5280] Analytics tries to make downloads from contacts btf-analytics.s3.amazonaws.com although switched off or privacy policy accepted
Workflow | Original: Stash Workflow - Restricted [ 1446757 ] | New: JAC Bug Workflow v3 [ 3134672 ] |
Workflow | Original: Stash Workflow [ 730735 ] | New: Stash Workflow - Restricted [ 1446757 ] |
Labels | Original: da-missed-use-case | New: da-missed-use-case ph-production |
Fix Version/s | New: 3.4.0 [ 45691 ] | |
Fix Version/s | New: 3.3.1 [ 45700 ] | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Remote Link | New: This issue links to "Page (Extranet)" [ 82663 ] |
Remote Link | New: This issue links to "Page (Extranet)" [ 81607 ] |
Labels | New: da-missed-use-case |
Status | Original: Needs Triage [ 10030 ] | New: Open [ 1 ] |
Component/s | New: Analytics [ 30392 ] |
Description |
Original:
Currently, even if analytics has been disabled and/or the privacy policy update has not been acknowledged, Atlassian Analytics will still attempt to call out to S3 to download the most up-to-date blacklist & whitelist for JIRA.
This *does not* involve sending out any data from the instance, just reading some flat lists of events that we do or do not want to collect (which are completely anonymous). However, it makes sense to simply not download these at all if the user has opted to disable analytics, or has not yet acknowledged the privacy policy update. Sample message in the log: {code} 2014-09-23 17:06:07,569 WARN [localScheduler_Worker-1] c.a.a.client.s3.AnalyticsS3Client Couldn't download the remote list file config/allowedwords.dict, detailed message: Unable to execute HTTP request: Connect to btf-analytics.s3.amazonaws.com:443 timed out {code} |
New:
Currently, even if analytics has been disabled and/or the privacy policy update has not been acknowledged, Atlassian Analytics will still attempt to call out to S3 to download the most up-to-date blacklist & whitelist for Stash.
This *does not* involve sending out any data from the instance, just reading some flat lists of events that we do or do not want to collect (which are completely anonymous). However, it makes sense to simply not download these at all if the user has opted to disable analytics, or has not yet acknowledged the privacy policy update. Sample message in the log: {code} 2014-09-23 17:06:07,569 WARN [localScheduler_Worker-1] c.a.a.client.s3.AnalyticsS3Client Couldn't download the remote list file config/allowedwords.dict, detailed message: Unable to execute HTTP request: Connect to btf-analytics.s3.amazonaws.com:443 timed out {code} |