#InfluxDB

Processing Plugins | InfluxDB 3 Processing Engine | InfluxData Browse the official plugin directory for the InfluxDB 3 Processing Engine. Filter by trigger type and get started in minutes.

2 days ago

NEW: Introducing the Plugin Library for the #InfluxDB 3 Processing Engine lets you extend custom Python plugins for anomaly detection, forecasting, downsampling, alerting, and more—running directly inside the database where your data lives.
Explore the plugins ↓ https://bit.ly/4sHXUpl

0 0 0 0

2 days ago

Struggling with sensor ingestion, schema design, or cardinality issues in your IoT stack? Join #InfluxDB experts Ian Clark, @suyashcjoshi, and @InfluxCole for a live open Q&A on March 17th.

Ask us anything about edge ingestion, dashboards, retention strategies, and more. https://bit.ly/3Nhydg9

0 0 0 0

InfluxData InfluxData provides the leading time series platform to instrument, observe, learn and automate any system, application and business process across a variety of use cases.

3 days ago

The latest update for #InfluxDB includes "When Your Plant Talks Back: Conversational #AI with InfluxDB 3" and "From Reactive to Predictive: Preserving BESS Uptime at Scale".

#monitoring #devops #timeseries https://opsmtrs.com/2W5CAx0

0 0 0 0

3 days ago

Tomorrow! Get hands-on experience building a scalable data pipeline for IoT applications with MQTT and #InfluxDB.

Sign up now to join the virtual 8AM PT | 3PM GMT training with Senior Developer Advocate Cole Bowden happening tomorrow: https://bit.ly/3MT5xtR

0 0 0 0

IoT Office Hours with InfluxDB 3 Got questions about your IoT data stack? We've got answers. Struggling to get sensor data flowing reliably from your edge devices? Not sure how to structure your schema for thousands of Raspberry Pi ...

6 days ago

Got questions about your IoT data stack? We’ve got answers. Join #InfluxDB for an open Q&A session for anyone working with IoT data and InfluxDB. Come with your challenges, and we’ll come with answers.

Sign up now: https://bit.ly/3Nhydg9

0 0 0 0

Dizzy

@bubblegumyeti.mastodon.social.ap.brid.gy

1 week ago

