How ops teams stay relevant during a shift left in DevOps
IT operations administrators should not perceive the shift left in DevOps as a threat to their relevance, but rather as a catalyst for a change in their priorities.
In the age of automation and the shift left movement, the exact role of IT operations teams might seem fuzzy — but it’s far from obsolete. The term shift left in DevOps means that developers address code issues during the design and development phases, rather than leave them for the operations team to resolve. This approach should be common sense — and it should have emerged before DevOps. The financial effect of a coding problem in production will always be higher than the cost of a delay in development, and the operations team shouldn’t have to pick up the pieces of poor development practices.
However, the shift left strategy has expanded, as organizations complete more tasks outside of operations. For example, developers should manage both development and testing through continuous development and delivery. And help desk loops should more closely involve business leaders in decision-making processes around the priority of issues and requests for extra functionality. Concurrently, IT sees a shift right movement: As the use of public cloud increases, admins that work internally at a cloud provider carry out actions normally within the remit of enterprise operations teams.
How ops stays relevant during these shifts
To shift left in DevOps, development teams take responsibility to ensure that code is of sufficient quality to not affect operations. Automation ensures things run as expected and that code gets packaged and provisioned without human intervention. Meanwhile, other teams of technical professionals manage third-party platforms. So, are IT organizations left to ask, “Will the last operations admin out the door please turn off the lights?”
This article originally appeared on TechTarget.com. To read the full article, click here.
Nastel Technologies uses machine learning to detect anomalies, behavior and sentiment, accelerate decisions, satisfy customers, innovate continuously. To answer business-centric questions and provide actionable guidance for decision-makers, Nastel’s AutoPilot® for Analytics fuses:
- Advanced predictive anomaly detection, Bayesian Classification and other machine learning algorithms
- Raw information handling and analytics speed
- End-to-end business transaction tracking that spans technologies, tiers, and organizations
- Intuitive, easy-to-use data visualizations and dashboards
If you would like to learn more, click here
Nastel Technologies is the global leader in Integration Infrastructure Management (i2M). It helps companies achieve flawless delivery of digital services powered by integration infrastructure by delivering tools for Middleware Management, Monitoring, Tracking, and Analytics to detect anomalies, accelerate decisions, and enable customers to constantly innovate, to answer business-centric questions, and provide actionable guidance for decision-makers. It is particularly focused on IBM MQ, Apache Kafka, Solace, TIBCO EMS, ACE/IIB and also supports RabbitMQ, ActiveMQ, Blockchain, IOT, DataPower, MFT, IBM Cloud Pak for Integration and many more.
The Nastel i2M Platform provides:
- Secure self-service configuration management with auditing for governance & compliance
- Message management for Application Development, Test, & Support
- Real-time performance monitoring, alerting, and remediation
- Business transaction tracking and IT message tracing
- AIOps and APM
- Automation for CI/CD DevOps
- Analytics for root cause analysis & Management Information (MI)
- Integration with ITSM/SIEM solutions including ServiceNow, Splunk, & AppDynamics