Update bug_report.md (#1483)

.github/ISSUE_TEMPLATE/bug_report.md

@@ -35,6 +35,30 @@ If applicable, add screenshots to help explain your problem.
 Add any other context about the problem here.
 
 If possible, please include:
- - `kubectl describe` output
- - yaml definitions for your objects
- - log files for the operator and database pods
+ - The operator logs
+ - Below we assume that your replicaset database pods are named `mongo-<>`. For instance: 
+```                                                                                      
+❯ k get pods
+NAME      READY   STATUS    RESTARTS   AGE
+mongo-0   2/2     Running   0          19h
+mongo-1   2/2     Running   0          19h
+                                                                                     
+❯ k get mdbc
+NAME    PHASE     VERSION
+mongo   Running   4.4.0
+```
+ - yaml definitions of your MongoDB Deployment(s):
+   - `kubectl get mdbc -oyaml`
+ - yaml definitions of your kubernetes objects like the statefulset(s), pods (we need to see the state of the containers):
+   - `kubectl get sts -oyaml`
+   - `kubectl get pods -oyaml`
+ - The Pod logs:
+   - `kubectl logs mongo-0`
+ - The agent clusterconfig of the faulty members:
+   - `kubectl exec -it mongo-0 -c mongodb-agent -- cat /var/lib/automation/config/cluster-config.json`
+ - The agent health status of the faulty members:
+   - `kubectl exec -it mongo-0 -c mongodb-agent -- cat /var/log/mongodb-mms-automation/healthstatus/agent-health-status.json`
+ - The verbose agent logs of the faulty members:
+   - `kubectl exec -it mongo-0 -c mongodb-agent -- cat /var/log/mongodb-mms-automation/automation-agent-verbose.log`
+ - You might not have the verbose ones, in that case the non-verbose agent logs:
+   - `kubectl exec -it mongo-0 -c mongodb-agent -- cat /var/log/mongodb-mms-automation/automation-agent.log`