InfluxDB: 3. Choose the instance size

This documentation is part of the GitHub Actions & GitLab CI guide. You can view the complete guide here: Launch a real InfluxDB service from your GitHub Actions or GitLab CI pipeline, run your tests against it, and automatically tear it down.

👋 Welcome to the Stackhero documentation

Stackhero offers a fully managed InfluxDB cloud environment, designed for speed and simplicity:

  • Unlimited writes, queries, dashboards, tasks, and buckets.
  • Unlimited data retention: keep your metrics for as long as you need.
  • Unlimited network and disk transfers, with no hidden limits.
  • One-click updates: always benefit from the latest features and fixes.
  • Consistent performance and enhanced security on your own private, dedicated infrastructure.

With Stackhero, you can focus on your data and analytics. Deploying InfluxDB cloud hosting only takes a few minutes, and every setup is optimized for long-term reliability.

The examples below use the entry-level instance 10G for InfluxDB by default. This is a reliable choice for most workloads, but you can adjust it as needed. To see all available instance types for InfluxDB, run:

# The NAME column shows the value to pass to --instance
stackhero instances-store-list --service-store=influxdb

Continue reading this guide

  1. Read the full guide: GitHub Actions & GitLab CI
    Launch a real InfluxDB service from your GitHub Actions or GitLab CI pipeline, run your tests against it, and automatically tear it down
  2. 1. Create an access token and store it as a CI secret
  3. 2. The lifecycle script
  4. 4. GitHub Actions
  5. 5. GitLab CI

Other articles for InfluxDB

  1. Introduction
    Introduction to InfluxDB, everything you need to know about it
  2. Getting started
    How to get started with InfluxDB
  3. Automate with the CLI
    Start InfluxDB, retrieve its credentials, and modify its configuration programmatically using the Stackhero CLI