Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uptimerobot Statuspage updates broken #499

Open
mwipplinger-ftapi opened this issue Jun 22, 2023 · 1 comment
Open

Uptimerobot Statuspage updates broken #499

mwipplinger-ftapi opened this issue Jun 22, 2023 · 1 comment
Labels
kind/bug Something isn't working

Comments

@mwipplinger-ftapi
Copy link

We've realized while trying to automatically set our uptimerobot monitors to all be added to a uptimerobot statuspage that the feature is currently broken.

The error messages we see when running the operator with our config are the following:

{"level":"info","ts":1687426035.3645682,"logger":"uptime-monitor-test","msg":"There are some new changes in <monitor_name> monitor"}
{"level":"info","ts":1687426035.414855,"logger":"uptime-monitor-test","msg":"Monitor Updated: <monitor_name>"}
{"level":"info","ts":1687426035.477496,"logger":"uptime-monitor-test","msg":"Status Page couldn't be updated: "}
{"level":"info","ts":1687426035.4775262,"logger":"uptime-monitor-test","msg":"Monitor couldn't be added to status page: Status Page couldn't be updated: "}

After a bit of analysis from our side we have identified that the required parameters for the editPSP api must have changed at some point and the current implementation of this controller does not reflect that
(The API expects the friendly_name of a psp in addition to it's id which it probably didn't do beforehand)

Also it seems like the statuspage tests were "temporally disabled" at some point by being commented out and that was never reverted so that's why this breaking change was not caught.

@karl-johan-grahn karl-johan-grahn added the kind/bug Something isn't working label Jun 28, 2023
@github-actions
Copy link

This issue is stale because it has been open for 60 days with no activity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants