Skip to content

Commit 3d0e563

Browse files
MaciejKarasfealebenpae
authored andcommitted
Add monitoring agent logs to diagnostics (#4130)
# Summary Dumps monitoring agent logs: - monitoring-agent-verbose.log - monitoring-agent.log - mongodb-agent-monitoring stdout as it contains different logs ## Proof of Work ![Screenshot 2025-02-26 at 12 46 21](https://github.com/user-attachments/assets/3cfe8f61-f13d-4945-ba0c-78f6f3183535) Monitoring files for: - [kind-e2e-cluster-2_om-tls-monitored-appdb-db-0-0-monitoring-agent-stdout.log](REDACTED) - [kind-e2e-cluster-2_om-tls-monitored-appdb-db-0-0-monitoring-agent-verbose.log](REDACTED) - [kind-e2e-cluster-2_om-tls-monitored-appdb-db-0-0-monitoring-agent.log](REDACTED) ## Checklist - [ ] Have you linked a jira ticket and/or is the ticket in the title? - [x] Have you checked whether your jira ticket required DOCSP changes? - [x] Have you checked for release_note changes? ## Reminder (Please remove this when merging) - Please try to Approve or Reject Changes the PR, keep PRs in review as short as possible - Our Short Guide for PRs: [Link](REDACTED) - Remember the following Communication Standards - use comment prefixes for clarity: * **blocking**: Must be addressed before approval. * **follow-up**: Can be addressed in a later PR or ticket. * **q**: Clarifying question. * **nit**: Non-blocking suggestions. * **note**: Side-note, non-actionable. Example: Praise * --> no prefix is considered a question
1 parent 9e3aa8e commit 3d0e563

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

scripts/evergreen/e2e/dump_diagnostic_information.sh

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -89,6 +89,9 @@ dump_pod_logs() {
8989
echo "Writing agent and mongodb logs for pod ${pod} to logs"
9090
kubectl cp "${namespace}/${pod}:var/log/mongodb-mms-automation/automation-agent-verbose.log" "logs/${prefix}${pod}-agent-verbose.log" &> /dev/null
9191
tail -n 500 "logs/${pod}-agent-verbose.log" > "logs/${prefix}${pod}-agent.log" || true
92+
kubectl cp "${namespace}/${pod}:var/log/mongodb-mms-automation/monitoring-agent-verbose.log" "logs/${prefix}${pod}-monitoring-agent-verbose.log" &> /dev/null
93+
kubectl cp "${namespace}/${pod}:var/log/mongodb-mms-automation/monitoring-agent.log" "logs/${prefix}${pod}-monitoring-agent.log" &> /dev/null
94+
kubectl logs -n "${namespace}" "${pod}" -c "mongodb-agent-monitoring" > "logs/${prefix}${pod}-monitoring-agent-stdout.log" || true
9295
kubectl cp "${namespace}/${pod}:var/log/mongodb-mms-automation/mongodb.log" "logs/${prefix}${pod}-mongodb.log" &> /dev/null || true
9396
# note that this file may get empty if the logs have already grew too much - seems it's better to have it explicitly empty then just omit
9497
kubectl logs -n "${namespace}" "${pod}" | jq -c -r 'select( .logType == "agent-launcher-script") | .contents' 2> /dev/null > "logs/${prefix}${pod}-launcher.log"

0 commit comments

Comments
 (0)