This repository has been archived by the owner on Jun 25, 2024. It is now read-only.
Publish integration job log event when fetching alert monitoring policies fails due to project/{PROJECT_ID} is not a workspace
#116
Labels
bug
Something isn't working
Comments
|
Fixed in #114 |
austinkelleher
added a commit
that referenced
this issue
Apr 28, 2021
Publish integration job log event when fetching alert monitoring policies
fails due to `project/{PROJECT_ID} is not a workspace
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Related:
Monitoring Alert Policiesstep fails when a project is not assigned to a workspace #108We should consider changing the
fetch-monitoring-alert-policiesstep handler to wrap the call toclient.iterateAlertPoliciesin a try/catch and publish a job log message to let the customer know that we were unable to ingest this data due to theis not a workspaceconfiguration. This does not seem like an error that should show up as partial failure of the integration job, but rather that the customer likely choose this type of setup in their GCP project on purpose.cc @eXtremeX
The text was updated successfully, but these errors were encountered: