What is NoOps, Is it Agile Ops?

Some time during 2011, Forrester had released a report ‘Augment DevOps With NoOps‘ quoting, “DevOps is good, but cloud computing will usher in NoOps.” It’s been over five years, several statements quoted then in the report still have a lot of weightage. While several have embraced cloud and Devops, there’s a huge bunch of DevOps professionals out there who still think NoOps is the end of DevOps. But, in reality NoOps is just the progression of DevOps.

And DevOps being the mere extension of Agile to include Ops as well, can we call NoOps as Agile Ops? In this post we will dive deep into how developers are building, testing and deploying applications, automating operations and making use of micro services, leading to  NoOps (more so Agile Ops) where everything is rolling out fast, very fast.  

Role of Cloud in NoOps and the Continuous Automative-Approach to DevOps for Agility

Before DevOps concept came into existence, the development team was responsible for the estimation of servers, memory and network components and the final specification of the resources. This was a tedious process. Later ITOps started taking care of estimation of servers, memory and network components and the final specification of the resources, while also managing them. However, to bring in agility, DevOps was born where developers started leveraging Agile concepts and managing operations too to roll-out applications faster.  

Today, several cloud and PaaS platforms help developers automate the application lifecycle management activities such as allocating a machine instance to run the application, loading the OS, and other architectural software components like application servers and databases, setting up the networking layer, building the application from the latest source in the code repository, deploying it in the configured machine, etc.  

So as and when the developers automate operational tasks, they are able to free-up their time more for business logic and less for operations. In most cases they perform ‘no Ops tasks at all.’ In essence, they have made a progression from DevOps towards NoOps.

DevOps is there, but it is being augmented with NoOps using automation.

Mike Gualtieri of Forrester Research, who coined the term NoOps, once said in his blog post, “NoOps means that application developers will never have to speak with an operations professional again.”  This means that now more and more developers are responsible for operations. And operations are getting ingrained in job description of developers. Thanks to increasing cloud adoption, today’s operational tasks are increasingly carried out by developers more rather than the ITOps professional. Here’s why: Cloud has brought in consistency and elasticity which makes it easier for developers to automate everything using APIs.

For instance, the leading public cloud AWS offers a bunch of services and tools that have the capability to automate repetitive tasks. Use of services like Jenkins, CodePipeline, & CodeDeploy helps them automate their build-test-release-deploy process. This enables developers to deploy a new piece of code into production, potentially saving hundreds of hours every month.

Consider the Netflix case study. Adrian Cockcroft, VP Cloud Architecture Strategy at AWS and then Cloud Architect at Netflix, says his blog post, “Several hundred development engineers use tools to build code, run it in a test account in AWS, then deploy it to production themselves. They never have to have a meeting with ITops, or file a ticket asking someone from ITops to make a change to a production system, or request extra capacity in advance.”

Cockcroft further adds in the same post, “They use a web based portal to deploy hundreds of new instances running their new code alongside the old code, put one ‘canary’ instance into traffic, if it looks good the developer flips all the traffic to the new code. If there are any problems they flip the traffic back to the previous version (in seconds) and if it’s all running fine, some time later the old instances are automatically removed. This is part of what we call NoOps.”

“NoOps approach leads to business focus, clean application development, shorter cycles, and more so increased business agility.” – Vijay Rayapati, CEO, Minjar Cloud Solutions

Further, as DevOps and microservices work better when applied together, adopting microservices architectural style and common toolset that supports it through code, engineers can bring about additional productivity to DevOps and agility to Ops.

DevOps and Microservices Architecture: Moving Hand-in-hand to Enable NoOps

Microservices can help developers and DevOps collaborate over requirements, dependencies, and problems, allowing them to work jointly on a problem such as build configuration or build script issue. With microservices, functional components can be deployed in their own archives. The application can then be organized as a logical whole through a lightweight communication component such as REST over HTTP.

More so, microservices-based architecture empowers DevOps to manage their own line of codes (LOCs) without depending on others for deploying them anytime. By enabling this independence, microservices architecture can not only help increase developer productivity but also make the applications more flexible and scalable.  

Here’re the highlights how microservices can help DevOps in all the aspects of operations management:  

  • Service Deployability: Microservices enables DevOps to incorporate service-specific security, replication, persistence, and monitoring configurations.
  • Service Replication: Kubernetes provides a great way to replicate services easily using Replication Controller when services are needed to be replicated using X-axis cloning or Y-axis partitioning. Each service can build their logic to scale.
  • Service Resiliency:  Since the services are independent by design, even if one service fails, it would not bring down the entire application. The DevOps can remedy that particular service without having to worry about the cascading impact because of the individual service failure.
  • Service Monitoring: As a distributed system, Microservices can simplify service monitoring and logging. Microservices allows DevOps to take a proactive action, for example, if a service is consuming unexpected resources and scale resources only for that service alone.

Considering the above points, DevOps should embrace the microServices approach to bring agility to all the Ops tasks carried out by DevOps engineers.

Public Cloud Services: Empowering DevOps to Move Towards NoOps

Due to a diverse set of features, tools, and services offered by cloud services, today’s developers as well as DevOps are able to automate several tasks and autoscale without the help of ITOps professionals.  This has brought down the burden of doing repetitive operational tasks, especially for developers and DevOps. For instance:

  1. Auto Scaling: A DevOps can create collections of EC2 instances/VMs, specify desired instance ranges, and create scaling policies that define when instances are provisioned or removed from the collection. When this resource provisioning capability is available at hand, the tasks of Ops team gets redundant and they can focus more on business logic rather than Ops.
  2. AWS OpsWorks, which helps configure and manage applications, create groups of EC2 instances streamline the instance provisioning and management process. When this resource managing capability is available at hand, the tasks of Ops team gets redundant and thus they can focus more on business logic rather than Ops.
  3. A centralized log management tool helps developers and devops simplify troubleshooting by monitoring, storing, and accessing log files from EC2, AWS CloudTrail, and other sources.
  4. Using EKK stack, a developer can focus on analyzing logs and debugging application instead of managing and scaling the system that aggregates the logs.  
  5. AWS CodePipeline, AWS CodeBuild, and AWS CodeDeploy help automate manual tasks or processes including deployments, development & test workflows, container management, and configuration management.
  6. AWS Config, which creates an AWS resource inventory like configuration history, configuration change notification, and relationships between AWS resources. It provides a timeline of resource configuration changes for specific services too.  Plus, change snapshots are stored in a specified Amazon S3 bucket and can be configured to send Amazon SNS notifications when AWS resource changes are detected. This will help keep vulnerabilities under check.

If you want to know how to work the magic with DevOps for AWS Cloud Management, read this post.

The last word: NoOps Brings Agility to Ops Tasks, So NoOps is Synonymous to Agile Ops

