Telegraf is a very powerful open source plugin-based agent that gathers data from stacks, sensors, and systems and sends it to a database. It collects data from an input and sends it to an output, and gives you the option to transform data with aggregators and processors before it reaches its endpoint.

Streaming time series data from brokers and services that are on-premises or in the cloud to a cloud-based database is a resource-intensive process requiring third-party software and heavy customizations. Today we’re announcing InfluxDB Native Collectors to make it easy for developers to collect, process, and analyze data by subscribing directly to supported message brokers.

SAN FRANCISCO — August 23, 2022 – InfluxData, creator of the leading time series platform InfluxDB, today announced new serverless capabilities to expedite time series data collection, processing, and storage in InfluxDB Cloud. InfluxDB Native Collectors enable developers building with InfluxDB Cloud to subscribe to, process, transform, and store real-time data from messaging and other public and private brokers and queues with a click of a button.

Today we are happy to officially announce that InfluxData has donated a generic object store implementation to the Apache Arrow project. Using this crate, the same code can easily interact with AWS S3, Azure Blob Storage, Google Cloud Storage, local files, memory, and more by a simple runtime configuration change. You can find the latest release on crates.io. We expect this will accelerate the pace of innovation within the Rust ecosystem.

InfluxDB is an open-source time series database. Built to handle enormous volumes of time-stamped data produced from IoT devices to enterprise applications. As data sources for InfluxDB can exist in many different situations and scenarios, providing different ways to get data into InfluxDB is essential. The InfluxDB client libraries are language-specific packages that integrate with the InfluxDB v2 API. These libraries give users a powerful method of sending, querying, and managing InfluxDB.

We love to write and ship code to help developers bring their ideas and projects to life. That’s why we’re constantly working on improving our product to meet developers where they are, to ensure their happiness, and accelerate Time to Awesome. This week, we are covering a featured product release that we think will save you time and effort when onboarding to time series and InfluxDB.

This article was originally published in The New Stack and is reposted here with permission. You may be familiar with live examples of machine learning (ML) and deep learning (DL) technologies, like face recognition, optical character recognition OCR, the Python language translator, and natural language search (NLS). But now, DL and ML are working toward predicting things like the stock market, weather and credit fraud with astounding accuracy.

This article was written by Shane from Infosys. Infosys is a global IT Leader, headquartered in India, with over 200,000 employees and a focus on digital transformation, AI/ML, and Analytics. Our organization faces challenges when working with data to assist with proactive anomaly detection, triaging incidents to accommodate for data and volume growth, and maintaining high availability and SLA’s for a near 100% uptime.

Thanks to Vinay Kumar for being a key contributor to this article. We love to write and ship code to help developers bring their ideas and projects to life. That’s why we’re constantly working on improving our product to meet developers where they are, to ensure their happiness, and accelerate Time to Awesome. This week, we are covering a featured product release that we think will save you time and effort when building with time series, InfluxDB – and specifically – Tasks.

Cloud native and microservice architectures bring many advantages in terms of performance, scalability, and reliability, but one thing they can also bring is complexity. Having requests move between services can make debugging much more challenging and many of the past rules for monitoring applications don’t work well. This is made even more difficult by the fact that cloud services are inherently ephemeral, with containers constantly being spun up and spun down.