Hello support team and community,

I'm currently try to replace our meraki monitoring from direct icmp calls to cloud based monitoring. I don't use the beta or prtg meraki sensors.

My plan is to use the HTTP Advanced Sensor and call each device individual via meraki API. So far so good. The API calls and custom http header are working.

Example:

https://api.meraki.com/api/v1/organizations/123456/devices/availabilities?serials[]=ABCD-JGDS-ABCD
Custom Header: X-Cisco-Meraki-API-Key: [MerakiAPI key]

My aim: I tried to store all variables in prtg field. Example:

%host = ABCD-JGDS-ABCD (serial number)
%windowsusername = 123456 (orgaID)
%windowspassword = [MerakiAPI key]

The solution should be scaleable to have the chance to replace central variables without a lot of efford (example: monthly API key rotation).

My problem: All prtg varaibles are not working with in the sensor settings. I testet them one-by-one and run into http fails. Example:

https://api.meraki.com/api/v1/organizations/%windowsusername/devices/availabilities?serials[]=%host
Custom Header: X-Cisco-Meraki-API-Key: %windowspassword

Does someone have a solution to pass variables into http advanced sensors ?

Article Comments

Hello,

the only variables you can use are documented in our KB here (KB article: What placeholders can I use with PRTG?)

If you want to have this feature added in a future, please submit a feature request as described here: KB article: How can I propose new features or sensors for PRTG?

Kind regards,
Johannes Beyerlein, Technical Support Team


Jan, 2023 - Permalink