problem with enabling Switch/ManagedSwitch

[geoham911]

I have been testing fortigate_exporter for the last month or so. I am using the latest version of Prometheus and the Fortigate_exporter Ver 1.25.
Firewalls are all 7.4.12 and switches are on the latest version of 7.6. Initially tested in a test lab consisting of a FG70F with a FSW-148FPOE connected. It worked well. I then added a production firewall to the .yml config file and Prometheus config

When Fortigate_exporter service was restarted after the addition the target health in the dashboard showed the test lab was UP but the live environment was DOWN with

‘Error scraping target: server returned HTTP status 500 internal server error’

I checked the probe page and all was fine for the test environment but for the live environment showed.

5604 error(s) occurred:

• collected metric "fortigate_managed_switch_max_poe_budget_watt" { label:{name:"switch_name" value:""} label:{name:"vdom" value:"root"} counter:{value:0}} was collected before with the same name and label values.

Above is an example of the error This is the same error as #288

The live environment consists of a Fortigate FG200G and a pair of FSW-1024E for the core with multiple FSW-148F-FPOE switches in the IDF cabinets.
If I exclude Switch/ManagedSwitch in the .yml config file the device changes to UP in Prometheus and I am able to get all the other metrics. The current .yml config is shown below minus the ip and token.

tls:
insecure_skip_verify: true
probes:
exclude:
- Switch/ManagedSwitch

- System/SensorInfo

- System/Interface/Transcievers

Am I missing something.
Any ideas as to what I could try?

[pizza0223]

I am also testing fortigate-exporter (v1.25) with docker.
After updating my fortiOS on my Fortigate 81F from 7.2.13 to 7.4.12 yesterday, I'm seeing the same errors as yours.

[geoham911]

Hi pizza0223.
I was starting to think it was something in my setup. Good to know it is an issues for us. We have a lot of FortiGate Firewalls and are in the process of upgrading our existing sites switch infrastructure to FortiSwitch so it would be great to work out what the issue is with FortiSwitch when the firewalls are at the latest version of 7.4