Incident response has been the cornerstone of reliability for decades. From digging in the server logs to navigating modern observability dashboards, responding quickly to incidents and outages is a big part of minimizing downtime. And it should be! When something breaks, your team should move as quickly as possible to address and repair the problem.
Data can be overwhelming. The purpose of this blog is help you sift through data to find exactly what you need to use it in a meaningful way when solving Citrix problems. After working in performance benchmarking and analysis, one thing I noticed is only the really really big companies have full-time staff dedicated to doing analysis on a daily basis. Which means, it’s up to the generalists, or Jacks and Jills-of-all-trades, to review data and make sense of it. How does one do this?
Flowmon is not a stand-alone system used in isolation. It is part of an ecosystem of monitoring and security tools used across the enterprise. Recently, we have introduced new integrations with Splunk and ServiceNow to simplify interoperability and enable IT and security teams to be more efficient. This is a good opportunity to remind of all the integration options and resources we have.
From Robocars to Reliability — SRE with self-driving cars; mapping out where the Observability space is in conjunction with self-driving cars.
This is the second post in the series about building email templates with MJML and deploying them on AWS. In the previous post, we learned about MJML and Handlebars.js for creating cross-browser email templates with dynamic content. In this post, I will show you how you can script the building process of MJML emails and prepare them for upload on AWS. Let's do a quick recap. In the previous post, I created a simple mail template in MJML.