In journey of DevOps, if you automate mundane Ops tasks, it leads to NoOps. Essentially, NoOps frees-up developers’ time to further utilize their time for more innovation and to bring agility into ops (which is Agile Ops). Whatever you perceive it is: Ops Automation, AI Ops, Agile Ops , or more, it is a rolling stone with the right momentum.

What is your take on this? Do share your thoughts.

April Roundup @ Botmetric: Aiding Teamwork to Solidify 3 Pillars of Cloud Management

Spring is still on at Botmetric, and we continue to evolve like seasons with new features. This month, the focus was on how to bring in more collaboration and teamwork while performing various tasks related to cloud management. The three pillars of cloud management, visibility, control, and optimization, can be solidified only with seamless collaboration. To that end, Botmetric released two cool collaborative features in April: Slack Integration and Share Reports.

1. Slack Integration

What is it about: Integrating Slack collaboration tool and Botmetric so that a cloud engineer will never miss an alert or notification when on a Slack channel and quickly communicate/alert it to their team ASAP. 

How will it help: Cloud engineers can quickly get a sneak-peak into specific Botmetric alerts, as well as details of various cloud events, on their desired channel of Slack. Be it an alert generated by Botmetric’s Cost & Governance, Security & Compliance, or Ops & Automation, engineers can see these alerts without logged into Botmetric, and quickly communicate the problem between the team members.

Where can you find this feature on Botmetric: Under the Admin section inside 3rd Party Integrations.

To know more in detail, read the blogBotmetric Brings Slack Fun to Cloud Engineers

2. Share/Email Data-Rich AWS Cloud Reports Instantly

What is it about: Sharing/emailing Botmetric reports directly from Botmetric. No downloading required.

How will it help: For successful cloud management, all the team members need complete visibility with pertinent data in the form of AWS cloud reports. The new ‘Share Reports’ feature provides complete visibility across accounts and helps multiple AWS users in the team better collaborate while managing the cloud.

Where can you find this feature on Botmetric: Across all the Botmetric products in the form of a share icon.

To know more in detail, read the blog ‘Share Data-Rich AWS Cloud Reports Instantly with Your Team Directly From Botmetric.’

Knowledge Sharing @ Botmetric

Continuing our new tradition to provide quick bites and snippets on better AWS cloud management, here are few blogs that we covered in the month of April:

Gauge AWS S3 Spend, Minimize AWS S3 Bill Shock

AWS S3 offers a durability of  99.999999999% compared to other object storage on AWS, and features simple web interface to store and retrieve any amount of data. When it comes to AWS S3 spend, it has something more in it beyond just the storage cost. If you’re a operations manager or a cloud engineer, you probably know that data read/write or data moved in/out also do count  AWS S3 bill. Hence, a detailed analysis of all these can help you keep AWS S3 bill shock to a minimum. To know how, visit this page.

7 Tips on How to Work the Magic With DevOps for AWS Cloud Management

Are you a DevOps engineer looking for complete AWS cloud management? Or are you a AWS user looking to use DevOps practices to optimize your AWS usage? Both ways, AWS and DevOps are modern way of getting things done. You should leverage new age DevOps tools for monitoring, application performance management, log management, security, data protection and cloud management instead of trying to build adhoc automation or dealing with primitive tools offered by AWS.

Get the top seven tips on how to work the magic with DevOps for AWS cloud management.

The Ultimate Cheat Sheet On Deployment Automation Using AWS S3, CodeDeploy & Jenkins

If you’re a DevOps engineer or an enterprise looking for a complete guide on how to automate app deployment using Continuous Integration (CI)/Continuous Deliver(CD) strategies, and tools like AWS S3, CodeDeploy, Jenkins & Code Commit, then bookmark this blog penned by Minjar’s cloud expert.

Botmetric Cloud Explorer: A Handy Topological Relationship View of AWS Resources

Do you want to get a complete understanding of your AWS infrastructure. And map how each resources are connected and where they stand today for building stronger governance, auditing, and tracking of resources. Above all get one handy, cumulative relationship view of AWS resources without using AWS Config service. Read this blog how to get a complete topological relationship view of your AWS resources.

The Cloud Computing Think-Tank Pieces @ Botmetric

5 Reasons Why You Should Question Your Old AWS Cloud Security Practices

While you scale your business on cloud, AWS too keeps scaling its services too. So, cloud engineers have to constantly adapt to architectural changes as and when AWS updates are announced. While all architectural changes are made, AWS Cloud Security best practices and audits need to be relooked too from time to time.

Tightly Integrated AWS Cloud Security Platform Just a Click Away

As a CISO, you must question your old practices and relook at them whether it’s relevant in the present day. Here’re the excerpts from a think tank session highlighting the five reasons why you should question your old practices.

The Rise of Anything as a Service (XaaS): The New Hulk of Cloud Computing

The ‘Cloud-driven aaS’ era is clearly upon us. Besides the typical SaaS, IaaS, and PaaS offerings discussed, there are other ‘As-a-Service(aaS)’ offerings too. For instance, Database-as-a-service, Storage-as-a-Service, Windows-as-a-Service, and even Malware-as-a-Service. It is the era of Anything-as-a-Service (XaaS). Read the excerpts from an article by Amarkant Singh, Head of Product, Botmetric, featured on Stratoscale, which share views on XaaS, IaaS, PaaS, and SaaS.

April Wrap-Up: Helping Bring Success to Cloud Management

Rain or shine, Botmetric has always striven to bring success to cloud management. And will continue to do so with DevOps, NoOps, AIOps solutions.

If you have missed rating us, you can do it here now. If you haven’t tried Botmetric, we invite you to sign-up for a 14-day trial. Until the next month, stay tuned with us on Social Media.

The March Roundup @ Botmetric: Easier AWS Cloud Management with NoOps

Spring is here, finally! The blooming fresh buds, the sweet smell of the roses, and the cheerful mood all around. Earth seems to come to life again. Seasons are vital to the transition and evolution of our planet; it also serves the purpose of the evolution of human consciousness too. Likewise, transition and evolution of your AWS Cloud Management consciousness too plays a vital role in improving the lives — primarily productivity — of DevOps and cloud engineers in your organization.

Your AWS Cloud Management efforts carried out by your DevOps engineers and cloud engineers, either in silos or with an integrated approach, needs to be regularly monitored, nurtured, and evolved from time to time. And when we say AWS Cloud Management efforts, we include AWS cost management, AWS governance, AWS cloud security and compliance, AWS cloud operations automation, and DevOps practices.

There are, of course, a variety of AWS services at your disposal to engineer a fully automated, continuous integration and delivery system, and help you be at the bleeding edge of DevOps practices. It is, however, easier said than done.

Right tools at hand are what that matters the most, especially when you are swimming in a tide of several modules. With agile digital transformations catching up quickly in every arena, it’s high time you must ensure that your team’s every AWS Cloud Management effort count to get that optimal ROI and lowered TCO.

To that end, Botmetric has been evolving all its products — Cost & Governance, Security & Compliance, and Ops & Automation, with several NoOps and DevOps features that make life of DevOps engineers and cloud engineers easier.

