Skip to content

Latest commit

 

History

History
29 lines (19 loc) · 1.92 KB

InfluxDB.md

File metadata and controls

29 lines (19 loc) · 1.92 KB
Raw

InfluxDB integration

Environment variables

  • Metrics (InfluxDB)
    • LOADRUSH_INFLUXDB_API: InfluxDB v2 API endpoint, typically like https://us-west-2-1.aws.cloud2.influxdata.com/api/v2. Refer to InfluxDB documentation.
    • LOADRUSH_INFLUXDB_TOKEN: InfluxDB token, which can be found in InfluxDB cloud admin console.
    • LOADRUSH_INFLUXDB_ORG: InfluxDB organization, which be can be found in the URL of InfluxDB cloud admin console. e.g. https://us-west-2-1.aws.cloud2.influxdata.com/orgs/<orgID>.
    • LOADRUSH_VERBOSE_METRICS: in terms of InfluxDB cost, text fields will be sent when it is set as true, otherwise only numeric fields are sent. Default: false.
    • LOADRUSH_INFLUXDB_BUCKET: the bucket (16 chars at most) used for different iteration of your testing. Default: current timestamp since unix epoch.

As we know, InfluxDB Cloud free plan has a rate limit of 10kb/s write.

InfluxDB

If you'd like to use InfluxDB as a metric storage, we still support it.

All the data is collected in InfluxDB if you set up the account beforehand. Then you can filter and aggregate time-series data, and end up with fancy charts. If you like, build a dashboard and keep monitoring. All these things are depending on your Data processing skills.

You can easily set up a InfluxDB in your cluster. Please check influxdb folder where there are some kubernetes resource to help you deploy an influxDB in your kubernetes cluster. We set up a public one: https://data.LOADRUSH.io

We integrate InfluxDB and send real-time metrics to the cloud, so we can do analytics later. Some basic metrics like requests/success/failure count, mean response time, RPS, active virtual users etc can be monitored in its platform. We choose InfluxDB as it has an intuitive UI and easy to integrate. But we will add more integrations to other monitoring platforms in the future.