It’s 3 AM and your phone is ringing. Rubbing your eyes, you take a look at the alert you just got from PagerDuty. A critical service has just gone offline. Angry customers are calling support. Your boss is on the phone, demanding the issue be resolved ASAP. You open up your log management tool only to be faced by 5 million log messages. What now?
In this post, you’ll learn which metrics to keep an eye on to improve your application performance, how AppSignal works, and how to interpret the data it generates. Grab a stroopwafel, make yourself comfy, and let’s start!
For most organizations, software development is team-driven. Good communication—messaging—is crucial to working together as a team and, increasingly, for working effectively with the tools used by the team. In recent years, instant messaging has taken over not only social networks, but also the workplace. In many ways, a collaboration tool based on instant messaging is key to collaboration, knowledge transfer, and solid teamwork.
Being innovative is like being handsome. It only counts when others think so. When Bank of America honors you for being innovative and improving how their 30,000 developers perform, it’s a very handsome compliment. At the 11th Bank of America Technology Innovation Summit, JFrog was recognized for industrial leadership and excellence in providing global business solutions. This year, JFrog was one of only two technology companies honored for its strong partnership with the firm.
During the past years we made plenty of contributions to improve the current state of the Windows monitoring. We tried to improve the actual installation with the Icinga 2 Powershell Module, allowing users to easier automate installation and configuration of Icinga 2. On a long term we however wanted to improve the monitoring of Windows infrastructures entirely, by not only providing new plugins but also to increase the contribution by the community.
If you’ve worked on a team that has adopted Agile techniques, you’ve probably heard of a retrospective. If not, here’s the TL;DR: A retrospective is a meeting in which a team connects regularly to reflect on what happens throughout a project and continuously improve how they work moving forward.
TL;DR: Fast-moving IT stacks see frequent, long and painful outages. Thousands of changes – planned, unplanned and shadow changes – are one of the main reasons behind this. Until now, IT Ops, NOC & DevOps teams didn’t have an easy way to get a real-time answer to the “What Changed?” question – the answer that can help reduce the duration of outages and incidents in these fast-moving IT stacks. Now, with BigPanda Root Cause Changes, they do.
If you have anything to do with the world of cloud computing or even programming for that matter, then I’m sure you’ve heard of different terms being tossed around such as “serverless computing” or “containers,” and even “monolithic architectures.” A lot of people who understand such computing methods can have a bad habit of using these terms without leaving any explanation as to what they are.
First time this year, multi-cloud enterprises, as a customer segment of Sumo Logic, have grown faster than any other segment: 50% Y/Y. What took so long? In my conversations with enterprises over the last 5 years, there was only one strategy for public cloud and it was multi-cloud. But evidence of multi-cloud usage was sparse at best. Data from our Continuous Intelligence Report in previous years didn’t find much to support that the strategy for multi-cloud was being implemented.
A Syslog server allows for the collection of logs into a centralized log repository. This centralized log repository allows for quick searching of your logs across your organization through different visualization tools. The Syslog web interface will provide the easiest access to the logs, and allows for easy secured remote access.
