I recently started using proxmox and was planning on monitoring metrics using InfluxDB and Grafana, which I have already deployed on my Kubernetes cluster. However, during that process, I encountered two issues:

  • Authentication
  • “Database not found”


For the Authentication issue, I found out that you have to use the Authorization header with the Token yourAuthToken value to access the bucket. So, configure the header name in the jsonData field, and we should configure the header value in secureJsonData for grafana helm chart values.

  httpHeaderValue1: 'Token ${INFLUXDB_TOKEN}'
  httpHeaderName1: 'Authorization'

Complete datasources helm values

    apiVersion: 1
      - name: Loki
        orgId: 1
      - name: Prometheus
        type: prometheus
        url: http://prometheus-operated:9090
        access: proxy
        isDefault: true
      - name: InfluxDB
        type: influxdb
        url: "http://influxdb.default.svc.cluster.local:80"
        database: "default"
          httpHeaderValue1: 'Token ${INFLUXDB_TOKEN}'
        access: proxy
          httpHeaderName1: 'Authorization'
          httpMode: GET

“Database not found”

This one took me a while to figure out. In InfluxDB v1, data gets stored in databases and retention policies. In InfluxDB v2, data gets stored in buckets. Because InfluxQL uses the v1 data model, before querying in InfluxQL, we must map a bucket to a database and retention policy. Find more information here.

As shown below, I am using the InfluxDB API method to create DBRP mappings for unmapped buckets.

curl --request POST http://localhost:8086/api/v2/dbrps \
  --header "Authorization: Token YourAuthToken" \
  --header 'Content-type: application/json' \
  --data '{
        "bucketID": "00oxo0oXx000x0Xo",
        "database": "example-db",
        "default": true,
        "orgID": "00oxo0oXx000x0Xo",
        "retention_policy": "example-rp"

Make sure to update Host, Token, bucketID, database, orgID, retention_policy with your values.

Lastly, go to Grafana, choose the InfluxDB data source, and try to run a query to see that the setup process was successful.