Operations | Monitoring | ITSM | DevOps | Cloud

Covid fundamentally disrupted the modern workplace in a way that no technological innovation ever has. Yet despite the initial acceleration of digital transformation initiatives, we’re still burdened by the legacy of the “old way”— work about work. According to the Anatomy of Work Index, an average employee switches between 10 tools up to 25 times per day. This level of app switching makes it challenging for team members to prioritize and execute work.

In modern software systems, it is common for several developers to work on the same project simultaneously. Siloed working with infrequent merging of code in a shared repository often leads to bugs and conflicts that are difficult and time-consuming to resolve. To solve this problem, we can adopt continuous integration.

Last year we cooked a holiday ham using Sysdig. Honestly, just revisiting that makes me hungry, but it got me thinking. What about dessert? Today, I’d like to discuss baking a pie and eating it with Prometheus Remote Write. But not just any pie: a Raspberry Pi. Specifically, I’d like to introduce you to Pi-hole, an open-source project that has become very popular in the community. In this article you’ll learn how easy is Monitoring Pi-hole with Prometheus Remote Write.

Qovery is a continuous deployment platform. Users deploy apps of all kinds, written in any language and framework they choose. The freedom users have come with a cost for the Qovery core team - the broad scope Qovery has to cover, makes it harder to make the deployment process stable and straightforward for everybody. It's easy to create a service focused on just one language or framework - supporting all of them requires considering many more factors.

Every now and then, issues occur that disrupt the very fabric of global software engineering. Chief amongst them is the recent mass outage of Github. Github is a fundamental building block in software productivity, hosting over 190 million code repositories. Github hosts our code and libraries, runs build pipelines, and much more. It is a central hub of activity and it is consumed by tens of thousands of organizations.

At Seniorlink, we provide services and technology to support families caring for their loved ones at home. In the past two years we’ve expanded our programs across the United States, and so our need to observe our application systems has grown too.

Sometimes it makes sense to switch your RMM vendor. For example, if your services have evolved to new requirements or you know there’s a good vendor who can really help your business. But I often see MSPs consider it for the wrong reasons. They think they’ll find a silver bullet in the next technology solution, not realizing their technology issue may actually be a deeper business issue. This is where having an MSP vendor who truly treats you as a partner can matter.

In March 2021, Microsoft announced Operator Connect, a new way for organizations to connect Microsoft Teams to a telecom provider. From an enterprise buyer’s perspective, Operator Connect delivers a new “apps store” type of experience to enable organizations to choose a telecom provider and connect Teams users to the PSTN from the Teams admin center. Equally important, Operator Connect enables a new set of menu-based user configuration tools within the Teams admin center.

In the last few months, we have been working on a new Apps framework for developers. The idea behind this framework is to make it easier for more developers to integrate external applications or their own applications into Mattermost. But wait a moment, don’t we have Plugins for that? Yes, but Apps provide some advantages to developers over Plugins.

Most everyone has some source of information on the health of their environments. Your experts know where to go and what to do when you get those cryptic messages and log files. To those content with the deep knowledge and where events and log files supply you with everything you need, I applaud you – you belong to a rare breed. Combing through logs or events takes time and effort, and rarely does it yield the speediest “return-to-service” solution.