Operations | Monitoring | ITSM | DevOps | Cloud

A few months ago, I was asked if I wanted to develop an open-source Terraform provider. Eleanor Saitta, principal at Systems Structure Ltd, had a client who was setting up JFrog Xray across their Github repositories but didn’t want to configure each repository by hand. As an SRE who enjoys working on projects that automate away those sorts of pain points (and someone who works extensively with Terraform during their day job), this sounded like an interesting project to work on.

Over the past year, we have witnessed remarkable changes brought on by our response to a global pandemic. Along with accelerated digital transformation and the consumerization of technology, Covid-19 has birthed the everywhere workplace, where users work with any device, to connect to business-critical systems and applications. Work has become something you do rather than a place you go.

Serverless computing is one of the fastest-growing areas in software development, along with hybrid clouds and using multi-cloud strategies. The global serverless architecture market is expected to grow at a CAGR of 16.2% in 2021 through 2026. It will reach $10.29 billion from $4.2 billion in 2020, according to MarketWatch. The serverless approach promises to help developers beat the cons of self-managed and even virtual server infrastructure. But is serverless right for you?

In our previous blog post on Windows access tokens for security practitioners, we covered: Having covered some of the key concepts in Windows security, we will now build on this knowledge and start to look at how attackers can abuse legitimate Windows functionality to move laterally and compromise Active Directory domains. This blog has deliberately attempted to abstract away the workings of specific Windows network authentication protocols (e.g., NTLM and Kerberos) where possible.

Last week DevOps Institute’s Chief Ambassador, Helen Beal, and Moogsoft’s own Chief Evangelist, Richard Whitehead, continued to follow the exploits of DevOps Engineer Sarah and her journey towards AIOps and Observability enlightenment.

In this video with with Kohsuke Kawaguchi (KK) from Launchable and Viktor Farcic we talk about testing K8s applications. Do we really need to write all the tests every time we make a change to the source code or make a release? That could take minutes or even hours. Wouldn’t it be better to run only the tests related to the changes we are making or the phase of the lifecycle of an application? Is the future of testing in AI and ML?

It’s more critical than ever to secure your company data and protect your workloads in the cloud. This blog post is a roundup of the latest technical resources and product capabilities by both Google Cloud and Splunk to enhance your threat prevention, detection, and response techniques, regardless of where you are in your business-transforming cloud journey.

IP address conflicts are an example of textbook “network problems”. There are multiple causes for IP conflicts, and, to make things even more fun, the behavior of devices experiencing an IP conflict can vary. Let’s explore IP conflicts in depth to help better understand what they are, why they occur, and how to fix IP address conflicts. An IP address conflict is a common network issue that occurs when two or more devices on the same network have the same IP.

Every IT environment is different. Some depend heavily on an efficient reactive support team, others need to manage a totally decentralized workforce, while some focus their resources on an infallible security and compliance team. Whatever your IT ecosystem looks like, you need to make sure you are taking into account the things that matter most to you, your IT department and your business at large.

In today’s complex IT infrastructures, Dynamic Host Configuration Protocol (DHCP) servers play an indispensable role in automating IP allocation and configuration. A DHCP server’s capacity to allocate IPs to the requesting clients in real-time is one of the factors that ensures constant uptime of dynamic networks. However, even though a network’s availability depends on them, DHCP servers are often not closely monitored by IT teams.