Thread: Automation
I have been asked to do some of automation as a postgres dba. I have only one year exp as dba.
Help me with some hints of what kind of automation I can do here in a simple postgres setup.
On 10/11/23 10:36, Rajesh Kumar wrote: > I have been asked to do some of automation as a postgres dba. I have only > one year exp as dba. "Some automation" is pretty ambiguous. > Help me with some hints of what kind of automation I can do here in a > simple postgres setup. What are you already doing? -- Born in Arizona, moved to Babylonia.
Hi Rajesh,
I agree with previous comments about this being pretty vague. Here are some general ideas though:
- Automate backups if applicable
- Automate fail-over if applicable
- Use Infrastructure / Configuration as Code
- Use Schema Migrations
- Implement CI/CD pipelines with static analysis (such as linting / anti-pattern checking) and automated testing.
Beyond these basics, I think people would really need to know what problem you are trying to solve. There's no point in automating a solution if the problem isn't defined and understood. Further, many solutions are really going to depend on your environment.
Best regards,
Dan Smith
On Wed, Oct 11, 2023 at 8:42 AM Rajesh Kumar <rajeshkumar.dba09@gmail.com> wrote:
Help me with some hints of what kind of automation I can do here in a simple postgres setup.
I would suggest you find at least one good reference book on PostgreSQL administration that covers everything involved with being a DBA. You will need to be aware of those regardless of automation you may choose to implement to avoid doing them manually. Also, automated metric collection tends to be important, and setting appropriate alerts (this include OS system administration scoped stuff like disk space) - regardless of whether you'd want to automated or manually resolve any events raised by those tools.
David J.
Hi
On top of that pretty good rule for automation is - automate any activity which you need to do more than 3 times e.g.
- backups
- restores
- migrations
- monitoring
- log checking
Regards
Paul G. Matuszyk
Paul G. Matuszyk
All the views expressed in this email are mine, and do not necessarily represent those of my client (or possibly anyone else in the known universe). No animals were harmed in the creation of this message. May contain nuts. In order to preserve the world's resources, this email was composed from refurbished pixels recycled from previously-used emails. Ingredients: E-113, E-120, E-9999, EI-EI-O. If you have read this far - don't you have anything better to do with your time?
On Wed, 11 Oct 2023 at 18:27, David G. Johnston <david.g.johnston@gmail.com> wrote:
On Wed, Oct 11, 2023 at 8:42 AM Rajesh Kumar <rajeshkumar.dba09@gmail.com> wrote:Help me with some hints of what kind of automation I can do here in a simple postgres setup.I would suggest you find at least one good reference book on PostgreSQL administration that covers everything involved with being a DBA. You will need to be aware of those regardless of automation you may choose to implement to avoid doing them manually. Also, automated metric collection tends to be important, and setting appropriate alerts (this include OS system administration scoped stuff like disk space) - regardless of whether you'd want to automated or manually resolve any events raised by those tools.David J.
Thanks, I'll check them out.
On Wed, 11 Oct, 2023, 9:57 PM David G. Johnston, <david.g.johnston@gmail.com> wrote:
On Wed, Oct 11, 2023 at 8:42 AM Rajesh Kumar <rajeshkumar.dba09@gmail.com> wrote:Help me with some hints of what kind of automation I can do here in a simple postgres setup.I would suggest you find at least one good reference book on PostgreSQL administration that covers everything involved with being a DBA. You will need to be aware of those regardless of automation you may choose to implement to avoid doing them manually. Also, automated metric collection tends to be important, and setting appropriate alerts (this include OS system administration scoped stuff like disk space) - regardless of whether you'd want to automated or manually resolve any events raised by those tools.David J.
Thank you
On Fri, 13 Oct, 2023, 2:15 PM Matuszyk, Paul G., <matuszyk@matuszyk.com> wrote:
HiOn top of that pretty good rule for automation is - automate any activity which you need to do more than 3 times e.g.- backups- restores- migrations- monitoring- log checkingRegards
Paul G. Matuszyk
All the views expressed in this email are mine, and do not necessarily represent those of my client (or possibly anyone else in the known universe). No animals were harmed in the creation of this message. May contain nuts. In order to preserve the world's resources, this email was composed from refurbished pixels recycled from previously-used emails. Ingredients: E-113, E-120, E-9999, EI-EI-O. If you have read this far - don't you have anything better to do with your time?On Wed, 11 Oct 2023 at 18:27, David G. Johnston <david.g.johnston@gmail.com> wrote:On Wed, Oct 11, 2023 at 8:42 AM Rajesh Kumar <rajeshkumar.dba09@gmail.com> wrote:Help me with some hints of what kind of automation I can do here in a simple postgres setup.I would suggest you find at least one good reference book on PostgreSQL administration that covers everything involved with being a DBA. You will need to be aware of those regardless of automation you may choose to implement to avoid doing them manually. Also, automated metric collection tends to be important, and setting appropriate alerts (this include OS system administration scoped stuff like disk space) - regardless of whether you'd want to automated or manually resolve any events raised by those tools.David J.