Citrix Virtual Apps and Desktops deployments are performance sensitive. There are many components both datacenter-side and client-side which must be optimally performing together to deliver a consistent and performing virtualized apps and desktops solution. With many different components in play, it can often be a challenging task for a Citrix administrator to determine the impact or cause of a Citrix related problem. Citrix troubleshooting nevertheless becomes challenging.
In order to analyze logs efficiently, they must be structured effectively. Often, logs from different sources label data fields differently and/or provide data that’s completely unstructured. The problem is that both types of data need to be structured appropriately in order to key in on particular elements within the log data, such as: Monitoring on source address, Applying rules associated with user names, and Creating alerts for destination addresses.
When logging applications to a centralized location like LogDNA, developers have two options: using a logging agent or using a logging library. Both approaches will get your logs to their destination, but choosing one over the other can have a significant impact on the design of your applications and infrastructure. In this article, we’ll explain the difference between logging via agents and logging via libraries, and which approach works best in modern architectures.
Uptime Robot treats all HTTP statuses equally. They mean either up or down… except HTTP 401. HTTP 401 is expected in some situations and not expected in others. Currently, HTTP 401 is handled as...
On LinkedIn, there are more than thirty thousand U.S.-based DevOps positions. That number may not be as high as it is for software developers, but it’s still higher than sysadmins or systems engineers. Maybe this demand has you interested in switching career paths, or maybe you want to change jobs. If that’s the case, you’re in luck. Today’s post will present some common interview questions that you’ll probably get when interviewing for a DevOps position.
Amazon MQ is a cloud-based, AWS-managed service for the popular Apache ActiveMQ message broker. It offers many advantages of being part of the AWS ecosystem as AWS automatically provisions and maintains infrastructure components from services including EC2 and EBS.
Five worthy reads is a regular column on five noteworthy items we’ve discovered while researching trending and timeless topics. This week, we explore serverless computing and how it can impact business operations.