Operations | Monitoring | ITSM | DevOps | Cloud

When you’re new to an industry, you encounter a lot of new concepts. We tend to use a lot of jargon, the documentation may be written with someone more experienced in mind or rely on contextual knowledge of the rest of the space, and it often doesn’t explain the “why” for the tool. This can make it really difficult to get your feet underneath you on an unfamiliar landscape, especially for junior engineers.

As software is the product in many of today's businesses, the need to manage the value stream from development to production is critical to ensure consistency of information, compliance and supply chain collaboration.In order to consistently deliver high velocity and quality of applications, engineering teams require visibility into how code is moving from dev to prod in a stable and efficient manner. Just as Observability is changing the way teams managing their applications in production, the concepts of observability apply to the entire software value stream.

In this session we’ll review networking options compatible with Calico for AKS cluster and will build a few AKS clusters using Azure CLI and ARM template.

Learn about the three pillars of observability and how they help you seamlessly carry out your IT operations.

Here are some tips that you can implement to enhance and optimize the your IT infrastructure.

Red Hat OpenShift is a great platform for hosting microservices, enabling developers to get up and running quickly. However, taking the next step from development to production imposes additional networking, security, and compliance requirements that must be addressed before Kubernetes apps can be widely deployed. Traditional networking tools, which were designed for relatively static IP environments, don’t have the context necessary to identify Kubernetes traffic flows, making it nearly impossible to effectively diagnose, troubleshoot, and resolve application connectivity issues.

A short demo of how you can use GitLab CI/CD pipelines to push a package to a private Cloudsmith repository.

Learn the importance of monitoring the end-user experience and the ten tips that will help you int he monitoring process.

When looking at a Traceroute, there's usually two important values for each hop or router: Latency Packet Loss Latency: Refers to the time difference between the time when a packet was sent and when a response was received. The latency between two hops can be affected by a number of things such as: To qualify the latency in a traceroute as good or bad, you should analyze historical traceroutes.

View Video