Varken Using Influx1 as a Proxy to Influxdb2/Influxdb3

[cafetera]

1. ### Install Telegraf (if not already installed)
   • Confirm it's running: systemctl status telegraf

2. Edit Telegraf Config (/etc/telegraf/telegraf.conf)
   Add the HTTP Listener Input:

[[inputs.http_listener_v2]]
service_address = ":8186"
path = "/write"
methods = ["POST"]
data_format = "influx"

Add the InfluxDB 2.x or 3.x Output:

Influxdbv2

[[outputs.influxdb_v2]]
urls = ["http://p Address:Port"]
token = "YOUR_INFLUXDB_TOKEN"
organization = "YOUR_ORG"
bucket = "YOUR_BUCKET"
Then restart Telegraf:
sudo systemctl restart telegraf

Influxdbv3

[[outputs.influxdb_v2]]
urls = ["http://Ip Address:Port "]
token = "apiv3_......"
organization = "your_org".####need Ignored ######
bucket = "your_bucket"

3. Configure Varken to Write to Telegraf
   Edit your Varken config.ini: change port from 8086 to 8186

[INFLUXDB]
hostname = 127.0.0.1
port = 8186
ssl = False
verify_ssl = False
db = varken ; Required by client, ignored by Telegraf
user = dummy ; Also ignored
password = dummy

4. Patch Varken's dbmanager.py
   Since Varken checks for a real InfluxDB server on startup (e.g., ping(), get_list_database()), edit the file to skip those checks.
   Edit: /opt/Varken/varken/dbmanager.py
   Replaced original init() with this:

def init(self, server):
self.server = server
self.logger = getLogger()

if self.server.url == "influxdb.domain.tld":
    self.logger.critical("You have not configured your varken.ini. Please read the Wiki.")
    exit(1)

self.influx = InfluxDBClient(
    host=self.server.url,
    port=self.server.port,
    username=self.server.username,
    password=self.server.password,
    ssl=self.server.ssl,
    database="varken",
    verify_ssl=self.server.verify_ssl,
    timeout=10,
)

self.logger.info(
    "Telegraf passthrough mode enabled — skipping InfluxDB ping and database/retention‑policy setup."
)

🔁 This allows Varken to start cleanly and write data to Telegraf as if it were InfluxDB 1.x.

5. Restart Varken
   Depending on how you run Varken:
   sudo systemctl restart varken

or

docker restart varken

Result
• No changes needed to Varken's core logic
• InfluxDB 2.x or 3x receives all metrics
• Grafana dashboards using the InfluxDB 2.x or 3.x bucket work as expected