Operations | Monitoring | ITSM | DevOps | Cloud

Did you know Halloween isn’t the only event in October ready to send shivers down your spine? Each year, October is “National Cybersecurity Awareness Month” in the U.S. and “European Cybersecurity Month” in Europe. So, before we dress up as ghosts, vampires, or whatever, let’s have a quick look at some old and new cyber risks to be aware of and how to deal with them.

You can take a wide range of actions to nurture a culture of cybersecurity in your organization. Some of them can be directed to your employees - and include initiatives like password management and phishing training - and others are related to strategy to adopt towards cybersecurity risk. That's where the NIST cybersecurity framework comes in (as well as other best practices such as CIS controls).

With so many apps to choose from, mobile users no longer have much patience for apps that don’t work well. This isn’t just about bugs and crashes; users also think about how fast the app works and how much battery it uses. But have you ever thought about what would happen to the business if your live applications running on the client’s systems went down or didn’t work as expected?

As Kubernetes monitoring continues to standardize on Prometheus as a form factor, more and more developers are becoming familiar with Prometheus’ built-in query language, PromQL. Besides being bundled with Prometheus, PromQL is popular for being a simple yet expressive language for querying time series data. It’s been fully adopted by the community, with lots of great query repositories, sample playbooks, and trainings for PromQL available online.

As a solutions engineer for FireHydrant, I speak with a wide variety of companies about their incident management programs — from start-ups with a handful of employees to large enterprise companies with thousands of engineers. Whether they’re looking to establish their incident management program or mature it, the same questions remain.

Every millisecond, humans generate significant volumes of data, from various IoT devices such as our wearable devices to daily activities such as internet surfing and tracking our workouts. Data continues to accumulate. Statista estimates that by 2025, the amount of data will have increased to 180 zettabytes. That's far too much information.

Monitoring is an integral part of most organizations. The monitoring process usually consists of several tools that, combined, show you information about whatever you're monitoring - applications, infrastructure, networks and so forth. While monitoring may seem like an obvious practice to some, it can be challenging to establish the best monitoring strategy for your organization.

Back in May, I had the pleasure of joining Michael Daniel, president, and chief executive officer of Cyber Threat Alliance, at the Forbes CIO Summit to discuss creating resilient digital ecosystems without sacrificing agility. In the past two years, we’ve evolved our product development models with a focus on a zero-trust mindset and culture.

In a world of monolithic applications and microservices, responding to incidents can be a painful process, involving multiple people with siloed knowledge jumping between different tools to find the relevant data and take action. Individuals within a business often hold the knowledge of how a particular component works, or how it depends on other services. The key to successfully responding to incidents is unlocking this knowledge and breaking down the silos between teams.

The following guest post addresses how to improve your services’ performance with Sentry and other application profilers for Unity. Learn more about Sentry’s Profiling product or try it out now if you’re already a Sentry user. We’re making intentional investments in performance monitoring to give relevant context to help you solve what’s urgent faster.