Operations | Monitoring | ITSM | DevOps | Cloud

A huge challenge when dealing with incidents is the coordination and communication needed to put things right. What’s happened so far? Who has tried what query? Did we remember to keep stakeholders informed? What is the severity of the incident? Does this affect customers? Figuring this out requires a lot of back and forth as new team members join the incident.

It’s an exciting day at Sysdig as we announce our channel-first approach to doing business. What does this mean exactly? Going forward, we will be conducting sales for all customers outside of the Global 500 through a channel partner. For more than three decades, customers have leveraged channel partners as trusted advisors for vendor-agnostic IT consultation and expertise. Our channel-first approach moves Sysdig in line with how customers buy.

The temptation with synthetic user journeys is to create a single, long running journey that checks everything in one go and run it every 5 minutes. This may sound like a good idea because one journey is cheaper than five or because there’s fewer scripts to maintain, but it will make your life much harder and is likely to still cost as much due to the total time it takes to run. Therefore a good approach to user journey monitoring is to create atomic journeys.

Fluentd is an open-source data collector that unifies data collection and consumption. It has different types of plugins that retrieve logs from external sources, parse them, and send them to log management tools like Site24x7 AppLogs. tail, forward, udp, tcp, http, syslog, exec, and windows_eventlog are common input plugins.