Operations | Monitoring | ITSM | DevOps | Cloud

It’s a question the Auvik support team receives often: “What’s the difference between packet errors, packet discards, and packet loss?” And if you’ve ever typed that sentence—or any other variation—into Google, you’ll know it’s a tricky answer to find. Until now. Before we break down the three packet terms, let’s first look at packets themselves.

In a recent post, we talked about AWS CloudTrail and saw how CloudTrail can capture histories of every API call made to any resource or service in an AWS account. These event logs can be invaluable for auditing, compliance, and governance. We also saw where CloudTrail logs are saved and how they are structured. Enabling a CloudTrail in your AWS account is only half the task.

Cost is a big reason many dev teams are transitioning to serverless. However, there are still some ways costs can creep up on you in serverless apps. The biggest culprit I’ve found in my own experience is the VPC resource. Because adding a VPC to a serverless stack is ridiculously easy in Stackery, I’ve sometimes gotten carried away. I’d deploy a stack with a VPC for testing, then quickly forget about it.

Bank in Texas enhances their Office 365 service by advanced, real end-to-end user experience monitoring.

Performance is one of those things that most people will agree is super important, but nevertheless tends to get overlooked. In light of that, I wanted to share the approach we recently took with auditing the Grafana product’s performance, and how we went about trying to improve it.

Have you ever wanted to detect a monitoring condition on an agent (Lets call it ProdWebser-01) and follow up the condition with a custom to either remediate the issue or get additional data for the alert? Great Idea, leveraging the agent is one of the best strengths of SCOM.

We’re happy to announce official support for Zeek in Logz.io Security Analytics for easier security monitoring! Logz.io Security Analytics provides a unified platform for security and operations designed for cloud and DevOps environments. It’s built on top of Logz.io’s enterprise-grade ELK Stack and is extremely easy to set up and integrate with.

We are often asked this question – we are monitoring our systems and able to keep their uptime high. Isn’t that enough? Unfortunately that only provides one side of the story. Yes, they are up and resource utilization on them may be well within the limits. But it doesn’t tell us In fact, low resource utilization is very misleading because low utilization also happens when things are stuck waiting on external services response and nothing is processing.

CHAOSSEARCH is building a new standard (a new category) in data analytics. Beyond the cost and complexity of Warehousing, Hadoop, or even Elasticsearch solutions. CHAOSSEARCH is a new kind of big data platform that delivers both search and analytics at a price and simplicity yet experienced. At CHAOS, we are primarily focused on transforming object storage (such as S3) into the first multi-model database, where the user provides read-only access to their S3 storage and CHAOS provides the rest.

For a monitoring service, uptime and reliability is of course a critical feature: customers are placing trust in the service to detect problems and deliver timely and accurate alerts. While I cannot guarantee that Healthchecks.io will absolutely never let you down, I can offer transparency on how it is currently being hosted and operated.