More so, you get more out of your AWS cloud management than you think. Explore Botmetric.

In March, Botmetric rolled-out four key product features. Here’re the four new feathers in the Botmetric’s cap:

1. Define Your Own AWS Security Best Practices & Audits with Botmetric Custom Audits

What is it about: Building your own company-wide AWS security policies to attain comprehensive security of the cloud.

How will it help:  Audit your infrastructure and enforce certain rules within your team, as per your requirements. You can put the custom rules or audits on auto-pilot — no need to build and run scripts every time through cron/CLI. Above all, you can automate your AWS security best practices checks.

Where can you find this feature on Botmetric: Under Security & Compliance’ Audit Report Console.

Get more details on this feature here.

2. Increase Operational Efficiency by 5X with Botmetric Custom Jobs’ Cloud Ops Automation

What is it about: Writing Python scripts inside Bometric to automate everyday, mundane DevOps tasks.

How will it help: Empowers DevOps engineers and cloud engineers to run desired automation with simple code logic in Python, and then schedule routine cloud tasks for increased operational excellence. Help engineers free up a lot of time.

Where can you find this feature on Botmetric: Under Ops & Automation’ Automation Console.

Get more details on this feature here.

3. Unlock Maximum AWS RDS Cost Savings with Botmetric RDS Cost Analyzer

What is it about: It is an intelligent analyzer that provides complete visibility into RDS spend.

How will it help: Discover unusual trends in your AWS RDS usage and know which component is incurring the significant chunk of the cost. Get a detailed breakup of RDS cost according to AWS instances, instance types, AWS accounts, AWS sub services, and instance engine.

Where can you find this feature on Botmetric: Under Cost & Governance’ Analyze console.

Get more details on this feature here.

4. AWS Reserved Instance Management Made Easy with Botmetric’s Smart RI

What is it about: Automatically modify reservation as soon as there is a modification available without going to AWS console.

How will it help: Reduce the effort involved in modifying the unused RIs. Automate modification of RIs that occur multiple times a day as soon as the unused RIs are found. Saves that much amount of cost that could have been wasted due to unnecessary on-demand usage, along with wasted RIs.

Where can you find this feature on Botmetric: Under Cost & Governance’ RI console.

Get more details on this feature here. You can also read it on AWS Week-in-Review.

Knowledge Sharing @ Botmetric

Continuing our new tradition to provide quick bites and snippets on better AWS cloud management, here are few blogs that we covered in the month of March:

The Road to Perfect AWS Reserved Instance Planning & Management in a Nutshell

98% of Google search on ‘AWS RI benefits’ shows that you can get great discounts and save tremendously compared to on-demand pricing. The fact is, this discounted pricing can be reaped provided you know what RIs are, how to use them, when to buy them, how to optimize them, how to plan them, etc. This blog covers all the details how to perfect your AWS RI planning and management.

DevSecOps: A Game Plan for Continuous Security and Compliance for your Cloud

DevOps makes it possible for the code to deploy and function seamlessly. And where does “security” stand in this Agile, CI/CD environment? You cannot afford to compromise on security and turn your infrastructure vulnerable to hackers, for sure! So, here comes the concept of “DevSecOps” — the practices of DevSecOps. If you’re looking to bring Security Ops into DevOps, then bookmark this blog.

3 Effective DDoS Protection & Security Solutions Apt for Web Application Workloads on AWS

NexusGuard research quoting 83% increase in Distributed Denial of Service (DDoS) attacks in 2Q2016 compared to 1Q2016 indicates that these attacks seems to continue being prevalent even beyond 2017. Despite stringent measures, these attacks have been bringing down web applications and denying service availability to its users with botnets. Without a doubt, DDoS mitigation is pivotal. If you’re a security Ops engineer, then this blog is a must read.

5 Interesting 2017 DevOps Trends You Cannot Miss Reading

In 2017, there is a lot of noise about what will be the future of DevOps. Here is a look at five interesting 2017 DevOps trends  you cannot miss reading and what our thought leaders think.

Don’t Let 2017 Amazon AWS S3 Outage Like Errors Affect You Again

On February 28th, 2017, several companies reported Amazon AWS S3 Cloud Storage Outage. Within minutes, hundreds and thousands of Twitter posts started making rounds across the globe sharing their experiences how their apps went down due to this outage. No technology is perfect. All technologies might fail at some point. The best way forward is to fool-proof your system against such outages in the future, as suggested by Team Botmetric.

To Conclude:

Rain or shine, Botmetric has always striven to improve the lives of DevOps and cloud engineers. And will continue to do so with DevOps, NoOps, AIOps solutions. Get 14-Day Exclusive Botmetric Trial Now.

If you have missed rating us, Botmetric invites you to do it here. Until the next month, stay tuned with us.

5 Interesting 2017 DevOps Trends You Cannot Miss Reading

Editorial Note: This exclusive post is written by Botmetric guest blogger, Kia Barocha.

If you think you heard and read a lot about DevOps in 2016, it’s not over yet. Gear up as there is much more expected in 2017. The key focus for DevOps in 2016 was to ensure security, enhancements and containerization. In 2017, there is a lot of noise about what will be the future of DevOps. Here is a look at what our thought leaders think (they definitely think that it will impact business hugely in 2017).

The main challenge, till date, for many professionals has been to clearly understand DevOps. Some call it a movement, while others think that it is a collection of concepts. If we were to properly define it, we would say that it is a combination of two terms, which are Development and Operations. Or as the definition goes, “it is a cross-disciplinary community of practice dedicated to the study of building, evolving and operating rapidly-changing resilient systems at scale.”

DevOps is a practice where operations and development professionals or engineers participate in the entire service lifecycle (which means starting from design to development and till the production support stage). It is a recipe of success through cultural shift. It is characterized by autonomous teams and a constantly learning environment. If you are ready for this adoption, it implies that you are ready to change fast, develop fast, test fast, fail fast, recover fast, learn fast, and also prep fast for product launches.

With DevOps businesses have experienced higher business value, better alignment with IT, helps break down silos, helps build a flexible and software enabled IT Infrastructure.

DevOps Trends in 2017

Image Source: https://cloudsmartz.com/wp-content/uploads/2016/01/Devops-Team.jpg

Let’s take a look at the DevOps trends that will really be dominant through 2017:

1. Large enterprises will adopt DevOps

The predominant trend, till now, has been that organizations have experimented with DevOps in small and discrete projects. Experts feel that in 2017, large enterprises will be more comfortable to adopt DevOps at large (at an enterprise-level). It will finally take the center stage. One of the key benefits that DevOps enables is enhanced collaboration between developers, QA and testing professionals, Operations personnel, people from business planning and security teams.

2. Focus on enhanced security

Not that the focus on security was not there earlier but given the way attackers are getting smarter and more sophisticated, there will be much more focus on unifying development, continuous security and operations efforts. 2017 will be the year, user experience and advanced security measures will go hand in hand.

