@patrickmuff@InfluxDB The alerting capabilities that the python processing engine (PPE) offers are more complete and vast than those of v2. We're also working on creating a UI for the PPE. Currently you can also check out this fun hackathon PPE workshop: https://t.co/djJ1qdfH60
@_BennyOtt_ Data corruption issues can be complex and difficult to resolve. This can happen due to many things like unexpected shutdowns, hardware issues, disk failures, concurrency issues etc. Have you tried: checking influxdb logs? backing up the rest of your data? Using influxd inspect?
@the123saurav InfluxDB 3.0 is even better at point lookups. The rewrite of the storage engine solves long requested performance issues around returning things like global values and point lookups. Learn more here: https://t.co/wGKfXPKQ08
@AlfonsoGarijo@InfluxDB The new UI will have a new data explorer as well but itll only be available to 3.0 instances. But ure correct, that explorer isn’t complete. Please create a feature request here: https://t.co/bG3JscQe43
With all of the features ud like to see and mention ud want to give feedback
@r3dragon@InfluxDB Hello! You can use the execd input plugin if you're looking to pull from NMEA or any source where there isn't an existing input plugin. If you're looking to contribute and have a question please create an issue on the telegraf repo to get assistance there.
@buzziinga@InfluxDB Hello can you please ask your question https://t.co/J2mICYoBrV or https://t.co/bHPy39s4BG and include your telegraf config file? And any errors you're experiencing?
Thank you!
@artifrex@InfluxDB Hello :) Unfortunately we don't offer much support on 1.x since we're on 3.x. These issues might be useful to you though: https://t.co/Dfwygq7R7Z
https://t.co/5Cvz42HQtd
Join Influxer @AnaisDotis for a session about the basics of #SQL data querying with #InfluxDB.
You'll learn how to query InfluxDB with SQL and additional more complicated query structure.
Coming up on April 6 📅
▶ https://t.co/dLakJYlEtH