[ https://issues.apache.org/jira/browse/CASSANDRA-18538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724337#comment-17724337 ]
Ariel Weisberg commented on CASSANDRA-18538: -------------------------------------------- Another way to disable it that works even if someone changes Cassandra's configuration is to put it in a static initializer block. So for example maybe in `DatabaseDescriptor`, `FullQueryLogTool`, `BinLog`, and `AuditLogViewer`. Also to record context, It looks like we actually never released a version that phones home because https://github.com/apache/cassandra/blob/trunk/.build/parent-pom-template.xml#LL708C1-L709C1 excludes the dependency for chronicle-analytics It was added in https://github.com/apache/cassandra/commit/cf39d031279620eb5684ad384dff72f7325104cd#diff-766797f233c18114f9499750c[…]ea50283850619c01bd173132021R585 before 4.0 was released. So we have never released with chronicle phoning home. I only noticed that it has this feature because I was upgrading and changing how we included the dependency and that brought in the analytics library. > Disable chronicle analytics > --------------------------- > > Key: CASSANDRA-18538 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18538 > Project: Cassandra > Issue Type: Bug > Components: Dependencies > Reporter: Brandon Williams > Assignee: Brandon Williams > Priority: Normal > Fix For: 4.0.x, 4.1.x, 5.x > > > At least chronicle-queue phones home to google analytics: > https://github.com/OpenHFT/Chronicle-Queue/blob/chronicle-queue-5.20.116/DISCLAIMER.adoc > but we can disable all chronicle analytics with a single flag: > -Dchronicle.analytics.disable=true -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org