3. Consolidation of DevOps tools

There are too many DevOps tools that are good for different aspects of meeting the requirements of the delivery cycle. Most of the tools that are available help to automate some aspect of the process of software delivery. Tools like Jenkins, Docker, AWS, GitHub, and JIRA are already quite popular in the market. In 2017, there will be an integration of all these tools to a selected few which can cater to all the requirements across the continuous delivery cycle. This can mean that the biggies might acquire the smaller DevOps companies, as well as start a journey towards NoOps to put their operations on auto-pilot.

4. Confluence of Big Data and DevOps

Just like IoT, there is a lot of critical information generated when software releases are automated. And again like IoT, this large volumes of data needs to be analyzed. There is a dire need to apply machine learning to all this data so that there is some actionable business reports, and way to predict failures, and manage the releases more effectively.

5. More support for hybrid everything

The market is dynamic and bigger organizations have legacy applications in co-existence with micro services, on premise cloud infrastructure – basically hybrid everything (which includes infrastructure, tools, processes, applications, etc.). DevOps, in that respect, is ready and can support multiple aspects of an organization’s hybrid existence.

If you wish to focus on software innovation, and accelerate release of application updates, look at DevOps as an enterprise-wide investment.


Guest Blogger’s Profile:

Kia Barocha is a content marketing strategist at ISHIR, a leading Dallas-based software development company, offering high-quality Mobile App Development, Web Design & Development, Cloud Computing Solutions and Application Virtualization Services to the clients across the globe. 

Increase Operational Efficiency by 5X with New Botmetric Custom Jobs’ Cloud Ops Automation

As a Cloud Ops engineer, do you get that feeling — that you are stuck like a tiny pet hamster in a wheel, doing the same stuff again and again, and going nowhere? You have plans to automate everyday cloud operation tasks and a roadmap towards Cloud Ops Automation, but don’t know from where to start! Working on mundane operational tasks day-in day-out is too taxing. Does this ring a bell?


The best way forward is to schedule all your routine tasks and use simple python scripts to achieve the desired automation using Botmetric’s New Custom Jobs.

Here’s Why Botmetric Built Custom Jobs

Botmetric Ops & Automation product already offered a list of 25+ pre-defined automated jobs. Using these jobs, you could automate a lot of routine tasks for major 7 AWS services. A lot of Botmetric customers liked these automated jobs and further requested some unique operational tasks in AWS cloud. Hence, Botmetric team built an universal solution that had the ability to custom run python scripts through the Botmetric console.

Game-changing Cloud Ops Automation Features in Botmetric Custom Jobs

In current marketspace a lot of SaaS products offer automations but  lack in delivering categories of custom jobs. However, Botmetric Ops & Automation, since its release, has solved almost 80% of automation requirement.

With Botmetric Custom Jobs you can:

  • Run your own custom scripts: Through one Botmetric console now you can perform both governance and automation. Botmetric Custom Jobs allows you to write desired Python scripts and automate scheduled execution through Botmetric console.
  • Increase operational efficiency: There are a list of tasks that a DevOps engineer performs on everyday basis and these tasks differ from one infrastructure type to another. Automating such tasks through scripts would free up a lot of time for the DevOps engineer so that one could concentrate on business innovation.
  • Get visibility into executions: Unlike running a script through cron/CLI, with Botmetric, you will have the ability to view status, receive alert or email notification on success or failure, and get historic execution details.

How to Schedule Custom Jobs on Botmetric?

There are two ways to schedule custom jobs:

1. Create a job with new script

Write your new script in the editor provided and verify the syntax. Provide necessary naming for identification and give email address to be notified.

Create a job with new script


2. Utilize saved scripts to create a new job

You can also choose from the previously created scripts and schedule a task out of it.

2) Utilize saved scripts to create new job


Essentially, Custom Jobs will empower you with running desired automation in your environment. With simple code logic of yours, written in Python, you can schedule your routine tasks for increased operational excellence.

Here’re few use cases to give you a gist of Custom Jobs’ potential:

The Case in Point for Creating VPC in a Region

Assume, you’re headquartered in Bay Area of the USA and have your business on cloud. So you have populated maximum of your resources in US-west. Lately, you expand your business to Germany too. However, you are still launching instances in US-west. Your team starts complaining about latency issues. So you decide to populate resources in EU-central, as the present EU-central region offers greater benefits. With a simple Python script for creating VPC in a region, with user defined CIDR scheduled, you can have the VPC created for any resources launched in this region.

The Case in Point for Copying EBS Snapshots Automatically Across Instance Tags

If you are looking for heightened DR policies and want to secure your snapshots, you can use Custom Jobs to write a custom script on Copy EBS snapshots across instance tags that can schedule your volume snapshots for the mentioned  instance tags across regions and secure them.

The Case in Point for Automatically Deleting Snapshots

If you are looking to derive savings from optimizing your back-ups, you can form a custom script to schedule deletion of old snapshots after defined number of days. By automating this through Custom Jobs you will lower wastage and save on unnecessary back-up retentions.

