Operations | Monitoring | ITSM | DevOps | Cloud

In part 1 of the CLI Stands For…A CLI Into Series, we outline why you would want to use the CLI, some of the benefits of doing so, and a bit of CLI history and terminology. In part 2 – An Introduction to Shell Commands, get ready to roll up your sleeves and dive into a deeper understanding of the terminal.

When designing a solution, you should keep future needs in mind. If the number of users increases dramatically in a short period of time, the solution should be scalable enough to handle the new growth. Making systems scalable on cloud is relatively easier as compared to scaling on-premises infrastructure. AWS has provided excellent tools/services to enable your applications for as much scalability as you want.

AWS currently offers over 200 services. Some of those make up the AWS Cost Management suite. This group comprises AWS Cost and Usage Report (CUR), AWS Budgets, AWS Cost Explorer, AWS Cost Categories, and AWS Cost Anomaly Detection. Budgets and Cost Explorer are an excellent pair of complementary tools in this group. They have similarities that cause users to wonder if they need both and, if so, why. Here is a brief overview of the differences between AWS Budgets and Cost Explorer.

Are you surprised? Are you under where are the first four tips? I start this series of blog posts on my blog, and you can see and read the previous Best practices, Tips, and Tricks here: And I will be sharing some of them here and others on my blog. So stay tuned for both blogs. Of course, the most recurring task is adding comments to our triggers and actions, but it is always good to know you to delete them. Some of you may be thinking that is a trivial task, simple like adding a comment.

Read a blow-by-blow analysis of two of the heavyweights in world of DevOps: when should you bet on Terraform, and what calls for Kubernetes?

One more blog topic stemming from our weekly office hours that we hold with the field team here at Shipa. In our last office hours, was asked a question about “what are the difference between DevOps Engineers and SREs?”. Both professions are emerging disciplines and cultures that continue to evolve and play an importance in technology organizations. I’ve been fortunate to have written and spoken about this before; though taking a fresh look at what the two domains try to accomplish.

To supervise the behavior of distributed applications and track the origin of service failures and downtime, developers often use traditional monitoring technologies and tools. However, this approach can fall short in its ability to measure the overall health of modern cloud-native architectures, which can span multiple hosting environments and encompass hundreds of microservices.

In a perfect world, your Configuration Management Database (CMDB) acts as the single source of truth for all your IT device inventory and the relationships between those devices. However, maintaining accuracy is easier said than done. That’s because the traditional method for provisioning and maintaining a CMDB is complex, unwieldy, and outdated the second it's updated. To keep up with the needs of a modern CMDB, an automated discovery and dependency mapping (DDM) solution is a must.