Open jmtsi opened 3 years ago
Not sure. The client code was extracted from another library, which had some compatibility issues with the newer Pingdom API version at the time.
This library was updated just a couple of days ago, maybe we can try using it again and removing the embedded client code.
Not sure it will help with the API limits issue you've been experiencing though.
Seeing this as well with latest.
Since this may not be maintained, suggest switching to https://github.com/timkra/prometheus-pingdom-exporter which has changes to the GO bin for Pingdom API 3.1 forked from giantswarm's exporter. Run binary natively or build docker container from the repo's Dockerfile. Note that exposed Prom metrics are a bit different.
This exporter seems to produce so much API requests that we hit the limits even with 90s scrape interval. Is there any room for optimising the amount of requests?