What people keep running into with devops
Complaints tagged devops, each raised by more than one person. One-off posts are not included.
13 recurring problems · 92 people · 17 forums we read
Raised more than once
Most people first.
- 43How to find a cheaper CRM when HubSpot gets too expensiveHigh-end software like HubSpot features great dashboards and lead tracking, but the pricing becomes unsustainable as soon as teams scale up users. This sudden cost jump leaves small businesses paying enterprise money just to access basic features they need.
- 8Why can't I trust AI agents with production tasks?Autonomous AI tools remain too unreliable for critical operational workflows, forcing engineers to restrict them to basic read-only queries like code searches. This lack of reliability prevents system administrators from safely delegating routine automation or granting write access to production environments.
- 6Unified tool for zero-touch provisioning and IT asset managementMost endpoint management solutions handle either device deployment or IT asset tracking separately, forcing teams to stitch together multiple tools. This fragmentation prevents sysadmins from managing multi-platform hardware lifecycle workflows in a single pane of glass.
- 6Why do departing engineers leave behind broken, half-baked systems?Engineers often introduce overly complex tools and half-baked platforms into the environment primarily to learn them or pad their resumes before quitting. Once they leave, these fragile implementations become mission-critical to daily operations, leaving the remaining team to deal with broken scripts and emergency fixes.
- 5Is it too late to shift from NetSuite to Oracle Fusion or DevOps?Industry layoffs and the rise of AI in enterprise software are driving professionals to question whether they can successfully transition ecosystems or move into Sys Admin and DevOps roles. Workers worry about whether vendors will accept years of multi-certification experience from a different platform, or if they risk wasting time down the wrong career path.
- 5How to track down undocumented scripts across inherited systemsInherited legacy environments accumulate years of hidden automation scripts that no one can fully inventory or track. Maintaining these undocumented files, along with their locations, alerts, and history, becomes an unwanted side project that prevents teams from knowing what systems actually exist.
- 4Which hostname should be included in a mail server TLS certificate?Embedding changing variables like OS, hardware type, or location into hostnames causes confusion and technical debt as enterprise environments scale. This creates uncertainty when selecting a lasting name for an SMTP mail server's TLS certificate CN or SAN. Using mutable server names stops teams from establishing clean naming standards that hold up as hardware or server roles evolve.
- 3What to do when your cloud service suddenly shuts downWhen a platform like Ginee abruptly shuts down or restricts availability, retail companies and developers lose critical integrations connecting ecommerce platforms with systems like MS Navision. This forces teams into rushed migrations to alternative solutions to keep their multi-app operations running without disruption.
- 3How to decide who gets access to workplace AI toolsOrganizations are struggling to figure out how to license AI tools fairly while controlling costs across different departments. Without a clear rollout strategy, companies face security risks from employees plugging sensitive information into public models and unmonitored shadow IT connections spreading across development teams.
- 3Why is infrastructure automation so hard to maintain?Legacy RMM and configuration management tools like Ansible feel increasingly outdated, lacking the flexibility, modern API/MCP integrations, and AI-driven capabilities needed for automated drift correction. Engineers get stuck wrestling with rigid playbooks and laggy systems rather than having seamless programmatic control over the entire stack.
- 2ECS vs EKS for teams without cloud experienceUsing EKS saddles teams with heavy management overhead like babysitting clusters and configuring non-app tools like Cilium and FluxCD. For teams lacking cloud or Infrastructure as Code experience, this operational burden gets in the way, whereas ECS offers a simpler alternative with almost no additional abstractions beyond basic AWS primitives.
- 2Transitioning from cloud to on-premises AD and server adminMoving from a cloud consulting background to an on-premises role often leaves engineers needing to learn local Active Directory and server administration from scratch, or struggling to maintain Linux skills when working in a Windows-heavy shop. Without hands-on courses or experience, bridging this gap makes it difficult to know where to start learning.
- 2How do I switch from old sysadmin stuff to IaC?Sysadmins with years of legacy experience feel majorly behind when trying to re-enter the job market without large-scale cloud infrastructure or modern tool proficiency. This leaves them stuck relying on basic manual workflows while struggling to transition into full-time DevOps roles.
Comes up alongside
Topics that keep appearing on the same problems — not topics with similar names.