The third and last week of GrafanaCONline starts today! We hope you’re able to check out all of our great online sessions. If you’ve missed any sessions (or want to watch them again), the videos are available on demand here. Here’s what’s coming up today...

Boom! Our latest release of the AppSignal for Node.js package now includes support for Next.js. The Next.js integration also includes end-to-end insights into application performance, as well as error tracking.

Amazon Web Services (AWS) has a suite of tools that help application development teams enhance and streamline their work experience, from the backend to frontend services. LogicMonitor consolidates data from these services and empowers users to monitor them side by side with the rest of their infrastructure, whether it’s in the Cloud or on-premises. Keep reading for tips on monitoring some of these services to ensure business continuity.

With SCOM 1802/1807 reaching end of life earlier this year and with SCOM 2012 R2 Mainstream support over (at the end of 2017), many of you are looking at your SCOM upgrade options. So what options are there?

Management Packs contain the actual monitoring (the workflows themselves) as well as extend the SCOM platforms functionality and are critical to getting your new SCOM Management Group up and running. The good news is most of SCOM Management Packs that worked with SCOM 2012 R2 work right through to SCOM 2019, so you are safe to import them into your new Management Group.

If you know which MPs your overrides are stored in, then migrating your current effective tuning is as easy as exporting all of your override MPs, and then importing them into your new SCOM Management Group, assuming you have already imported the MPs containing the monitoring itself. As you also know, in most SCOM deployments, this is never reality across the board.