To test a game with a lot of emergent gameplay, I have several debug UI (and logging) modes. I was thinking of plugging in some realtime system (#Grafana? #Influxdb) but I think that is overkill.

#GameDevelopment #raylib

2 0 0 0

InfluxDB University Master time series data on InfluxData platform through videos, workshops and live training to get started with InfluxDB, Flux and Telegraf.

1 week ago

#InfluxDB University offers free courses to help developers get up to speed with time series data!

We've got courses covering:

➡️ InfluxDB 3 Essentials
➡️ Telegraf Basics
➡️ Data Collection with Telegraf
...and lots more!

https://bit.ly/4mBD5sW

0 0 0 0

1 week ago

#InfluxDB 3's Python Processing Engine lets you run scripts directly in the database—no external tools needed!

Filter, transform, and automate on time series data as it arrives.

Cut tool sprawl, speed up workflows, and act faster. 📊⚡
https://bit.ly/4lVKgLN

0 0 0 0

InfluxData InfluxData provides the leading time series platform to instrument, observe, learn and automate any system, application and business process across a variety of use cases.

1 week ago

The latest update for #InfluxDB includes "From Reactive to Predictive: Preserving BESS Uptime at Scale" and "A Practical Guide to SCADA Security".

#monitoring #devops #timeseries https://opsmtrs.com/2W5CAx0

0 0 0 0

1 week ago

Get the #InfluxDB downsampling plugin in under 40 seconds. ⏱️

Watch how. 👇

0 0 0 0

Satellite Telemetry Monitoring with InfluxDB 3 In this session, Sales Engineer Ian Clark walks through how InfluxDB 3 can be used to ingest, store, and query satellite telemetry without fighting scale, latency, or data shape.We will focus on...

1 week ago

Join tomorrow’s webinar on satellite telemetry monitoring with #InfluxDB 3 at 8 AM PT | 4PM GMT. Discover how InfluxDB 3 handles high-frequency sensor data, large and evolving tag sets, and long retention periods common in aerospace systems.

Register now: https://bit.ly/4kxsqiT

0 0 0 0

How We Switched to Time-Series Telemetry for SaaS Apps Behind the scenes at InfluxData, which turned to its own in-house security monitoring platform, DiSCO, to protect its supply chain.

1 week ago

Discover why #InfluxDB engineers decided to use our own time series telemetry to power our in-house security monitoring platform, DiSCO. (Spoiler: DiSCO provides top-notch security observability to prevent breaches.) https://bit.ly/4p7AMiK via @DarkReading

0 0 0 0

InfluxData InfluxData provides the leading time series platform to instrument, observe, learn and automate any system, application and business process across a variety of use cases.

1 week ago

The latest update for #InfluxDB includes "A Practical Guide to SCADA Security" and "The 'Now' Problem: Why BESS Operations Demand Last Value Caching".

#monitoring #devops #timeseries https://opsmtrs.com/2W5CAx0

0 0 0 0

1 week ago

Join Thursday’s webinar on satellite telemetry monitoring with #InfluxDB 3. Gain practical knowledge for monitoring spacecraft health, analyzing trends across fleets, and supporting both live operations and retrospective analysis – using a single data platform.

Sign up today: https://bit.ly/4kxsqiT

0 0 0 0

1 week ago

Python devs: Build custom real-time dashboards with Streamlit and #InfluxDB 3 Core!

Skip the constraints of traditional viz tools and query time series data directly.

Perfect for financial analytics, IoT, or observability. ↴ https://bit.ly/4ncK6Qq

1 0 0 0

YouTube Share your videos with friends, family, and the world

1 week ago

Telegraf collects, processes, and routes data from sensors, APIs, and systems with a plugin-based architecture.

Deploy it anywhere—IoT devices, edge gateways, VMs—and build custom pipelines that transform raw data into actionable insights for #InfluxDB. https://bit.ly/4czEmyL

0 0 0 0

YouTube Share your videos with friends, family, and the world

1 week ago

Plant monitoring with IoT sensors generates 500K data points daily.

#InfluxDB handles the ingestion, downsampling, and threshold alerts to keep it all running efficiently. See how. 👇 https://bit.ly/3P3EQmF

0 0 0 0

Building Real-Time SMS, WhatsApp and Slack Alerts Learn how to create a comprehensive alerting system across three critical channels using InfluxDB 3's new Python processing engine.

2 weeks ago

Immediate alerts matter when systems fail.

This guide shows how to build multichannel monitoring with SMS, WhatsApp, and Slack using #InfluxDB 3's embedded Python engine.

No external orchestration needed! bit.ly/4kbGTzg via @thenewstack

1 0 0 0

Getting started with the Node.js client library in InfluxDB If you use Node.js, then the Node.js client library allows you to interact with the InfluxDB platform quickly, using a familiar language. Here, Zoe Steinkamp discusses some of the features of the Node.js client library to help you get started building a...

2 weeks ago

The Node.js client library allows you to interact with the #InfluxDB platform quickly, using a familiar language.

This quick video outlines some of the features of the Node.js client library to help you get started building awesome applications with InfluxDB even faster. ⚡️

https://bit.ly/4kXbgeK

0 0 0 0

InfluxData InfluxData provides the leading time series platform to instrument, observe, learn and automate any system, application and business process across a variety of use cases.

2 weeks ago

The latest update for #InfluxDB includes "The 'Now' Problem: Why BESS Operations Demand Last Value Caching" and "What Is Predictive #Analytics? A Complete Guide for 2026".

#monitoring #devops #timeseries https://opsmtrs.com/2W5CAx0

0 0 0 0

2 weeks ago

#InfluxDB 3 Core is an open source, recent-data engine built for speed.

Sub-10ms queries, in-memory processing, and real-time visibility for the use cases that demand it.

Watch the video to see what's possible!

0 0 0 0

InfluxData InfluxData provides the leading time series platform to instrument, observe, learn and automate any system, application and business process across a variety of use cases.

2 weeks ago

The latest update for #InfluxDB includes "What Is Predictive #Analytics? A Complete Guide for 2026" and "From Legacy Data Historians to a Modern, Open Industrial Data Stack".

#monitoring #devops #timeseries https://opsmtrs.com/2W5CAx0

1 0 0 0

InfluxData InfluxData provides the leading time series platform to instrument, observe, learn and automate any system, application and business process across a variety of use cases.

3 weeks ago

The latest update for #InfluxDB includes "From Legacy Data Historians to a Modern, Open Industrial Data Stack" and "How to Use Pandas Time Index: A Tutorial with Examples".

#monitoring #devops #timeseries https://opsmtrs.com/2W5CAx0

0 0 0 0

Olivier Mehani

@shtrom.piaille.fr.ap.brid.gy

3 weeks ago

HomeAssistant's history graph widget. The top part shows categorical data, with multiple coloured blocks along the timeline for “Sound meter ann[otation]”. The bottom part shows a single continuous value from sensor “Bt-Proxy-6Fb14C UNI-T Mini Sound Meter UT353BT”. The values are between 40 and 60 dBA, with a single data point spike to 90.

#homeAssistant / #homeLab question

I store some HA historical values into InfluxDB. The app has a Telegraf frontend.

One sensor collect continuous data, while I have added a text input_helper to collect manual annotations about this data.

Is there a way in […]

[Original post on piaille.fr]

0 0 0 0

bentasker.co.uk Feed

@mastodon.bentasker.co.uk

1 month ago

Importing FX Chronograph Readings Into InfluxDB I use an FX Pocket Chronograph V2 to help monitor the power output of my air rifles. It's a small radar based device which hangs below the barrel and links to my phone to write readings into the FX Radar app. Although obviously quite useful while shooting, I also wanted to be able to monitor behaviour over time. For example, if the rifle's output trends down, it might suggest worn seals, whereas trending up could raise _significant_ legal concerns. So, like most other things that I monitor, I wanted to get the data into InfluxDB so that I could visualise and alert using Grafana. This post describes the script that I wrote to process FX Radar exports and ingest them into InfluxDB. Although I use this for airguns, the chronograph apparently works for rim-fire and even archery too: this should therefore also work for those sports. * * * ### The FX Radar App This isn't an advert and (sadly) FX haven't given me anything but this section is probably going to sound a little as if they have. I want to give **massive** kudos to FX for the Radar app. Although it's interface could use a little polish, the app is _completely_ local: there's no account registration required, no ads and no SaaS subscription. It's what it needs to be: a local only app, which connects to the Chronograph using bluetooth to record ballistic data into a locally stored database1. In a world driven by monetisation, I cannot overstate _just how welcome_ it is that FX have chosen to focus on having the app do what users need rather than wedging in online functionality (or worse... AI). * * * ### Exporting From FX Radar Unfortunately, there isn't a way to schedule automatic exports. But, it's quick and easy to do manually, so doing so after a shooting session isn't too inconvenient: * Open FX Radar * Tap the Shot string view (middle Icon at the bottom) * Tap `All Saved Strings` * Tap `Share` * Choose somewhere to save it (I use Nextcloud, but more on this below) The export file is essentially an annotated CSV: CP2, BSA Storm Bullet:BSA Storm Weight: 15.29 gr Weather: 9.0°C 19.9mph light rain 998hPa/mbar 29.47inHg 85% Shot count: 37 Low: 315 Hi: 552 Avg: 492 STD Dev: 89 Spread: 237 2/7/26 11:32:13,374,FPS,4.8,FT Lbs, 2/7/26 11:32:18,375,FPS,4.8,FT Lbs, 2/7/26 11:32:24,355,FPS,4.3,FT Lbs, 2/7/26 11:32:30,358,FPS,4.4,FT Lbs, 2/7/26 11:32:35,345,FPS,4.0,FT Lbs, .. etc .. My utility iterates through the lines, generating Line Protocol to feed into InfluxDB, providing metrics on individual shots as well as shot strings. * * * ### Using The Utility You'll need a way to get the export file from your phone to the system that the utility runs on. Because I have a Nextcloud instance, I save it straight into there allowing automated runs to fetch and process it. If you've got Nextcloud (or some other WebDAV compatible system), great! Most readers of this doc, though, probably won't have, so we'll ignore that as an option for now. FX Radar allows you to send the file to yourself (via email, or messaging apps etc) - use whatever means suits you best, but ensure that you save the file onto your computer with a `.txt` extension. * * * #### Using `docker-compose` Most readers _probably_ don't have InfluxDB or Grafana, so we'll stand those up and trigger imports manually The utility is designed to be run as a Docker container, so you'll need docker. Download a zip of my repo, or (if you have git), clone it down: git clone ssh://git@codeberg.org/bentasker/fx_radar_to_influxdb.git Change into the directory containing the compose file: cd fx_radar_to_influxdb/examples/docker-compose There's a file called `.env`, you should edit this to change the credentials stored in it. nano .env Start the containers: docker compose up -d This will start InfluxDB v2 and a Grafana instance (preconfigured with my Chronograph dashboard). Grafana can be accessed at http://localhost:3000 using the credentials in `.env`. The compose file also defines, but does not start, the import container. To run an import, copy the FX radar export file to a file named `shots.txt` and then trigger the importer cp /path/to/export.txt ./shots.txt docker compose run --rm fx_radar_importer Once it completes, you should be able to view your shot data in the Grafana dashboard. * * * #### Automated Workflow If you've got Nextcloud (or something supporting WebDAV) you can potentially automate imports. It's assumed that you also already have InfluxDB and Grafana (if not, use the `docker-compose` steps above to set them up). At it's simplest, automation can be achieved by creating a cron job containing a docker invocation: docker run \ --rm \ -e WEBDAV_URL="https://nextcloud.example.com/remote.php/dav" \ -e WEBDAV_PATH="files/foobar/fx_radar_exports" \ -e WEBDAV_USER="user" \ -e WEBDAV_PASS="password" \ -e INFLUXDB_URL="http://192.168.1.5:8086" \ -e INFLUXDB_BUCKET="telegraf" \ -e INFLUXDB_ORG="myorg" \ -e INFLUXDB_TOKEN="aaaabbbbccccdddd==" \ codeberg.org/bentasker/fx_radar_to_influxdb The utility will connect to your WebDAV server and iterate through all `.txt` files it finds at `WEBDAV_PATH`. If you're a bit more nerdy and have a Kubernetes cluster, this can also be configured as a K8S `CronJob`. Create secrets: kubectl create secret generic influxdbv2 \ --from-literal=influxdb_token=<my token> \ --from-literal=influxdb_org=<org> \ --from-literal=influxdb_url=<url> kubectl create secret generic nextcloud \ --from-literal=webdav_user=<user> \ --from-literal=webdav_pass=<password> \ --from-literal=webdav_url=<url> And then define the resource: apiVersion: batch/v1 kind: CronJob metadata: name: fx-radar-to-influxdb spec: schedule: "0 */4 * * *" failedJobsHistoryLimit: 5 successfulJobsHistoryLimit: 5 jobTemplate: spec: template: spec: containers: - name: fx-radar-to-influxdb image: codeberg.org/bentasker/fx_radar_to_influxdb imagePullPolicy: IfNotPresent env: - name: INFLUXDB_BUCKET value: "telegraf" - name: INFLUXDB_MEASUREMENT value: "fx_radar" - name: WEBDAV_PATH value: "files/service_user/fx_radar/" # Don't import shots/strings older than 14 days - name: MAX_DATA_AGE value: "1209600" - name: INFLUXDB_TOKEN valueFrom: secretKeyRef: name: influxdbv2 key: influxdb_token - name: INFLUXDB_ORG valueFrom: secretKeyRef: name: influxdbv2 key: influxdb_org - name: INFLUXDB_URL valueFrom: secretKeyRef: name: influxdbv2 key: influxdb_url - name: WEBDAV_URL valueFrom: secretKeyRef: name: nextcloud key: webdav_url - name: WEBDAV_USER valueFrom: secretKeyRef: name: nextcloud key: webdav_user - name: WEBDAV_PASS valueFrom: secretKeyRef: name: nextcloud key: webdav_pass restartPolicy: OnFailure This will run every 4 hours, processing any files that it finds at the provided path. The variable `MAX_DATA_AGE` tells the script to skip any shots (or string data) that's too old: this prevents the utility from continually re-ingesting old data (which would also cause InfluxDB to run more compactions than it otherwise would). * * * ### Visualisation The code repo includes a Grafana Dashboard Export. A version of this dashboard is also preconfigured in the `docker-compose` Grafana: This displays shot data, separated by gun and pellet type. * * * ### Alerting This is a _slightly_ unusual usecase for alerting: data has to be imported after the fact, so we don't want (or get) realtime alerting2. An alert rule can be created, using the following query from(bucket: "Systemstats") |> range(start: v.timeRangeStart, stop: v.timeRangeStop) |> filter(fn: (r) => r._measurement == "fx_radar") |> filter(fn: (r) => r._field == "energy") |> keep(columns: ["_time", "_value", "_field", "gun", "pellet", "weight"]) |> max() The alert should be set to query the last day of data: Because we're using `max()` in the query, we don't need Grafana to run a reduce: delete box `B` and then set `C` to use `A` as input. Set the threshold to 12 (or, if you'd prefer to err on the side of caution, 11.9) Create an evaluation group to have the query run once daily and set the pending period to 0s. Save the alert. * * * ### Conclusion I'm not really sure how big an overlap there is between airgunners and tech nerds, so there's a very real possibility that this is useful to an audience of one (me!). Still, though, capturing the data in InfluxDB means that, as well as being able to alert on power levels, I can conveniently look at behaviour over time: as seals start to age, I should see a gradual degradation in the stats. Similarly, if power output starts to creep up, I should become aware of it before it risks becoming a legal liability3 Finally, it also means that, if FX ever do decide to enshittify the app, I won't be too bound to it. * * * 1. If you're looking on the filesystem the app uses the name `com.basepaintball.fxblue` ↩ 2. The FX Radar app can provide a sort of realtime alerting - it allows high and low velocity thresholds to be set - this isn't _particularly_ useful for power output, though I've found it extremely useful as an indicator that the air cylinder has dropped below regulator pressure ↩ 3. I also _assume_ that, if the Police were ever to test and claim that they were over the limit, continual good-faith monitoring might be looked upon kindly in a plea of mitigation. ↩

New #Documentation: Importing FX Chronograph Readings Into InfluxDB
Author: Ben Tasker

www.bentasker.co.uk/posts/documentation/shoo...

#fxradar #influxdb #shooting

0 0 0 0

Matze

@matze.kittsteiner.blog.ap.brid.gy

1 month ago

Original post on kittsteiner.blog

I had been playing with Grafana, InfluxDB, Telegraf and Prometheus the last two weeks and can now share my story of what I finally use to replace my Netdata instances and why.

[…]

kittsteiner.blog/blog/2026/migrated-from-... #Ansible #DevOps #Grafana […]

0 0 0 0

InfluxData InfluxData provides the leading time series platform to instrument, observe, learn and automate any system, application and business process across a variety of use cases.

1 month ago

The latest update for #InfluxDB includes "From Legacy Data Historians to a Modern, Open Industrial Data Stack" and "How to Use Pandas Time Index: A Tutorial with Examples".

#monitoring #devops #timeseries https://opsmtrs.com/2W5CAx0

0 0 0 0

InfluxData InfluxData provides the leading time series platform to instrument, observe, learn and automate any system, application and business process across a variety of use cases.

1 month ago

The latest update for #InfluxDB includes "How to Use Pandas Time Index: A Tutorial with Examples" and "How Network Operations Teams Use InfluxDB to Solve Network #Monitoring Gaps".

#devops #timeseries https://opsmtrs.com/2W5CAx0

0 0 0 0