Operations | Monitoring | ITSM | DevOps | Cloud

Latest News

Five worthy reads: Keeping a close eye on cybersecurity while working remotely

Five worthy reads is a regular column on five noteworthy items we’ve discovered while researching trending and timeless topics. This week, we highlight the importance of creating and enforcing a solid cybersecurity strategy for employees who work remotely.

Rancher 2.4 Enhances Security with CIS Benchmark Scanning

Editor’s note: Rancher Labs’ William Jimenez provides an introduction to CIS Scan. Then Saiyam Pathak takes over with a hands-on demo. Cluster security is critical to any successful Kubernetes strategy. Recent research by AimPoint revealed that 44 percent of respondents had delayed application production due to security concerns around Kubernetes containers. Yet securing Kubernetes is a complex machine with many moving parts, integrations and knobs and levers.

Best ergonomic home office setup tips for remote workers

I’m into my third week of working from home and I’m starting to feel it. My back is playing up, my neck and shoulders are tight, and my legs are getting increasingly more restless. My make-shift remote work setup consists of a little desk and a dining table chair. Not exactly the ergonomic home office setup the health and safety department would recommend. Everyone is working under different circumstances, but we all want to be as productive as we can. Some of you may still be in an office.

How to monitor multiple Azure subscriptions in a single dashboard

In a typical enterprise, there would be multiple Azure subscriptions managed across various tenants. Each tenant would have multiple subscriptions for respective environments. This blog focuses on managing the multiple Azure Subscriptions with Serverless360. Let us take a simple scenario to have a better understanding of how Serverless360 overcome the challenges faced in the Azure portal with the help of Composite Application.

Granular Control Over Scale-Down For Mission-Critical ECS Services

Managing highly efficient ECS clusters requires balancing between overprovisioning, which drives costs up, and underprovisioning, which result in performance issues and pending tasks. Fortunately, Ocean by Spot provides ECS users with an automated, serverless experience. Its proprietary autoscaler leverages just the right blend of type, size, and lifecycle of container instances, for an optimally utilized cluster.

This is why you should use content checks with all your web monitors

Do all your synthetic monitors include a content check? Why not? Content checks are free with all our monitor types, but for the most part, Uptrends users underutilize content checks. In this article, we talk about why content checks are important for your monitoring, and we touch on some tips to help you pick the content checks that work best for you.

Remote pair programming: Tips, tools, and how to measure

Remote pair programming is an Extreme Programming (XP) methodology which is a part of the Agile software development model. It takes the principle of pair programming to the remote workplace. Pair programming leads to higher quality code and fewer bugs by making continuous code reviews and synchronous collaboration possible. In traditional pair programming, two programmers sit side by side in front of the same computer.

SQL Server, Part 1: Why you should monitor SQL logs

Over 44 records are stolen per second every day due to data breaches, and according to the Risk Based Security Research report published in 2019, databases are the top most targeted assets for malicious actors to exploit organizations’ confidential data. Often, organizations don’t realize their databases have been compromised for months. Once sensitive data is leaked, the damage can’t be undone.

Ride Down Into JavaScript Dependency Hell

Every JavaScript project starts ambitiously, trying not to use too many NPM packages along the way. Even with a lot of effort on our side, packages eventually start piling up. package.json gets more lines over time, and package-lock.json makes pull requests look scary with the number of additions or deletions when dependencies are added. “This is fine” — the team lead says, as other team members nod in agreement. What else are you supposed to do?