[mk_title_box color=”#FFFFFF” highlight_color=”#008080″ highlight_opacity=”0.5″ size=”18″ line_height=”34″ font_weight=”inherit” margin_top=”0″ margin_bottom=”18″ margin_left=”10″ font_family=”none” align=”center”] Try Botmetric Custom Jobs Now[/mk_title_box]

To Conclude

Each passing day, we are moving more towards NoOps, which essentially means that machines can automate known problems, while humans can focus on new problems. Many of Botmetric customers have embraced NoOps (knowingly/unknowingly) by automating all and every possible routine tasks in their environment so that DevOps time is spent more towards solving new issues, and increase operational efficiency by 5X.

What are you waiting for? Take a 14-day trial and check for yourself how Botmetric helps you automate cloud ops tasks. If you’re already a customer, and have any questions, please pop them in the comment section below. We will get back to you ASAP. If you are looking to know about all things cloud, follow us on Twitter.

The Feb Roundup @ Botmetric: Embark on a Journey Towards NoOps

The second month of 2017 has ended on a great note at Botmetric, with more focus on championing NoOps and making life easier for AWS users.

Our philosophy at Botmetric is that humans should solve new problems while machines can solve known problems. So, we have embarked on a journey towards NoOps, which essentially means: Saying ‘No’ to mundane and known ‘operational’ problems that can be automated using machines.

To that end, we released Incidents, Actions, & Triggers app, under Botmetric Ops & Automation product. Essentially, this app helps DevOps engineers take control on how they manage a deluge of alerts thrusted upon them. Botmetric’s intelligent machine learning capability can automatically do the correlation of alerts from network, application and infrastructure, group them as incidents and automate remediation for known operational problems in an IT infrastructure. To get a gist of what it is read the blog here. To get a detailed overview of the app, visit Botmetric feature page here.

[mk_title_box color=”#FFFFFF” highlight_color=”#008080″ highlight_opacity=”0.3″ size=”18″ line_height=”34″ font_weight=”inherit” margin_top=”0″ margin_bottom=”18″ font_family=”none” align=”left”] TRY Incidents, Actions, & Triggers NOW [/mk_title_box]

What’s Else is New?

In February, we also introduced Undo & Reallocate capability into Botmetric Chargeback app, which helps AWS users manage their AWS cloud budget like a champ, and also provide the capability to define, control, allocate, and understand their AWS cost allocation by different cost centers in their organization, while also have an ability to generate internal chargeback invoices. Botmetric Product Marketing Executive Girivaru Tarun covered an awesome post about this feature. Do read it here.

[mk_title_box color=”#FFFFFF” highlight_color=”#008080″ highlight_opacity=”0.3″ size=”18″ line_height=”34″ font_weight=”inherit” margin_top=”0″ margin_bottom=”18″ font_family=”none” align=”left”] Know More About Undo & Reallocate [/mk_title_box]

As a customer-focused company, Botmetric always strives to integrate top-notch features that ultimately make the customers’ life easier and better. So, Botmetric introduced the first phase of Single Sign On (SSO) for Enterprises with Google. Do read the blog post to know more about it.

[mk_title_box color=”#FFFFFF” highlight_color=”#008080″ highlight_opacity=”0.3″ size=”18″ line_height=”34″ font_weight=”inherit” margin_top=”0″ margin_bottom=”18″ font_family=”none” align=”left”] Single Sign On (SSO) for Enterprises : Check it Out Now [/mk_title_box]

Featured Blogs of the Month

Botmetric published several blogs to throw more light on how to make a progression from DevOps to NoOps in 2017. Do check them out below.

Top Five DevOps to NoOps Trends to Watch in 2017 and Beyond

Know all the top five trends shaping the cloud world in 2017 and beyond, like Serverless Programming, Containerization, Microservices Architecture, Intelligent and Unified Operations, and Self Healing and Auto Remediation. Read here.

Champion DevOps to NoOps in 2017 with Algorithmic IT Operations (AIOps)

A progression from DevOps to NoOps is a must, if you are building your application or solution with a credo that “machines should solve known problems and engineers must focus on solving new problems.” And for that progression to actualize from DevOps to NoOps, embracing AIOps is a must. This blog is a must read, if you want to know about the top five AIOps that can help you navigate your DevOps tasks smoothly through 2017. Read here.

Why You Need Cloud Garbage Collection in 2017?

At Botmetric, we are implementing several cloud garbage collection mechanisms for our customers to ensure they take advantage of the cost savings and leverage intelligent automation to tame the leakages and thus control their business’ cloud spend. Want to know what cloud garbage collection is, read this blog post.

The State of DevOps in 2017

Botmetric guest blogger, Nate Vickery, beautifully weaved the State of DevOps in 2017 for us. In this blog post, Nate says, “DevOps has arrived in the time of need, giving a solution to the demand for new software and offering a way into the future with new ways of collaboration and development of software processes.Read on to know what this year hold for DevOps engineers in the cloud.” Read the blog to know more.

More Expert Featured Blogs @ Botmetric

In February, we also spoke about Continuous Security on the cloud, to help cloud users to be more nimble when it comes to cloud security, and how they need to use automation to get continuous security on the cloud.

On the more technology front, Botmetric’s zealous Minja Nikit Swaraj shared one of his awesome blog posts titled, Containerized Application Deployment on AWS using Docker Cloud. If you are a DevOps guy trying to deploy containerized application on AWS, then bookmark this blog. Because it provides step-by-step procedure on how to go about it.

There are many more insightful blogs populated on public cloud and cloud management. Do read them here.

The ultimate goal at Botmetric is to help customers move towards NoOps. With that, on to March! We’ve got some exciting things coming in few days. So, to be the first to hear about feature updates, new blog posts, and more just just leave your email ID below and we will ensure you will receive all updates from Botmetric. And have you rated Botmetric, yet? If not, rate it now.

The State of DevOps in 2017

Editor’s Note: This is a guest blog post authored by Nate Vickery, a business technology expert.

As we witness the technological “Big Bang,” the demand for new applications and new software will expand. This is nothing new, because every time humanity has leaped forward with new technologies, so has the demand for new products. DevOps has arrived in the time of need, giving a solution to the demand for new software and offering a way into the future with new ways of collaboration and development of software processes.

However, in 2016, humanity saw DevOps in a typical way humanity views something new – the “Let’s poke it with a stick, and see what happens” kind of way. Every time a new opportunity is seen on the horizon, humanity is skeptical. Nevertheless, DevOps offers a new perspective that is perceived as positive by enterprises, which are already starting to implement some of the ideas DevOps has to offer. 2017 will be an interesting year for DevOps and software development in general.

Alternative or Evolution

People see DevOps as an alternative to agile software development. Experts argue about whether we should abandon a system that has been proven effective and has been around for over a decade and switch to a more innovative method. After all, we are creatures of habit – it’s always a challenge to move from what you got used to, to something different. However, the need for DevOps came to life from agile software development’s popularity and its tendencies to provide more software releases.

Agile methodology signifies a change in the way of thinking and practice that leads to organizational change. DevOps emphasizes the importance of organizational change and improved collaboration between departments for achieving goals. Instead of an alternative, DevOps should be seen as the next step in agile development as it improves the practices of agile methodology and brings something new to the process.

Increased Popularity

Enterprises are already experimenting with DevOps practices. DevOps practices ensure notably shorter time to market, better product quality, reliable releases, and improved customer satisfaction. Also, they allow you to build the right product by fast experimentation and improved productivity and efficiency. But those are not the only things that DevOps brings to the table. The popularity of DevOps will continue to rise as its innovative methods are being used more often.

We can already see microservices being used more and more for developing continuously deployed systems. And the possibilities of software containers are driving enterprises crazy. Serverless systems that have the potential to change how companies develop software and applications that are built into the kernel itself are truly capturing the attention of everyone in the industry. Large enterprises will undeniably adopt DevOps even more in 2017.

More Useful Tools

We have seen various tools similar to DevOps in the past few years, like Docker – for containerization, Vagrant- visualization platform, Puppet – Infrastructure as Code, and Jenkins – for continuous integration. Docker, for example, is an open source project, and many companies like Microsoft and IBM have already announced support or partnership with Docker in the future.

There are plenty more tools available, like:

  • Code review and Verizon control tools
  • Build status tools
  • Test and result tools that determine performance
  • Artifact repository and application pre-deployment staging tools
  • Release automation tools
  • Infrastructure as Code tools
  • Application performance monitoring tools

DevOps supply a wide variety of tools – from biometric authentication tools to Code development tools. It seems that enterprises see the potential in the development and usage of these tools, and are willing to offer even more support. Therefore, we can expect that most, if not all, of those tools will become improved and more sophisticated in 2017.

More Collaboration and Consolidation

With DevOps comes a new way of organizing business structure. Managers have been interested in improving cross-department communication in more than one way. DevOps introduces a necessity for collaboration and consolidation between all aspects of an organization and mutual aid between developers, SQA testers, security testers, and every other staff member of the IT sector.

This culture has a positive effect on efficiency and progress of software life-cycle and software delivery. Since there has been positive feedback on this culture, the management team will most likely try to implement this method on a company-wide scale. After all, it is perceived as well-organized and profitable.


DevOps is a clipping from “software development” and “information technology operations.” DevOps aims to establish an environment and culture where developing, testing and releasing software can happen frequently, rapidly and more reliably. As mentioned, it emphasizes collaboration between software developers and other IT professionals. So far, it has proved to be an amazing method with a potential to push the technology even further. It is safe to assume that 2017 will be the most exciting year for DevOps progress and development. Let’s wait and see how the events unfold.


Guest Blogger’s Profile:

Nate Vickery is a business technology expert mostly focused on future trends applicable to SMB and startup marketing and management processes. He has also been blogging in the past few years about before mentioned topics on various leading sites and communities. In the little free time left, Nate edits a business oriented website – Bizzmarkblog.com.

Champion DevOps to NoOps in 2017 with Algorithmic IT Operations (AIOps)

How awesome would it be if machines resolve known, repetitive, and identifiable mundane problems while humans solve new complex problem? As a DevOps engineer managing cloud operations and handling tons of alerts everyday, had you wish this was true; that day isn’t far. Thanks to Algorithmic IT Operations (AIOps), which can reduce the stress and fatigued workload, eliminate alerts & repetitive events, improve business agility through intelligent management layers, and above all respond quickly to production incidents ten times faster.

Here’re the five AIOps that can help you navigate your DevOps tasks smoothly through 2017:

  • Adopt a Culture of NoOps

    For engineering teams to nurture the belief that “machines should solve known problems and engineers must focus on solving new problems,” they must first adopt NoOps philosophy, which essentially means saying NO to manual operations and yes to AIOps.

  • Automate Known Problems

    Engineers, who have managed production infrastructure, business services, applications and architected systems often observe that few problems are caused by known events and few problems have identifiable patterns. In such scenarios, these engineers would have had an idea on what to do when certain events or symptoms occur in their application or production infrastructure. Automating actions (response mechanisms) for such known events, along with the business logic embedded using algorithms, is the best way forward.

  • Build Diagnostics for Operational Issues

    Most of today’s tools just provide a text of what happened instead of providing a context of what is happening or why it’s happening, when events or alerts occurring due to problems are triggered. If there are diagnostic, algorithmic scripts or programs to tell why, rather than just when and where, it becomes easier to get the context, thus enabling to find the root cause faster. 

  • Use Code as a Weapon

    Yes! You can create everything from automated actions to diagnostics using code to save hours of time after every deployment. In essence, using CODE as a mechanism for resolving problems should be the way forward.The key is to start applying algorithms for solving IT operational problems.As a DevOps engineer, if you are building the continuous integration or continuous delivery today then you should certainly deploy a trigger as part of your CI/CD pipeline that can monitor deployment for health metrics and invoke a rollback if it detects issues.

  • Adopt Intelligent DevOps Tooling

    With the availability of technologies like Docker, microservices, cloud and API driven approach to deploying applications at scale, days of using static tooling for deployments, provisioning, packaging, monitoring, APM and log management is almost over. It’s about time, embrace AIOps.

The Wrap-Up

A progression from DevOps to NoOps is a must, if you are building your application or solution with a credo that “machines should solve known problems and engineers must focus on solving new problems.” And for that progression to actualize from DevOps to NoOps, embracing AIOps is a must.

Botmetric is excited about working on an intelligent event-driven platform for managing incidents and operations for the cloud world. Botmetric, as a platform, handles most of the operational problems a DevOps engineer faces using application discovery, alerts data, cloud configuration, historic patterns and known events. The ultimate goal at Botmetric is to help customers move from DevOps to NoOps philosophy by bringing Algorithmic IT Operations for incident management in the cloud.

What is your take on AIOps and NoOps? Do share your thoughts below in the comment section, or on Twitter. Do read the Botmetric blog post on Alert Analytics to see how Botmetric is driving cloud management with NoOps capabilities.

Editor’s Note: This exclusive blog post is an adaption of the original article, DevOps to NoOps: Embrace Algorithmic IT Operations in 2017, penned by Botmetric CEO Vijay Rayapati.

Embark on a NoOps Journey: Mitigate Alert Fatigue with Botmetric Incidents, Actions, & Triggers

Editorial Note: This exclusive blog post is written by Botmetric CTO Akash Bhunchal.


Every IT Ops engineer, on an average, receives hundreds of alerts, perhaps even more than that, in his/her inbox or on Slack. Upon seeing an alert, the engineer spends up to 20 minutes to tend to it. Essentially to identify the issue, analyze it, run various commands to get diagnostics and then resolve the issue. And when the identical alert resurfaces, similar mundane steps should be executed again. ‘Sigh! Not again!’ is the usual reaction. And as the day progresses, these alerts slowly snowballs to extreme exhaustion; what we call alert fatigue.

Hear, hear! Are you a DevOps or IT Ops engineer who can relate to this situation? Our philosophy at Botmetric is that humans should solve new problems and machines can solve known problems. So we are on a journey towards NoOps, which essentially means: Say No to solving known Ops problems again and again manually! Automate them so that machines can take care of them.

To this end, Botmetric is delighted to announce the launch of Incidents, Actions, & Triggers app as part of its Ops & Automation product. By using Incidents & Triggers flow, DevOps and IT Ops engineers like you can automate remediation for known operational problems in your infrastructure and use intelligent automation for handling and assuaging alert fatigue.

Above all, Botmetric Incidents, Actions, & Triggers pulls off the complete life cycle of an alert, starting from collection to correlation to the actual execution of a diagnostic or remediation action on the impacted infrastructure. And all this automatically without any human intervention so that your precious engineering time is saved. And that you can spend more time on all things rip-roaring rather than all that humdrum.

Why Botmetric built Incidents, Actions, & Triggers?

Botmetric Incidents, Actions, and Triggers was built to solve five major problems:

1. Alert Deluge

Often, monitoring alerts and event notifications are in the form of an email, and arrives in hundreds, sometimes thousands in full flamboyance looking all red. Some of the common reasons for this avalanche of alerts is improper configuration of alerts and noisy hosts sending too many events.

2. Spot critical alerts/problems from noise

Sometimes alerts are a precursor to an imminent problem. There is no easy way out to quickly run analytics on these alerts to sieve the real issue from the noise out there. It’s critical you prioritize the severity of an alert. And among the deluge of alerts, it is natural you’ll be piqued by the time you figure out the most critical ones. Moreover, you would have spent precious time when a notification pops out in your inbox or Slack. There is no shortcut to determine the problem or critical alert quickly, without using intelligence.

3. Manually solving same problems over and over

It might also so happen that any known issue could be recurring on the same machine, time and again. Resolution to this could be as simple as checking the specific service/system utilization and restarting a service. However, precious human and engineering hours goes wasted in doing this manually each and every time!  In a worst case scenario, it could be a false alert and no action is actually needed but you still have to read the alert, login into the system, and verify the context to determine it’s not a useful event. Until Botmetric built its Ops & Automation’s Incidents app, there was no automated way of debugging or resolving such problems.

4. Dealing with multiple monitoring systems, a necessary evil

Often multiple systems are used for monitoring, log management, APM, API/URL checks, etc. And every monitoring system has its own semantics for metrics and alerts. The same alert may appear differently in different monitoring systems. The need of the hour is to correlate these alerts across monitoring systems to give a unified view to the engineers and DevOps.

5. Identifying recurring alerts

Monitoring systems send out multiple alerts and event notifications, one for each of the monitor/metric. However, more often than not, these alerts are related as the underlying problem. For example, low disk space may lead to a process getting hung or a CPU spike. Such scenarios make it difficult to correlate these alerts and get to the root cause faster. If an alert or event is not useful, then you shouldn’t be bothered.

How to Leverage Botmetric Incidents, Actions, & Triggers to Assuage Alert Fatigue

1. Integrate your monitoring systems with Botmetric

Integrate your existing monitoring systems like Datadog, NewRelic, and Cloudwatch with Botmetric Ops and Automation, so that the Botmetric Agent can pull the alerts from there and collate them in one place for further machine analysis.

2. Setup Actions and Triggers for Incidents

Once the monitoring systems’ integrations are in place, you can start reviewing all the alerts and events. These alerts and events correlated for a particular host are classified and grouped together as Incidents by the Intelligent Correlation Engine (ICE). The primary reason being: reducing alert fatigue. With Incidents, you need to scout through lesser alerts rather than browsing through hundreds or thousands of alerts.

The correlated Incidents can be resolved by the engineer manually through an acknowledgement after reviewing it or Botmetric automatically resolves it after 48 hours of inactivity.

Embark on a NoOps Journey: Mitigate Alert Fatigue with Botmetric Incidents, Actions, & Triggers

3. Create Actions

Botmetric provides a way to execute a set of actions for handling your alerts based on Triggers. You can add scripts or a program with set of commands to handle your alert/event. For example, script (check-thread-restart-apache.sh) can be written to handle APACHE alerts that checks the number of Apache worker threads and restarts the Apache web server if the number of threads is greater than a desired threshold or MEMORY usage goes beyond 75% of the system capacity.

Or a script can be written to enable log rotate if DISK usage is close to 90% of the capacity and push the old logs to S3 for automatic archival.

4. Deploy Triggers

A Trigger is a IF-THIS-THEN-THAT (IFTTT) Job for handling alerts based on a criteria, to deploy diagnostics or remediation scripts that are created using Actions. For instance, you may want to automatically execute the above mentioned script check-thread-restart-apache.sh when a CPU high alert occurs then check IF CPU usage is say more than 90%. Similarly, you can also setup a Trigger to be executed automatically on a high disk usage alert. This will eliminate the need for you to review alerts every time and handle all known operational problems with intelligent automation.

You can also set up a job to trigger automation actions in response to alerts from different monitoring systems. You just need to define what action to take when a particular metric goes above a threshold on the selected hosts using Trigger workflow.

5. Review the status of all the Alerts

Whenever Botmetric receives an alert, it checks if there are one or more workflows that match all the user defined criteria to deploy a response for that alert. If there are any workflows that match these conditions, then the Action will be executed on the impacted servers or cloud infrastructure without any engineers intervention.The status of the Actions executed are available in the Execution History.

To Wrap Up:

As a DevOps engineer, take control on how you manage a deluge of alerts thrusted upon you. Stop investing precious time and effort in identifying, analyzing, and running diagnostic commands to resolve known and recurring alerts. Start your journey towards NoOps with Botmetric Intelligent Incidents, Actions, & Triggers. Reduce the time spent in resolving alerts significantly.  

You can access this app in Botmetric Cloud Management Platform under Ops & Automation. Give it a 14-days try, experience what NoOps is, and write to us with your feedback.Until our next blog post, do stay tuned with us on Twitter, Facebook, or LinkedIn for other interesting news from us!

Top Five DevOps to NoOps Trends to Watch in 2017 and Beyond

2017 will be an exciting year for DevOps engineers. The astounding rise of containers, microservice architectures, and proliferation of machine intelligence is helping them solve their everyday problems. To this end, Ops & Automation is much simpler now. And with the fast-moving innovation paradigm that has set in over the years, the Ops community has seen the operational tasks evolving from traditional operations to new age DevOps. Primarily to suffice the need for more  agility and productivity. But with the rise of machine intelligence, another new trend is treading currently: DevOps to NoOps.

In the words of Botmetric CEO Vijay Rayapati, “NoOps is a logical progression of DevOps with the philosophy: Humans should solve new problems and the Machines should solve known problems!”

Vijay adds, “NoOps is an era of using intelligent automation for your operational tasks so you can eliminate the need for humans to manage operations, save precious engineering time, and solve known problems. As machines can make decisions on known problems and can provide diagnostic information for the new problems to reduce the operational overhead for engineers.”

Here’re the top five DevOps to NoOps adoption trends that every cloud engineer should know:

1. Serverless Programming: This programming and deployment paradigm will significantly eliminate the DevOps requirement for provisioning and configuration management. The cloud world will only see a growth trajectory for NoOps movement as all cloud vendors mature their serverless offerings.

2. Containerization: The containers like Docker will further abstract the dependencies and resource sharing between different components by leveraging cluster management and orchestration solutions like Kubernetes, Mesos, ECS, Nomad, etc. to provide a common view of underlying infrastructure.

3. Microservices Architecture: It will help engineers and companies to decouple the complexity of monolithic systems into small yet manageable components handling specific responsibility. As containerization becomes standard way of deploying components in the cloud, it will see rapid adoption.

4. Intelligent and Unified Operations: Static tooling with (no intelligence) is slowly growing on to the engineers and getting on their nerves To this end, there has been a  rise in the use of machine intelligence, and increased adoption of deep learning. Consequently, the industry will see more adoption of dynamic tooling that can ultimately help them in day-to-day operations.

5. Self Healing and Auto Remediation: Earlier, DevOps world was limited to build, deployment and provisioning while the day-to-day operations were handled in a manual or semi-automated fashion. Now it’s about time, engineers embrace NoOps where machines can resolve known, repetitive problems and engineers can solve new problems.

To delve further deep into DevOps to NoOps trends, read the post by Botmetric CEO Vijay Rayapati, where Vijay will throw light on the details of all the five trends shaping the cloud world in 2017 and beyond.

Which other technologies do you think will trend this year in the cloud arena? Do drop in your thoughts in the comment section below or tweet to us at @BotmetricHQ.

Editor’s Note: This exclusive blog post is an adaption of the original article, The 2017 Cloud Trends: DevOps to NoOps, penned by Botmetric CEO Vijay Rayapati.

The January Roundup @ Botmetric: Solidifying DevOps with NoOps on the Cloud

The first month of 2017 at Botmetric has ended on a good note. We launched one of most sought after feature every DevOps engineer on the cloud seeks to have it: Alert Analytics.

Plus, we have been contemplating more around how DevOps and NoOps on private cloud looks like in 2017 and beyond. We spoke about how DevOps drives cloud more than ever. Likewise, the DevOps community, for long, has been speaking about the emergence of NoOps. Especially around continuous software delivery, continuous security, and high-end business contribution.

But there seems to be a lot of confusion among the DevOps community, as most DevOps guys believe ‘NoOps’ is an Utopian paradise; and more so it is a threat to IT operations and would downsize the resources-in-line. However, the fact is NoOps is just minimizing the amount of time spent on Ops by a DevOps guy. To give a perspective to it, we spoke about what NoOps is through the eyes of a DevOps engineer.

Besides to further help the DevOps community, Botmetric is conscientiously working on improving its Ops & Automation product around it, to further define the future of cloud computing.

Alert Analytics: A new feather in the Botmetric’s cap

Enhancements are an essential part of growth. This month, Botmetric product engineering team took cloud management a notch higher with the release of Alert Analytics in its Ops & Automation product.

What is it about: Managing operational email alerts generated by systems  

How will it help:  It provides DevOps engineer with a bird’s eye view of all the system generated email alerts from multiple monitoring systems like DataDog, NewRelic, etc., and detects anomalies across a cloud infra, thus helping manage alerts.

Where can you find this feature on Botmetric: In Ops & Automation.

Know more about it on this blog post.

Knowledge Sharing @ Botmetric

Botmetric published several blogs to help make your cloud management a breeze. Do check out some of the trending blogs posted on Botmetric this month.

Cloud Computing in 2017: An Op-Ed From the Cloud Geeks

Know the trends that will reign cloud computing in 2017: Microservices, NoOps, Serverless Computing, Machine Learning, and more.

Blue Whale Docker on AWS as CaaS, and How Enterprises Can Use it!

Docker Datacenter (DDC) on AWS as Container-as-a-Service (CaaS) is changing the delivery process of containerized application among the enterprises; and Docker wants to make it easy to set up internal CaaS operations. Know more.

7 Blind Spots to Watch Out for in Your Public Cloud Strategy

Public cloud, today, is all about driving business innovation, agility, and enabling new processes & insights. And for this to happen, a practical public cloud strategy is the cornerstone. A strategy that is based on your own unique landscape and requirements while also taking all the critical blind spots into account. Read this blog to know these top blind spots.

11 Hard-Won Lessons We’ve Learned about AWS Auto Scaling

AWS Auto scaling, even though one of the powerful tools leveraging the elasticity feature of public cloud, it is a double-edged sword. Because it introduces higher level complexity in the technology architecture and daily operations management. Without the proper configuration and testing, it might do more harm than good. So, we’ve collated few lessons we learned over a period – to help you make the most of Auto Scaling capabilities on AWS.

5 AWS Tips and Tricks to Solidify your EC2 and RDS RI Planning in 2017

Almost 92% of AWS users fail to manage EC2 and RDS Reserved Instances (RIs) properly, thus failing to optimize their AWS spend. An effective AWS cost optimization excise starts with an integrated RI strategy that combines a well thought out AWS EC2 and RDS planning. To this end, we have collated top 5 tips and tricks to solidify your EC2 and RDS RI planning. Besides, we’ve an exclusive cloud engineer’s guide for you. This guide demystifies RIs, and covers all the pro tips & tricks and best practices one need to know to make successful RI planning that helps save thousands of dollars. Grab your free copy now.

There are many more insightful blogs populated on public cloud and cloud management at Botmetric. Do read them here.

Rain or shine, Botmetric will continue to provide many more AWS cloud management features. And, if you have not caught-up with all the 2016 AWS re:Invent announcements, we have a cheat sheet ready for you. Until the next month, stay tuned with us on Twitter, Facebook, and LinkedIn.

By the way, have you rated Botmetric, yet? Rate it now.

The Perspective: NoOps Through the Eyes of a DevOps Engineer

What is NoOps for a DevOps guy? If you ask a coder, he/she will be whip-smart enough to tell it is something about ‘No Operations.’ And if you ask a DevOps engineer, you would have evoked several emotions in him/her. Few say it’s automating everything underlying the infrastructure, and few counter argue saying not everything can be automated; it just involves stuff that minimizes few steps in the IT operations.

Whatever the case, few experts say, NoOps is a progression of DevOps.

What NoOps means to the IT industry:

Several research companies, who have been following several IT Cos fro decades, have come up with their own version of NoOps definition. Tech Target defines it as a concept where an IT environment can become so automated and abstracted from the underlying infrastructure that there is no need for a dedicated team to manage software in-house. Which means: No dedicated team will be required for operations while the application development team can itself manage operations.

On the other hand, Forrester defines NoOps as “the goal of completely automating the deployment, monitoring and management of applications and the infrastructure on which they run.”

Adrian Cockcroft from Netflix, in one of his blogs, mentioned that the Platform-as-a-Service (PaaS) will produce lesser needs for operations which in turn gives rise to NoOps culture.

So many versions, and so many ideas, out there. Phew!

What NoOps means to the DevOps fraternity:

For many, who take the literal meaning of it, perceive that with NoOps there shall be no operations whatsoever and that a system will start, manage, report and repair resources in IT infrastructure by itself.

And for a hard-core DevOps engineer “NoOps is a progression of DevOps.” For this engineer, it is just a process that minimizes Ops tasks by 10-15% and thus helps free-up a developer’s time for more innovation.

In other words (or from the eyes of a DevOps engineer), NoOps means performing DevOps with lesser Ops involvement. And that some parts of processes of DevOps will still be used for it.  So, both are no much different. This is why, it is seen as a progression of DevOps. Similar to how DevOps was a progression from IT Ops.

Lucas Carlson, CEO of Appfrog, once said, “SysOps is blu-ray but NoOps is streaming. Blu-ray is going to be around for a long time and there is a strong market for it. There will be people wanting to play Blu-ray disks for decades to come. But streaming is a generational shift.”

The last word: NoOps is a progression of DevOps

The ultimate vision of NoOps is to free-up developers’ time to further utilize their time for more innovation. Whatever you perceive it is: zero Ops, Ops controlled by bots, eliminating Ops workforce, Artificial Intelligence (AI) Ops, or more, it is a rolling stone with the right momentum.

What is your take on this? Do share your thoughts below in the comment section, or on any of our social media pages Twitter, Facebook or LinkedIn. Do read the Botmetric blog post on Alert Analytics to see how Botmetric is driving cloud management with NoOps capabilities.