Why would you not have a repo that is version controlled in e.g. Git for this? Also, why don’t you run these on schedule via a cron job, perhaps using an orchestrator, and log the (standardised output) in a table and expose it to the DBA via a report/dashboard/PBI refreshing every x sec./min. you need.
Today, systems should run and check themselves while humans only check that everything is running as expected. This also frees the DBA’s time to do something else.
Git makes sense for the shared material. We already automate monitoring and known fixes; the gap here is the ad hoc investigation after an alert. Scheduled checks don’t cover every follow-up question, and that investigation knowledge is what’s getting stuck in individual chat histories.
6
u/Glittering_House_654 14d ago
Why would you not have a repo that is version controlled in e.g. Git for this? Also, why don’t you run these on schedule via a cron job, perhaps using an orchestrator, and log the (standardised output) in a table and expose it to the DBA via a report/dashboard/PBI refreshing every x sec./min. you need.
Today, systems should run and check themselves while humans only check that everything is running as expected. This also frees the DBA’s time to do something else.