Our client is one of the biggest oil and gas conglomerates in India, contributing to around 75% of Indian domestic production. They have been in business for over 60 years, currently employing around 30,000 people. With decades of growth, they have entered into different ancillary companies and expanded globally. The expansion has led to several offices, branches, desks, and teams spread across geographies.
Over the past few years, we’ve seen an almost obsession with developing and adopting CI/CD tools throughout the DevOps community. There are thousands of “how-to’s”, “top x tools”, and “tool x vs tool y” type articles, and it has gotten to the point where it’s quite difficult to figure out how and which one to pick as your own.
So, you want to plan a product release? Well, let’s be honest, no one really wants to plan a product release; it’s a complex and exhausting process that requires the buy-in of various people across your organization.
In this blog, we will explore suspicious file activity inside a container and see how to effectively implement a file integrity monitoring (FIM) workflow. We’ll also cover how Sysdig Secure can help you implement FIM for both containers and Linux hosts.
IT is advancing blazingly fast. To keep up with architectural changes and hybrid environments, it’s more important than ever to maintain efficient infrastructure monitoring and troubleshooting. Adding to the complexity is the increase of distributed systems, comprised of many components and services.
In the next decade, the world will produce an unfathomable amount of machine data — metrics, measurements, and telemetry data that is emitted from everything from servers to robots and satellites. And the pace of that data generation is increasing exponentially. I wrote in a paper published last year how this data is a virtually untapped source of extraordinary business insights — data so dense and rich it will dwarf traditional business intelligence in terms of its potential value.
Like everyone else, my life for the last few months has become a never-ending stream of video calls. With Zoom calls, and the occasional Skype, Google Meet, or Microsoft Teams, becoming the norm I’ve noticed that the fans on my Macbook have been kicking in and sounding like a tiny jet trying to take off.
In Kubernetes, Ingress objects define rules for how to route a client’s request to a specific service running inside your cluster. These rules can take into account the unique aspects of an incoming HTTP message, including its Host header and the URL path, allowing you to send traffic to one service or another using data discovered in the request itself. That means you can use Ingress objects to define routing for many different applications.
