<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Telegraf on Techetio</title><link>https://techetio.com/tag/telegraf/</link><description>Recent content in Telegraf on Techetio</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 29 Nov 2021 01:32:28 +0000</lastBuildDate><atom:link href="https://techetio.com/tag/telegraf/index.xml" rel="self" type="application/rss+xml"/><item><title>InfluxDB V2: Using The V1 API For V1 Dependent Applications</title><link>https://techetio.com/2021/11/29/influxdb-v2-using-the-v1-api-for-v1-dependent-applications/</link><pubDate>Mon, 29 Nov 2021 01:32:28 +0000</pubDate><guid>https://techetio.com/2021/11/29/influxdb-v2-using-the-v1-api-for-v1-dependent-applications/</guid><description>&lt;p&gt;With the expanded feature set that InfluxDB V2 offers, many want to upgrade their existing V1 InfluxDB installations. The issue is that there are a lot of incompatibilities between V1 and V2. Any of your systems writing to InfluxDB, like Telegraf, will need to be updated to use the new influxdb_v2 plugin, since this new version comes with token based authentication instead of user based authentication. The query language is also different in V2, which spells trouble if you have something like Grafana set up. Even the intern doesn&amp;rsquo;t want to rewrite every panel in every dashboard to use the Flux language instead of InfluxQL.&lt;/p&gt;</description></item></channel></rss>