ajeje93 / grafana-mongodb-docker

Docker container for Grafana with MongoDB datasource plugin

Grafana MongoDB datasource Docker container

Credits

Thank to JamesOsgood for creating the plugin https://github.com/JamesOsgood/mongodb-grafana.

Thank to SiemaApplications for upgrading and maintaining the plugin https://github.com/SiemaApplications-attic/mongodb-grafana. Refer to their repository for the plugin usage.

Usage

Just run docker-compose up -d to start the container.

grafana-mongodb-docker's Issues

Unsupported OP_QUERY command: aggregate.

Hi ajeje93,
Is it possible to have an image based on the fork https://github.com/SiemaApplications/mongodb-grafana that is more up to date ? Because I have an error "Unsupported OP_QUERY command: aggregate. The client driver may require an upgrade. For more details see https://dochub.mongodb.org/core/legacy-opcode-removal" due to the version of the npm mongo package being "^3.0.8" when I run this request on timeseries collection:

db.measurements.aggregate(
[
    {
        "$project": {
            "name": "$metadata.DevEUI",
            "value": "$temperature",
            "ts": "$timestamp",
            "_id": 0
        }
    }
]
)

and that works when my mongo package is at least in "^4.12.1"

Can you do something for me ?
Sincerely

grafana

i am unable to run docker-compose file can you please let me know.

My grafana wont connect to mongoDB, can anybody help?

I receive "Bad gateway"

I receive "Bad gateway" when I save and test the data source.
MongoDB version is 5.0.7 and it is installed locally on the host of docker containers.

Private repo

I think they made their repo private
https://github.com/SiemaApplications/mongodb-grafana

docker file to install grafana-mongodb image

Hi ajeje93 is there any way to use a docker-compose.yml file to install your plugin ?
Like this for example:

version: "3.7"

services:      
  grafana:
    image: ajeje93/grafana-mongodb
    container_name: grafana-mongodb
    ports:
      - 3000:3000
    restart: unless-stopped
    volumes:
      - ./grafana/provisioning/datasources:/etc/grafana/provisioning/datasources
      - grafana-data:/var/lib/grafana
      
volumes:
  grafana-data:

Like this grafana installs but I don't see the data source mongo db can you help me?
Sincerely

docker-compose up --- error

hi, I run run docker-compose up -d to start the container, finally, got the error:

..........................................................................
...........................................................................

Step 11/11 : ENTRYPOINT ["/custom-run.sh"]
 ---> Running in 3efaa137c276
Removing intermediate container 3efaa137c276
 ---> 3e677487c272
Successfully built 3e677487c272
Successfully tagged grafana-mongodb-docker_prod:latest
WARNING: Image for service prod was built because it did not already exist. To rebuild this image you must use `docker-compose build` or `docker-compose up --build`.
Creating grafana-mongodb-docker_prod_1 ... 
Creating grafana-mongodb-docker_prod_1 ... error

ERROR: for grafana-mongodb-docker_prod_1  Cannot start service prod: driver failed programming external connectivity on endpoint grafana-mongodb-docker_prod_1 (dbf0061c66e3d06739a3e7d7212b021cca0ce2b8c6ce480d2833d3af0f458244): Bind for 0.0.0.0:3000 failed: port is already allocated

ERROR: for prod  Cannot start service prod: driver failed programming external connectivity on endpoint grafana-mongodb-docker_prod_1 (dbf0061c66e3d06739a3e7d7212b021cca0ce2b8c6ce480d2833d3af0f458244): Bind for 0.0.0.0:3000 failed: port is already allocated
ERROR: Encountered errors while bringing up the project.

the 3000 port is using by Grafana default.

How to solve this, thanks.

Times out for mongodb://localhost:27017

Great implementation, works perfectly for the example server and other remote servers

I can't get it to connect to the standard 'mongodb://localhost:27017/', however. I'm guessing this is to do with the proxy server being blocked by some firewall? Any ideas how I might go about fixing.

Returns Failed to fetch' on browser and Gateway timeout' on server.

This is quite probably a user error rather than a bug!