I'm seeing hundreds of requests being made to api.segment.io from Mattermost on a new installation over the course of a day. It would be great to either:
I understand that there are some easy workarounds:
But it would be ideal if this can be controlled natively as part of application logic during setup. (Apologies if this is already possible; I couldn't find any such option in the settings interface or in the config file.)
This seems to be what I was looking for, thanks!
Turns out, as far as I can tell, the environment variables to change this setting (documented nowhere) is MM_LOGSETTINGS_ENABLEDIAGNOSTICS = "false" as well as MM_SERVICESETTINGS_ENABLESECURITYFIXALERT = "false". I haven't tested it.
You can also do the following in a Dockerfile:
FROM mattermost/mattermost-team-edition:latest
RUN sed -i 's#api.segment.io#xx.example.com#gI' /mattermost/bin/mattermost
RUN sed -i 's#securityupdatecheck.mattermost.com#xxxxxxxxxxxxxxxxxxxxxx.example.com#gI' /mattermost/bin/mattermost
That should give you a clean image that doesn't phone home.
@sneak changing the environment variables indeed seems to solve the issue, thanks! Specifically, in /lib/systemd/system/mattermost.service, add:
Environment=MM_LOGSETTINGS_ENABLEDIAGNOSTICS=false
Environment=MM_SERVICESETTINGS_ENABLESECURITYFIXALERT=false
It then seems that mattermost no longer queries segment.io.
Really shameful and unethical that this happens without notifying the user, and that turning it off is not documented clearly anywhere.
Most helpful comment
@sneak changing the environment variables indeed seems to solve the issue, thanks! Specifically, in
/lib/systemd/system/mattermost.service, add:It then seems that mattermost no longer queries
segment.io.