When high temperatures, prolonged drought, and lightning strikes ignited a huge swath of Australia’s wilderness in late 2019 to mid-2020, Australians stepped up in droves to assist with the rescue and cleanup efforts. The New South Wales (NSW) Rural Fire Service (RFS), a government agency under the NSW State Public Sector, was inundated with inquiries and applications from people wanting to join the fight.
FireHydrant captures your incident, from declaration through remediation, and gives you a framework to run your retrospectives. But retrospectives are only as effective as their inputs. Now we're delivering a better way to learn from and analyze retrospectives by guaranteeing consistent, structured, and sufficient data from your team.
GitKraken knows that software development relies on efficiently coordinating with your A-Team. That is why we’ve added a pull requests section, more repo information to GitKraken Workspaces and a new way to organize and share them with your teams in GitKraken Client! As Mr. Keif would say: I pity the tool that doesn’t have the incredible team features included in GitKraken Client v8.4!
Being on call is challenging. It’s signing up to be operating complex services in a totally interruptible manner, at all hours of the day or night, with limited context. It’s therefore critical to have proper on-call on-boarding procedures, offer continuous training sessions, and continuously improve documentation. We also need to make sure people feel safe by providing ways to reduce their stress, and make room for questions to surface all sorts of uncertainties around our operations.
Before we dive into the Collector, let’s cover the components that make up the OpenTelemetry project. If you missed it, our post What is OpenTelemetry gives a high level introduction to OpenTelemetry and the key components of OpenTelemetry project: The OpenTelemetry collector is optional when using a SaaS service like Scout. Even so, knowing what the Collector can do and when to use it is helpful to understand.
