# Devops tools used day to day

**URL:** <https://forum.guvi.in/t/devops-tools-used-day-to-day/424>\
**Category:** General\
**Tags:** devops\
**Created:** [February 4, 2026, 1:19pm UTC](https://forum.guvi.in/t/devops-tools-used-day-to-day/424 "2026-02-04T13:19:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![narankarthi101113457](https://avatars.discourse-cdn.com/v4/letter/n/f0a364/32.png) [@narankarthi101113457](https://forum.guvi.in/u/narankarthi101113457)\
**Post date:** [February 4, 2026, 1:19pm UTC](https://forum.guvi.in/t/devops-tools-used-day-to-day/424/1 "2026-02-04T13:19:22Z")

</div>

I want to understand which DevOps tools are used in day-to-day work in real projects. We often see many tools listed, but I’m curious about what is actually used daily vs occasionally.

Could you share your daily workflow or the tools you use most often as a DevOps engineer? Real-world examples would be really helpful.

---

<div class="post-metadata">

**Author:** ![astha37422](https://avatars.discourse-cdn.com/v4/letter/a/8edcca/32.png) [@astha37422](https://forum.guvi.in/u/astha37422)\
**Post date:** [February 5, 2026, 7:51am UTC](https://forum.guvi.in/t/devops-tools-used-day-to-day/424/2 "2026-02-05T07:51:02Z")

</div>

In day-to-day DevOps work, the tools are less about “using everything” and more about **a small set used consistently** across projects.

Most days start with **Git** (GitHub/GitLab/Bitbucket) for code changes, reviews, and version control. **CI/CD tools** like Jenkins, GitHub Actions, or GitLab CI are used regularly to run builds, tests, and deployments.

For environments and infrastructure, **Docker** is used daily to build and run containers, while **Kubernetes** is common for managing and scaling applications. **Cloud platforms** (AWS, Azure, or GCP) are part of everyday tasks like deployments, scaling, and monitoring resources.

Monitoring and troubleshooting also take up a lot of time. Tools like **Prometheus, Grafana, ELK stack, or CloudWatch** are used to check logs, metrics, and alerts. Alongside all this, basic **Linux commands and shell scripting** are used constantly.

So in practice, daily DevOps work revolves around **Git + CI/CD + containers + cloud + monitoring** , with automation tying everything together.

---

<div class="post-metadata">

**Author:** ![samiralimd45473](https://avatars.discourse-cdn.com/v4/letter/s/ecccb3/32.png) [@samiralimd45473](https://forum.guvi.in/u/samiralimd45473)\
**Post date:** [February 5, 2026, 10:48am UTC](https://forum.guvi.in/t/devops-tools-used-day-to-day/424/3 "2026-02-05T10:48:03Z")

</div>

In real projects, the day-to-day DevOps work is usually pretty repetitive and tool usage is more focused than those long “DevOps tool lists” you see online.

On a daily basis, most time goes into **Git** (reviewing PRs, managing branches) and **CI/CD tools** like GitHub Actions, GitLab CI, or Jenkins to check builds, deployments, and failures. You’ll also constantly use **cloud consoles and CLIs** (AWS/Azure/GCP) to inspect services, logs, and configs. **Containers** are another daily thing—Docker for building images and Kubernetes for checking pods, deployments, and rollouts.

You’ll also live inside **monitoring and logging tools** like Grafana, Prometheus, CloudWatch, or ELK to investigate alerts and performance issues. For infrastructure, **Terraform or CloudFormation** gets used whenever there’s a change, but not always every single day. Tools like Ansible are more occasional, usually for configuration changes or legacy systems.

So day to day it’s mostly: check pipelines → review deployments → watch metrics/logs → fix issues → repeat. The big takeaway is that you don’t need to master everything at once—knowing a solid workflow around Git, CI/CD, cloud, containers, and monitoring covers most real-world DevOps work.