Issue Summary

Jira have outgoing http connections even though disabled Analytics

Steps to Reproduce

1. Jira Administration > System > Analytics Disabled analytics
2. Restart Jira and see outgoing connection through forward proxy or debug outgoing connections

   172.20.0.5 - proxyuser [05/Dec/2019:05:13:11 +0000] "CONNECT btf-analytics.s3.dualstack.us-east-1.amazonaws.com:443 HTTP/1.1" 200 - "-" "Apache-HttpClient/4.5.5 (Java/1.8.0_232)"
   ...
   172.20.0.5 - proxyuser [05/Dec/2019:06:13:14 +0000] "CONNECT server-notifications.atlassian.com:443 HTTP/1.1" 200 - "-" "Apache-HttpClient/4.5.5 (Java/1.8.0_232)"
   172.20.0.5 - proxyuser [05/Dec/2019:06:13:14 +0000] "CONNECT server-notifications.atlassian.com:443 HTTP/1.1" 200 - "-" "Apache-HttpClient/4.5.5 (Java/1.8.0_232)"
   

Expected Results

There is no outgoing connection related analytics if it's disabled.

Actual Results

• Every 6 hours, Jira sent request to server-notifications.atlassian.com to get latest news from atlassian.

  172.20.0.5 - proxyuser [05/Dec/2019:06:13:14 +0000] "CONNECT server-notifications.atlassian.com:443 HTTP/1.1" 200 - "-" "Apache-HttpClient/4.5.5 (Java/1.8.0_232)"
  172.20.0.5 - proxyuser [05/Dec/2019:06:13:14 +0000] "CONNECT server-notifications.atlassian.com:443 HTTP/1.1" 200 - "-" "Apache-HttpClient/4.5.5 (Java/1.8.0_232)"
  

  clusteredjob table

  id     job_id                                       job_runner_key                               sched_type  interval_millis  first_run      cron_expression  time_zone  next_run       version  parameters  
  -----  -------------------------------------------  -------------------------------------------  ----------  ---------------  -------------  ---------------  ---------  -------------  -------  ----------  
  18514  com.atlassian.whisper.plugin.fetch.FetchJob  com.atlassian.whisper.plugin.fetch.FetchJob  I           21600000         1575514489169  (null)           (null)     1575536715200  2        (null)      
  

• Jira sent request to btf-analytics.s3.dualstack.us-east-1.amazonaws.com when start Jira application to get hash code that is used for analysis

  172.20.0.5 - proxyuser [05/Dec/2019:05:13:11 +0000] "CONNECT btf-analytics.s3.dualstack.us-east-1.amazonaws.com:443 HTTP/1.1" 200 - "-" "Apache-HttpClient/4.5.5 (Java/1.8.0_232)"
  

• In another scenario for Jira 10.3.2 when Analytics is DISABLED and OUTGOING connectivity is restricted, Analytics spams atlassian-jira.log with 1000’s of lines when Jira issue is accessed.

  2025-02-04 07:20:23,260+0000 analyticsEventProcessor:thread-1 ERROR someusername     [c.a.a.client.pipeline.DefaultAnalyticsPipeline] Failed to send analytics event com.atlassian.analytics.api.events.MauEvent@d987dbec
  com.atlassian.cache.CacheException: io.atlassian.util.concurrent.LazyReference$InitializationException: software.amazon
  .awssdk.core.exception.SdkClientException: Unable to execute HTTP request: Connect to btf-analytics.s3.dualstack.us-eas
  t-1.amazonaws.com:443 [btf-analytics.s3.dualstack.us-east-1.amazonaws.com/XX.XX.XX.XX, btf-analytics.s3.dualstack.us-
  east-1.amazonaws.com/XX.XX.XX.XX, btf-analytics.s3.dualstack.us-east-1.amazonaws.com/XX.XX.XX.XX, btf-analytics.s3.
  dualstack.us-east-1.amazonaws.com/XX.XX.XX.XX, btf-analytics.s3.dualstack.us-east-1.amazonaws.com/XX.XX.XX.XX, btf
  -analytics.s3.dualstack.us-east-1.amazonaws.com/XX.XX.XX.XX, btf-analytics.s3.dualstack.us-east-1.amazonaws.com/XX.XX.XX.XX, btf-analytics.s3.dualstack.us-east-1.amazonaws.com/XX.XX.XX.XX,..... failed: Connect timed out
          at com.atlassian.cache.ehcache.DelegatingCache.get(DelegatingCache.java:114)
          at com.atlassian.cache.impl.metrics.InstrumentedCache.get(InstrumentedCache.java:72)
          at com.atlassian.jira.cache.stats.CacheWithStats.get(CacheWithStats.java:46)
          at com.atlassian.analytics.client.pipeline.serialize.properties.extractors.mau.MauService.hashEmailPropertyForM
  auEvent(MauService.java:48)
          at com.atlassian.analytics.client.pipeline.serialize.properties.extractors.mau.MauAwarePropertyExtractor.getEve
  ntPropertiesWithHashedEmail(MauAwarePropertyExtractor.java:20)
  -----
  ----- 

Workaround

If you don't have Jira Service Management installed you can disable Analytics Client Plugin and Atlassian Notifications Plugin from Jira Administration > Add-ons > Manage add-ons > System add-ons