Operations | Monitoring | ITSM | DevOps | Cloud

Our community is more than just helping with questions, sharing experiences and tailoring monitoring together. We’ve grown so much in the past 10 years that we always seek to improve the conversation. You’ve seen our many Icinga Camps, keep following our social media channels, engage with developers on GitHub, read our blog … one thing is gladly missed: Our very own discussion platform which combines a forum with a mailing list and also enables quick chats known from IRC channels.

Back in the days of the wild wild web (www) and post JQuery era, one web framework stood above all others: AngularJS. A “ring to rule them all”, AngularJS consolidated quite a few micro-frameworks and provided many extensibility points of expansion if needed. Over time though, many performance and architectural questions began to arise, to the point of no return – when the guys @Google decided to migrate from AngularJS to Angular (a poor naming decision).

When developing PHP applications, error logs are under-used because of their apparent complexity. PHP error logs are helpful, especially when configured and used properly. While there are advanced tricks to truly squeeze every last drop of utility out of error logs, this article will cover the basics of configuration and the most common use cases so you can get up and running quickly.

Even after being in business for 9 years, I still wanted to keep everything: every email, every note, every design draft or mockup — all the small things that helped Monitive evolve into what it is today. Storage is not an issue these days, and by the looks of where technology is headed, that trend will not change anytime soon. There’s just one catch.

We’ve added more info on the upcoming talks at GrafanaCon LA and are excited to see the schedule shaping up. Grab your ticket while the last and join us February 25-26 for two days of great talks and hands-on workshops. This week we’re happy to share articles on how to view Azure Monitor Log Analytics data in Grafana, a proof of concept to visualize Fitbit data, how to quickly get up and running with Prometheus and more.

There were some big IT headlines this past year. Microsoft acquired GitHub and IBM bought Red Hat. Kubernetes graduated from the CNCF incubator program. And the biggest headline of all—at least to those of us at Datadog, where we live and breathe monitoring—we released Datadog Agent version 6, a completely new monitoring agent written in Go! As we start the new year, we’d like to take a moment to recognize some of the incredible things our engineers accomplished in 2018.

Last week, the LogicMonitor executive staff kicked off a global tour across the LM offices to celebrate 2018 wins and share the company vision moving into 2019. This annual Company Kick-Off event (CKO) remains a strong tradition here at LogicMonitor, allowing team members to celebrate, collaborate and fuel-up for success in the coming year.

Meet Cameron. She’s a product manager at a mid-sized tech company, tasked with the challenge of increasing usage of their mobile app. She knows she’ll need all hands on deck to make this happen. But, previously when she’s set team-wide goals like this, things have quickly fallen off-track.

As you may know, Microsoft SQL Server is a relational database management system (RDBMS) developed by Microsoft. Several industries rely on SQL database servers for data storage and access because it supports a wide range of transaction processing, business intelligence, and analytics applications in corporate IT environments.

One of the biggest challenges Citrix admins face is uncovering answers for Citrix performance issues. When an application or a desktop is slow, people naturally pin the blame on the Citrix infrastructure. It’s possible that there could be issues stemming from the Citrix side of the house, but often the real culprits are the supporting infrastructure components: network latency, virtualization bottlenecks, AD issues, storage hotspots, database issues, etc.