Operations | Monitoring | ITSM | DevOps | Cloud

Logs from a variety of different AWS services can be stored in S3 buckets, like S3 server access logs, ELB access logs, CloudWatch logs, and VPC flow logs. S3 server access logs, for example, provide detailed records for the requests that are made to a bucket. This is very useful information, but unfortunately, AWS creates multiple .txt files for multiple operations, making it difficult to see exactly what operations are recorded in the log files without opening every single .txt file separately.

Elasticsearch and the rest of the Elastic Stack are commonly used for log and metric aggregation in various environments, including Kubernetes. In addition, the Elastic Stack is frequently being used for uptime tracking, with Heartbeat, as well as Application Performance Monitoring (APM), with agents supporting common programming languages, including Java.

This article originally appeared in TechBeacon. Gartner first coined the term "AIOps" a few years ago to describe "artificial intelligence for IT operations," and over the last few years, IT operations monitoring tool vendors have begun incorporating AIOps features into their products. Now AIOps tools are commonplace, but many IT leaders remain cautious about using these relatively new capabilities.

Standard operating procedures—more commonly known as SOPs—are written, step-by-step instructions that describe how to perform a routine activity. While you can create an SOP for anything, SOPs that outline technical procedures are a well-known path to increasing efficiency in your MSP business. Whether you’ve got existing SOPs you’re interested in updating, or you’re looking for some basic steps to build brand new SOPs around, you’ve come to the right place.

January is a good time for bug-fixing and we've spent the last couple of weeks making small tweaks and improvements to Downtime Monkey. We've focused on the kind of bugs that aren't urgent but shouldn't be overlooked and aim to continue this for a couple more weeks before starting development of the next major feature. We'll document each change in its own post. First up is an improvement to the range of webpages available for monitoring: webpages with query strings can now be monitored...

In the olden days, we used to have to get logs by putting our agent on one machine at a time, like hitching a horse to a horse-drawn carriage. But now, we’ve got Kubernetes. It’s like a horse factory, and we’ve got more horses than we know what to do with. In this wild west of containerization, we could quickly end up underneath more logs than our old-timey agent could keep track of! But now there’s a new sheriff in town.

AWS has a lot of services, and they all generate logs. A lot of logs. We’ve worked hard to make sure you can capture logs from every source and service on AWS, and today we’re happy to announce the final piece of our AWS logging puzzle: LogDNA’s S3 Collector integration. It’s an easy-to-use Lambda function that lets you ingest any AWS logs that get dumped to S3 – like logs from CloudFront and ELB.

Industry 4.0 technology is transforming industry all over the world. Digital innovations such as data, virtual reality, automation, and robotics are all helping brands create products and services and deliver them to customers in better and more efficient ways than ever before. One of the most useful elements of Industry 4.0 technology comes from the Internet of Things.

In order to determine the health and current state of your systems, monitoring by its very nature requires access to internal and external services. Traditionally, users have had to get creative in terms of how they expose sensitive information (secrets, like access credentials) to their monitoring tool; operators typically would leverage local environment variables or give up entirely by putting secrets in the monitoring configuration.

This is the one post I hope you’ll never need. However, should you ever need it, this is your one-stop shop for understanding how to proceed with DevOps incident management. Have you just been attacked? Did the commit go wrong? A CI pipeline went haywire? Don’t worry. I got you.