Today, we're introducing a new major feature: monthly site reports. In such a report, you got a bird's eye summary of everything we know of a site in a particular month. We've gone the extra mile and added the ability to mail these reports to people outside of your team automatically. If you're an agency and manage sites for your clients, you could use this feature to send a monthly report of all broken links to your client. In this blog post, we'll tell you all about the feature.

Back in October, we announced the Splunk OpenTelemetry Collector Distribution, which offered the industry’s first production-ready support for OpenTelemetry. This distribution is the recommended way that customers of Splunk’s award-winning observability products capture metrics and traces.

Splunk Phantom 4.10 introduced many new enhancements, including the ability to develop playbooks in Python 3. In fact, Python 3 is now the default for Splunk Phantom playbooks. In doing so, we needed to create two different “playbook runners” to ensure we could continue to support playbooks written in Python 2.7 while also supporting Python 3.

Many of us get sentimental about past projects we’ve worked on…for me it is a mobile dashboard that leveraged ML/AI to help a sales team make quicker decisions while in the field (nerdy, I know…but it was one of my first projects as a UX Designer when I was starting out my career, and I have many fond memories about this project). For many members of the team at Grafana Labs, that sentimental project is worldPing.

High-level information and speedy configuration for the busy network administrator. If you want to respond to network issues quickly and promptly, you can’t waste time digging for information. So how can Flowmon 11.1 help?

‍Today we’re excited to be rolling out a completely redesigned Sleuth experience. Our new Command Center provides one place to visit so developers can quickly and safely deploy new changes. ‍

We often hear that our customers love using Splunk, know the power behind our platform and want to expand usage to IT. But they aren’t sure what steps to take first. We want our customers to maximize their Splunk investment and get them jump-started with Splunk for IT use cases by providing the guidance and best practices they seek.

It’s January 2021 and you’ve probably broken five out of six New Year’s Resolutions. I don’t want to be the reason for breaking your last one, so I’ll cut right to the chase. We just released an update to our JavaScript SDK with the ability to track the health of your releases and support for Web Assembly. Still with me? Great.

Incidents are inevitable, and the reality is some of them are inevitably going to repeat themselves. FireHydrant has always strived to make the entire incident response lifecycle smooth, but up until today, common incident types were slightly burdensome for our customers. We decided it was time to help people make it easy to declare incidents using easy-to-use templates, which we’re deeming Incident types.

We’re happy to announce the release of AppSignal for Elixir 2.1.0. 🥳 In this version, we’ve made our error helpers more flexible than before. You could already send Elixir exceptions directly through AppSignal and now you can add extra metadata to errors when using send_error/2-4. Let’s go through all of the changes 😀