OSS 2.0 is a release candidate at this time, so this may change once it’s released.
It wasn’t quite clear to me how to get up and running quickly with a docker based setup for OSS 2.0 version, so this may save you some time if you are interested. It also should be very similar to the Windows workflow excepting the basic
brew commands and service install commands you’ll just want to flip over to
choco install telegraf .
Grabbed this from a comment and modified the ports as the were flipped from the
9999 range used during first early access.
# docker exec -it influxdb /bin/bash version: "3.1" services: influxdb: restart: always # It will always restart on rebooting machine now, no need to manually manage this container_name: influxdb ports: - '8086:8086' image: 'quay.io/influxdb/influxdb:2.0.0-rc' volumes: - influxdb:/var/lib/influxdb2 command: influxd run --bolt-path /var/lib/influxdb2/influxd.bolt --engine-path /var/lib/influxdb2/engine --store bolt volumes: influxdb:
The main modifications I made was ensuring it auto started.
Access the instance on
It’s pretty straight-forward using homebrew.
brew install telegraf
The configuration file is created by default at:
/usr/local/etc/telegraf.conf as well as the
I’m still a bit new on macOS, so once I opened Chronograf, I wanted to try the new http based configuration endpoint, so I used the web gui to create a telegraf config for system metrics and then:
brew services stop telegraf
I updated the configuration (see line 16).
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>KeepAlive</key> <dict> <key>SuccessfulExit</key> <false/> </dict> <key>Label</key> <string>homebrew.mxcl.telegraf</string> <key>ProgramArguments</key> <array> <string>/usr/local/opt/telegraf/bin/telegraf</string> <string>-config</string> <string>http://localhost:8086/api/v2/telegrafs/068ab4d50aa24000</string> <string>-config-directory</string> <string>/usr/local/etc/telegraf.d</string> </array> <key>RunAtLoad</key> <true/> <key>WorkingDirectory</key> <string>/usr/local/var</string> <key>StandardErrorPath</key> <string>/usr/local/var/log/telegraf.log</string> <key>StandardOutPath</key> <string>/usr/local/var/log/telegraf.log</string> </dict> </plist>
- Start service with
brew services start telegrafand it should start sending data.
- NOTE: I’m still getting the hang of brew and service management on Linux/macOS, so the first time I did this it didn’t work and I ended up starting it using
telegraf -config http://localhost:8086/api/v2/telegrafs/068ab4d50aa24000and just running initially in my console. Any comments on if I did something wrong here would be appreciated 😁 I’m pretty sure the culprit is the need for the
INFLUX_TOKENenvironment variable and I’m not sure if the service load with brew is actually sourcing the
.profileI put this in. Maybe I can pass it explicitly?
I like the final result. Dark theme for the win.
I’ve had some spikes in Vscode recently, impacting my CPU so I’ve been meaning to do something like this for a while, but finally got it knocked out today once I realized there was a 2.0 docker release I could use to get up and running easily. Next step will be to add some process level detail so I can track the culprit (probably VScode + Docker Codespaces).
- Pretty formatting of date/time like Grafana does, such as converting seconds into hour/minutes.
- Log viewing api so I could query cloudwatch logs like Grafana offers without needing to ingest.
- Edit existing telegraf configuration in the load data section. Right now I can’t edit.
- MSSQL Custom SQL Server query plugin to be released 😁 Issue 1894 & PR 3069Right now I’ve done custom exec based queries using dbatools and locally included PowerShell modules. This sorta defeats the flexibility of having a custom query call so I can minimize external dependencies. #development #influxdb