#tokio #influx-db #metrics #telegraf #async #tcp-connection #sockets


Minimal async rust wrapper for the telegraf/influxdb protocol, based on Tokio

4 releases (breaking)

0.5.0 Feb 14, 2024
0.4.0 Feb 12, 2024
0.3.0 Jan 12, 2024
0.2.0 Jan 10, 2024
0.1.0 Jan 9, 2024

#425 in Database interfaces

Download history 14/week @ 2024-01-04 70/week @ 2024-01-11 299/week @ 2024-01-18 174/week @ 2024-01-25 179/week @ 2024-02-01 479/week @ 2024-02-08 322/week @ 2024-02-15 232/week @ 2024-02-22 118/week @ 2024-02-29 238/week @ 2024-03-07 395/week @ 2024-03-14 175/week @ 2024-03-21 76/week @ 2024-03-28 55/week @ 2024-04-04

748 downloads per month

MIT license

581 lines


Under development

tokio_telegraf crate tokio_telegraf crate downloads tokio_telegraf documentation

tokio_telegraf is a lightweight client library for general metrics writing using Telegraf. Telegraf is a micro-service provided by InfluxData for making metrics reporting easy for distributed services - see their docs for more information.

This library is a fork of maxmindlin/telegraf-rust to allow usage with asyncio, under the Tokio ecosystem.

This library does not provide querying or other InfluxDB client-library features. This is meant to be lightweight and simple for services to report metrics.

tokio_telegraf supports all socket connection types, such as UDS (unix domain socket):

  • TCP (tcp://)
  • UDP (udp://)
  • UDS Stream (unix://)
  • UDS Datagram (unixgram://)

Differences with maxmindlin/telegraf-rust

  • Asyncio only operations, based on the Tokio ecosystem.
  • TBD - Fewer allocations, by reducing the usage of Box and by handling data-points lifetimes.


Add it to your Cargo.toml:

tokio_telegraf = "*"

How to use

Using this library assumes you have a socket listener setup in your Telegraf configuration file. An example TCP connection looks like so:

  service_address = "tcp://localhost:8094"

All usage will start by creating a socket connection via a Client. This supports multiple connection protocols - which one you use will be determined by how your Telegraf input.socket_listener configuration is setup.

Once a client is setup there are multiple different ways to write points:

Define structs that represent metrics using the derive macro

use tokio_telegraf::*;

let mut client = Client::new("tcp://localhost:8094").await.unwrap();

struct MyMetric {
    field1: i32,
    tag1: String,

let point = MyMetric { field1: 1, tag1: "tag" };

By default the measurement name will be the same as the struct. You can override this via derive attributes:

use tokio_telegraf::*;

#[measurement = "custom_name"]
struct MyMetric {
    field1: i32,

As with any Telegraf point, tags are optional but at least one field is required.

Timestamps are optional and can be set via the timestamp attribute:

use tokio_telegraf::*;

struct MyMetric {
    ts: u64,
    field1: i32,

Use the point macro to do ad-hoc metrics

use tokio_telegraf::*;

let mut client = Client::new("tcp://localhost:8094").await.unwrap();

let p = point!("measurement", ("tag1", "tag1Val"), ("field1", "val") ("field2", 10); 100);

The macro syntax is the following format:

(<measurement>, [(<tagName>, <tagVal>)], [(<fieldName>, <fieldVal>)]; <timestamp>)

Measurement name, tag set, and field set are comma separated. Tag and field tuples are space separated. Timestamp is semicolon separated. The tag set and timestamp are optional.

Manual Point initialization

use tokio_telegraf::{Client, Point};

let c = Client::new("tcp://localhost:8094").await.unwrap();

let p = Point::new(
        (String::from("tag1"), String::from("tag1value"))
        (String::from("field1"), Box::new(10)),
        (String::from("field2"), Box::new(20.5)),
        (String::from("field3"), Box::new("anything!"))


Field Data

Any attribute that will be the value of a field must implement the IntoFieldData trait provided by this library.

pub trait IntoFieldData {
    fn field_data(&self) -> FieldData;

Out of the box implementations are provided for many common data types, but manual implementation is possible for other data types.


Timestamps are optional. If not present, the Telegraf daemon will set the timestamp using the current time. Timestamps are specified in nanosecond-precision Unix time, therefore u64 must implement the From<T> trait for the field type, if the implementation is not already present:

use tokio_telegraf::*;

#[derive(Copy, Clone)]
struct MyType {
    // ...

impl From<MyType> for u64 {
    fn from(my_type: MyType) -> Self {

struct MyMetric {
    ts: MyType,
    field1: i32,

More information about timestamps can be found here.


~186K SLoC