Open bernd opened 1 year ago
@bernd wondering about our Integration Tests and org.graylog.testing.graylognode.NodeContainerFactory
? Do we have to fix these, too?
@bernd wondering about our Integration Tests and
org.graylog.testing.graylognode.NodeContainerFactory
? Do we have to fix these, too?
@janheise
The telemetry only affects the frontend, as far as I know. The NodeContainerFactory
is already disabling versionchecks via the GRAYLOG_VERSIONCHECKS
environment variable.
@bernd at least for the reporting IT tests, we build and start the frontend, too.
@bernd at least for the reporting IT tests, we build and start the frontend, too.
@janheise Ah okay. I think we have an ongoing issue to disable telemetry for reporting in 5.1?
Expected Behavior
The telemetry reporting should be disabled when the Graylog server runs in local mode. (
--local
)Decision May 25th: Instead of completely disabling telemetry, we will configure it as follows:
local mode -> disable telemetry by default
smd.dev -> send events to Posthog
Development
projectPosthog Development project key:
phc_N86WWkaKgfoywB57IFSbZNWCp1fsQ131yqMXMJRByqq
public release -> send events to Posthoh
Production
projectPosthog Production project key:
phc_t3lgBB66QsPW4HEfiGopO14um4XGNtBcefEKYWelWda
Tasks
--local
flag is used (equivalent totelemetry_enabled = false
)DEVELOPMENT
environment variable is set and not value"false"
(equivalent totelemetry_enabled = false
) see IsDevelopmentServerProvidertelemetry_dev_api_key
config setting and set it to the PostHog dev key by default-SNAPSHOT
suffix)telemetry_api_key
valuetelemetry_dev_api_key
Current Behavior
The telemetry reporting is enabled even when Graylog is running in local mode.
Context
We run test and development setups in local mode. Submitting telemetry data for test and dev setups would produce lots of noise in the analysis of user behaviour in public environments .
Your Environment