These are defects and will be handled as a Jira. Pls see https://github.ibm.com/NetworkTribe/ELBaaS-VPC/issues/10011
Point: 1. If we configure an alert on PRD LB, we are not able to pinpoint the exact source of the 500 error.
Point 2: If we configure this alert on Pool, then it's easy to catch the source of the 500 error.
Point 3: ibm_is_load_balancer_backend_active_members: this is also not working; I have configured it multiple times.
| Idea priority | Urgent |
| Needed By | Not sure -- Just thought it was cool |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Excellent, thank you for the additional information ! I will send it forward to the LB team
Hi and thank you for your submission ! This seems like a defect , have you tried to resolve through a support ticket?