Hello,
Following the recent changes in Spotify API policies (🤬), the account I used to setup the Spotify App was no longer meeting the requirements (premium + less then 5 users associated). I've only discovered this issue after a few days (and thus I have a big hole in the collected infos) when I tried to login on the UI and I was getting a 403 and a login loop. After checking the logs, I've noticed that the your_spotify server was getting errors/403 since the API policies changes but was failing "silently" (only in the logs).
Would it be possible to expose a metric to get the current status of the connection with Spotify API? Maybe a simple boolean or better a timestamp of the last successful data retrieval so that we can setup metrics based alerts?
Another way of exposing that would be to expose an endpoint that would give the status. In addition to Prometheus metrics, I also have external monitoring system that watches / but fetching the / on the server always answered 200 even if nothing was working in the backend 😅
Hello,
Following the recent changes in Spotify API policies (🤬), the account I used to setup the Spotify App was no longer meeting the requirements (premium + less then 5 users associated). I've only discovered this issue after a few days (and thus I have a big hole in the collected infos) when I tried to login on the UI and I was getting a 403 and a login loop. After checking the logs, I've noticed that the your_spotify server was getting errors/403 since the API policies changes but was failing "silently" (only in the logs).
Would it be possible to expose a metric to get the current status of the connection with Spotify API? Maybe a simple boolean or better a timestamp of the last successful data retrieval so that we can setup metrics based alerts?
Another way of exposing that would be to expose an endpoint that would give the status. In addition to Prometheus metrics, I also have external monitoring system that watches
/but fetching the/on the server always answered 200 even if nothing was working in the backend 😅