You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Infoblox provider should increment external_dns_registry_errors_total when changes cannot be submitted due to WAPI request errors, e.g. :
CreateObject request error: 'WAPI request error: 404('404 Not Found')
Contents:
{ "Error": "AdmConDataNotFoundError: View not found",
"code": "Client.Ibap.Data.NotFound",
"text": "View not found"
}
Currently CreateObject errors do not get added to external_dns_registry_errors_total.
It looks like the counter relies on the error being propagated from the internal createRecords method to ApplyChanges here
Why is this needed:
Without this, the metric only catches a subset of issues and I have to supplement with log monitoring.
When we upgraded from 0.14.0 to 0.14.2, we had "View not found" errors relating to never having set the cmdline option "--infoblox-view=default". The errors only appear in container logs and not the metrics.
This is similar to enhancements made to error reporting in other providers, like Cloudflare in issue #4081.
The text was updated successfully, but these errors were encountered:
What would you like to be added:
The Infoblox provider should increment external_dns_registry_errors_total when changes cannot be submitted due to WAPI request errors, e.g. :
Currently CreateObject errors do not get added to external_dns_registry_errors_total.
It looks like the counter relies on the error being propagated from the internal createRecords method to ApplyChanges here
Why is this needed:
Without this, the metric only catches a subset of issues and I have to supplement with log monitoring.
When we upgraded from 0.14.0 to 0.14.2, we had "View not found" errors relating to never having set the cmdline option "--infoblox-view=default". The errors only appear in container logs and not the metrics.
This is similar to enhancements made to error reporting in other providers, like Cloudflare in issue #4081.
The text was updated successfully, but these errors were encountered: