influxdata / influxdata/influxdb

Influxdb2 is doing telemetry (phone home) even with `reporting-disabled = true`

Open
#23,236 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
31.7k
Forks
3.7k
Avg merge
13h 37m
Merged PRs (30d)
8

Description

__Steps to reproduce:__

1. Disabling reporting in /etc/influxdb/influxdb.conf : `reporting-disabled = true`
2. Restart the service `systemctl restart influxdb`
4. Seeing opened connection to aws:443 `ss -lapunte | awk '/influx/ && /443/'`

__Expected behavior:__

service not communicate with external aws ip.

__Actual behavior:__
It opens a connection via :443

__Environment info:__

* System info: Linux 5.16.16-200.fc35.x86_64 x86_64
* InfluxDB version: InfluxDB 2.1.0 (git: 435907d68d) build_date: 2021-11-08T20:07:48Z
* Other relevant environment details:

__Config:__
See attached file
[influxdb.md](https://github.com/influxdata/influxdb/files/8364993/influxdb.md)

__Logs:__
`
ss -lapunte | awk '/influx/ && /443/'`

`tcp ESTAB 0 0 192.168.6.233:35390 108.138.217.96:443 users:(("influxd",pid=2852,fd=21)) timer:(keepalive,067ms,0) uid:988 ino:47123 sk:5c cgroup:/system.slice/influxdb.service <->`

__Performance:__

Performance not impacted

Contributor guide

Open the contributing guide

Research direction

Reproduce with reporting-disabled = true in /etc/influxdb/influxdb.conf, restart using systemctl restart influxdb, and check ss -lapunte | awk '/influx/ && /443/'. Trace the telemetry connection path to determine why an external AWS connection remains open. Done means the service no longer communicates externally when reporting is disabled, with a regression test covering the setting.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, rust
Domain
databases, observability
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.