1. Proposed title of this feature request
Provide steps on how to proactively monitor MetalLB after installation.

2. What is the nature and description of the request?

To improve MetalLB documentation, building on already existing section (2) , with routinely executed commands right after installation (but not limited to) in regards of  `type LoadBalancer` bits.

e.g. 

$ oc get pods -n metallb-system => check the pods status
$ oc logs <pod-name> -n metallb-system => check for errors in the pod logs

i.e. Instruction how to inspect what the speaker pod is doing, how to check the BGP peers, etc. Basically all the procedures one would execute to make sure MetalLB has been installed correctly, or any procedure that is routinely executed to verify MetalLB is working correctly (e.g. the first few actions routinely executed on a remote call for MetalLB issues).

3. Why does the customer need this? (List the business requirements here)

Improved customer experience, and ease of issues triaging. We do have a cookbook for common troubleshooting issues in (2), something digging a big more would improve the clusters operator's life.

4. List any affected packages or components.

Documentation (0), in particular the parts for MetalLB (2), in particular the `type LoadBalancer` bits.

If that is not possible, a KCS vetted by engineering and QE would suffice, and could be later added to (1).

(0) https://docs.openshift.com/container-platform/4.12/networking/metallb/
(1) https://access.redhat.com/articles/4217411 
(2) https://docs.openshift.com/container-platform/4.12/networking/metallb/metallb-troubleshoot-support.html