Ok, a bit of context here regarding some of the variables (we will get back to them later on as well). DOCKER_INFLUXDB_INIT_ADMIN_TOKEN=randomTokenValue DOCKER_INFLUXDB_INIT_BUCKET=chooseBucketName DOCKER_INFLUXDB_INIT_PASSWORD=yourInfluxPassword DOCKER_INFLUXDB_INIT_USERNAME=yourInfluxAccount Use the following docker-compose to run the new InfluxDB 2: version: "3.5" So to start with InfluxDB, you can use the latest Docker image or any image that is 2.0 or above. Let's begin! I will keep each container separate, and not run them as a single docker-compose stack, but you can if you choose to do so. Also, be prepared to use a different query language to present the data in Grafana than before as InfluxDB 2 uses the new Flux language, and not InfluxQL as before. The reason is that we first have to configure our DB then the agent(s), and finally Grafana that will present it all.Ĭompared to the previous article, there will be some changes that will be specific to using the latest (current) versions of Influx and Grafana, and I will point out what those are. You might notice that I have placed Grafana last on the list. Grafana - the web UI that will present the metrics Telegraf - agent that will ship the metrics to InfluxĠ3. InfluxDB 2 - database element for your metricsĠ2. You need three major components to make this run in your Docker setup: 01.
In case you do not want to run the new Influx instance and use the new Flux language, stay on the older stack using the initial article! NOTE: Running InfluxDB 2 you will encounter major breaking changes as compared to InfluxDB 1.8 (or older). The reason for this article is to stay up to date with the new features as well as see if there are some other benefits of running the new platforms. Like with every platform, both Grafana and InfluxDB have been updated to give us more features, more options, and to follow user's needs and demands.
#Docker for mac disk usage how to#
How to run your GIT monitoring stack with Grafana, InfluxDB, and Telegraf. About two years ago I wrote the same article like this one.
0 kommentar(er)
