panic: Unsupported Config Type ""

[rockonedege]

Describe the bug

using docker container ghcr.io/raffis/mongodb-query-exporter:v1.0.0, to try it. I had 2 problems

• cannot open file /etc/mongodb-query-exporter/config.yaml, even it's mapped already. I had it worked around by changing it to /tmp
• then I have this mythic error: panic: Unsupported Config Type "" with all v1,v2,v3 config.yml files from folder /example. I actually modified seom filelds and them restored the original files. all the same error.

below is my docker compose snippet

  mongodb_query_exporter:
  # https://github.com/raffis/mongodb-query-exporter
  # docker pull ghcr.io/raffis/mongodb-query-exporter:v1.0.0
    image: ghcr.io/raffis/mongodb-query-exporter:v1.0.0
    container_name: mongodb_query_exporter
    hostname: mongodb_query_exporter
    environment:
      - "MDBEXPORTER_CONFIG=/tmp"
    volumes:
      - ./:/tmp

To Reproduce

Steps to reproduce the behavior:

Expected behavior

it should run as expected, with out error in parsing config.yml, or if it does, it better tells me where it is(line# , fileds etc.)

Environment

• mongodb-query-exporter version: v1.0.0
• Deployed as: docker

Additional context

None

[raffis]

1. If you mount a folder containing a config.yaml file into /etc/mongodb-query-exporter it should work fine docker run -v /home/raffi/Desktop:/etc/mongodb-query-exporter ghcr.io/raffis/mongodb-query-exporter:v1.0.0

2. If you set MDBEXPORTER_CONFIG it needs to point to a file with a .yaml suffix. If you mount the config.yaml into /tmp, the MDBEXPORTER_CONFIG needs to be /tmp/config.yaml.

I agree the error message could be more verbose in this case, I will add a fix for this. Even the .yaml suffix requirement should be removed. However at this point it is required.

[rockonedege]

The missing file problem I could get around with the yml snippet above. i suspect it was a typical permission problem I have yet to debug,thay why I used /tmp to bypass it. what stopped me is the problem with the file content as in the title, even the sample files are illformated .

[raffis]

The missing file problem I could get around with the yml snippet above. i suspect it was a typical permission problem I have yet to debug,thay why I used /tmp to bypass it. what stopped me is the problem with the file content as in the title, even the sample files are illformated .

I can just repeat myself, in the snippet your posted, the MDBEXPORTER_CONFIG is wrong. It needs to point to a file and not the folder containing the file.
If you still have a problem, please share the kubernetes manifests you used so I can reproduce it.

[raffis]

v2.0.0 is now more precise with this error. If you still have a problem please create a new task and reproducible k8s manifests.