Operations | Monitoring | ITSM | DevOps | Cloud

Over the last several years, systems architects have had to make sure their systems are cloud native, with applications that are optimized for scalable cloud technology infrastructure. In today’s environment, you should be asking whether your solutions are cloud nimble as well. For the modern enterprise, cloud computing is now the default model for applications, storage, and compute.

Continuous integration (CI) and continuous delivery or deployment (CD) cover the process of automatically merging, building, and testing code changes ready for release, and – in the case of continuous deployment – releasing those changes to users. If you’re developing software for others to use, you’ll need to go through some form of build and test process before you make your latest changes available.

Ask any software engineer about the best way to do something and they’ll likely tell you “it depends.” Every project and team works differently and has specific concerns, requirements, and opinions, adding complexity on top of the technical and operational complexity of software development. The challenge lies in managing the work and emergent complexity while staying abreast of industry best practices in a way that fits our teams’ particular processes and environments.

Here at LogicMonitor, we’re really big on extensibility and automation. We’re constantly adding to our catalog of monitoring coverage and ensuring that setup is as simple as possible. We also monitor almost any data you can expose on a network. People have done way more with LogicMonitor than we would have ever imagined, and I’m extremely excited to announce our next step in that commitment to extensibility and automation.

The success of your enterprise’s digital transformation relies in no small part on your hybrid cloud infrastructure, which SearchCloud Computing defines as “a cloud computing environment that uses a mix of on-premises, private cloud and third-party, public cloud services with orchestration between these platforms.” Because this infrastructure is not a homogeneous environment, migration, management, and optimization can be an ongoing challenge.

As we kick off the new year and our release of Shipa 1.5.0, dabbling in the art of the possible, what if it was possible to provide your developers with a single line of configuration to get their ideas into production. Shipa is an application and policy abstraction layer which easily integrates with your DevOps toolchains.

When you work in tech, there are certain truths about the holiday season you can always count on. For example, you’ll be holding your breath up until New Years waiting to see if deals will come across the line. The end-of-year planning you intended to have done by December 31, will inevitably bleed into January. And, without a doubt, you’ll spend your holidays trying to explain to your relatives what exactly it is that you do.

There are many benefits to working with JFrog Artifactory as your private Docker registry, allowing you to store, share and deploy your binary artifacts in a single source of truth. This blog post will focus on using Artifactory in Kubernetes. Specifically, we’ll walk through the steps for configuring Kubernetes to pull images from Artifactory and most importantly – scale up! It will also describe how you can enable cluster-wide authenticated access to Artifactory behind the scenes.