We software engineers like to think ourselves unflappable. Consider that we spend most of our days staring at glowing pages of eldritch horror that no mortal was meant to witness. We whisper and type our otherworldly incantations, all the while feeling the hungry gaze of a lurking cross-site scripting bug, or a shadowy use-after-free, or an accidental summoning of ZALGO. (H̨e̛ ̕c͢om͢es, you know.)
If our end users end up too long for a query to return results due to Elasticsearch query performance issues, it can often lead to frustration. Slow queries can affect the search performance of an ecommerce site or a Business Intelligence dashboard – either way, this could lead to negative business consequences. So it’s important to know how to monitor the speed of search queries, diagnose and debug to improve search performance.
Migrations carry a setup cost and engineers don’t work for free. Even under the most ideal conditions, it’s possible moving data between web monitoring providers will result in some missing feature or differing functionality. That’s just life. If you’re facing a migration you sometimes have to make do with the cards you’re dealt. But it’s not all doom and gloom! We hope this checklist will help you play like you’ve got pocket aces.
HAProxy provides an easy and straightforward way to add HTTPS to your website. As a load balancer positioned in front of your web servers, it can handle all of the encryption and decryption duties, offloading those tasks from your upstream servers. That’s good because in today’s age of privacy awareness, the consensus is that every website must implement HTTPS, regardless of whether sensitive or private information is being exchanged.
A lot of engineers think a project is done once the code is live. In a perfect world, that could be true—alas, commits are rarely free of problems. For companies that have a lot of focus on dev but little on ops, this can quickly turn into a nightmare. Fortunately, there are a lot of infrastructure monitoring tools out there that can help marry DevOps and keep your apps, websites, and processes running smoothly.
We are about to install and manage Argo CD through a CD pipeline. “Why would we do that? We can just as well accomplish that through a command like kubectl apply or helm upgrade --install.” I’m glad you asked. The primary objective of Argo CD is to help us apply GitOps processes when deploying applications. It is directing us towards the world in which everything is defined as code, and all code is stored in Git.
If you are a part of an engineering organization it is highly likely that you have heard the latest buzz words “containers”, “docker” and “kubernetes”. Today we will try to demystify these terms for you. Sit tight, it's going to be very interesting.
Telehealth use has become a prominent and preferred method of patient care since the COVID-19 outbreak. What happens though when technology becomes a barrier to adequate care? For example, your Electronic Health Record (EHR) Telehealth application is working too slowly or is randomly disconnecting. This not only looks bad to the patient trying to meet with the physician, but it makes it impossible to deliver a quality patient experience.
This post will help you write effective Snort Rules to materially improve your security posture. We’ll begin with a breakdown of how a Rule is constructed and then explore best practices with examples in order to capture as many malicious activities as possible while using as few rules as possible. Snort is an open-source network intrusion detection system (NIDS) that provides real-time packet analysis and is part of the Coralogix STA solution.
