Coder Social home page Coder Social logo

docker-compose-grafana-influxdb's Introduction

Hi there ๐Ÿ‘‹

Developer from Taiwan ๐Ÿ‡น๐Ÿ‡ผ

Role I Play at Work

Site Reliablity Engineer, DevOps Engineer, Cloud Engineer, Technical Support Engineer

Skill Sets





More about me

guessi's github stats guessi's language stats

docker-compose-grafana-influxdb's People

Contributors

guessi avatar suhasrkms avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

docker-compose-grafana-influxdb's Issues

No influxdb.conf file

I've been using this set up with Gatling, to do this we need to have the graphite endpoint enabled and add some templates, which we were doing in the influxdb.conf file (sections I was adding below). With the latest commit upgrading to InfluxDB 2, this no longer exists. Can you advise on where I should be making these changes now?

templates = [
"gatling..users..* measurement.simulation.measurement.request.field",
"gatling...... measurement.simulation.group1.group2.request.status.field group=2",
"gatling.....* measurement.simulation.group1.request.status.field group=1",
"gatling.... measurement.simulation.request.status.field group=0",
"v2.gatling....users..* .measurement.run.host.simulation.measurement.request.field",
"v2.gatling........ .measurement.run.host.simulation.group1.group2.request.status.field group=2",
"v2.gatling.......* .measurement.run.host.simulation.group1.request.status.field group=1",
"v2.gatling...... .measurement.run.host.simulation.request.status.field group=0"]`

[[graphite]]
enabled = true
database = "gatling"
bind-address = ":2003"
protocol = "tcp"
batch-size = 5000
batch-pending = 10
batch-timeout = "1s"
separator = "."

Grafana plugin installation error: permision denied.

After running docker-compose up:
...
grafana_1 | installing grafana-clock-panel @ 0.1.0
grafana_1 | from url: https://grafana.com/api/plugins/grafana-clock-panel/versions/0.1.0/download
grafana_1 | into: /var/lib/grafana/plugins
grafana_1 |
grafana_1 |
grafana_1 | Error: โœ— Could not create /var/lib/grafana/plugins/grafana-clock-panel. Permission denied. Make sure you have write access to plugindir
grafana_1 |
grafana_1 | NAME:
grafana_1 | Grafana cli plugins install - install <plugin version (optional)>
grafana_1 |
grafana_1 | USAGE:
grafana_1 | Grafana cli plugins install [arguments...]
demo_grafana_1 exited with code 1

Missing directory under /etc/grafana/provisioning

With Grafana version upgrade, when container boot up, it will try to find plugins and alerting directories. But it currently have no folder pre-created, causing error message prompt behind the scene.

grafana  |logger=provisioning.plugins t=2023-03-22T14:30:23.196557499Z level=error msg="Failed to read plugin provisioning files from directory" path=/etc/grafana/provisioning/plugins error="open /etc/grafana/provisioning/plugins: no such file or directory"
grafana  |logger=provisioning.alerting t=2023-03-22T14:30:23.204998472Z level=error msg="can't read alerting provisioning files from directory" path=/etc/grafana/provisioning/alerting error="open /etc/grafana/provisioning/alerting: no such file or directory"

ref: https://grafana.com/docs/grafana/latest/administration/provisioning/

cleanup.sh nukes all local docker volumes

I lost a bunch of volumes unrelated to this project to docker system prune --volumes --force in the cleanup script. Any particular reason why you don't just use the -v flag with docker-compose down -v?

No worries by the way. I didn't lose anything I actually needed, but it could have been much worse.

And thanks for this project. It helped me a lot!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.