Complex problems can often be solved with simple, practical solutions. That’s what our team at Kenshoo discovered when we realized that we needed a way to easily and proactively track specific log messages which indicate mission-critical events.
Support for relational databases is a growing focus for Kubernetes users, and the release of Windows Server 2019 is expanding options for .NET applications and SQL Server. SQL Server workloads, however, often rely on Active Directory and Windows Auth, and storage arrays, which will not be supported by SQL Server containers on Windows Server 2019. Fortunately, a new Rancher Labs partner, Windocks, offers new options for SQL Server on Kubernetes and Rancher.
We are delighted to welcome guest blogger Brian Wren of Microsoft. Brian is something of a superstar in the SCOM world – and you will see why when you check out his technical guides on TechNet or Microsoft Learn. His series on Management Pack Authoring for SCOM is a definitive guide that has helped many of us get started with a difficult topic. It is fair to say that when Brian works his magic, he makes the complicated perfectly understandable.
When adding a new feature to Checkly or refactoring some older piece, I tend to pick Heroku for rolling it out. But not always, because sometimes I pick AWS Lambda.
Manual ticket creation can often be a pain. It’s difficult enough handling the barrage of alerts coming in, let alone opening tickets and copy/pasting their details into these tickets. In this post – we discuss a simple way to ease this pain, and share a video on how to do it.
Our September update improves the assignment of categories to Signl alerts, hence the enrichment and routing of alerts to the right people. Until now, a ‘Services & Systems’ category was assigned to a Signl alert, if at least one of the entered keywords was found in the event content or text delivered to SIGNL4 by email or webhook. This basically represents a logical ‘OR’ operator for this keywords search.
