Operations | Monitoring | ITSM | DevOps | Cloud

MapR is an Apache Hadoop distribution that enables organizations to manage, analyze, and store all their data at scale. MapR handles a wide range of data types across infrastructures and locations by leveraging dataware, an abstraction layer in the enterprise software stack that separates data from any dependencies. We’re excited to announce that our new integration provides comprehensive visibility across all the moving parts of your MapR deployment.

Rojan Australia Pty Ltd is a managed IT services provider that supports a wide assortment of customers and businesses, and provides services such as hosted Microsoft Exchange, Xen Citrix servers, rack space, internet links, and desktop support.

Our second day at Ignite was busy busy as usual! We’ve gotten into the full swing of things now with the demos, presentations, customer briefings and LEGO giveaways. As expected, sessions we attended today were Azure focused, with an emphasis on proper (and hybrid) monitoring, cloud migrations, and new tech like Azure Arc.

Building dashboards that show real-time streaming data and allow for interactive queries is challenging. At the recent InfluxDays conference in San Francisco, Ryan McKinley, Grafana Labs VP of Applications, discussed new approaches to integrate real-time data into Grafana dashboards. Prior to joining Grafana, McKinley worked at a renewable energy startup, Natel Energy, which builds hydropower turbines. There, he used Grafana and Influx to display an overview of how the systems were working.

To get an accurate picture of the current state of Kubernetes deployments, Rancher Labs recently conducted an industry survey that included 1,106 respondents from large and small enterprises across a broad range of more than 25 industries, including technology, financial services, telecom, education, government and healthcare. The respondents were almost evenly split among EMEA and North America and included both Rancher and non-Rancher users.

More than a decade ago, a small piece of code that would eventually be called Sentry was born. When I wrote this code, I didn’t know much about open-source, so when it came down to licensing, I just grabbed the first reasonable suggestion thrown my way. That suggestion happened to be the BSD 3-Clause License. Fast forward to today, and a lot has changed.