Operations | Monitoring | ITSM | DevOps | Cloud

When you work in IT, there’s never a shortage of things to do. For folks who like to be busy, IT is a great place to be. But the workload can quickly become overwhelming, and it may often feel like you and your team are putting out fires and not productively working on other tasks that move the needle for your team or company. The trick is managing your team’s time effectively so the excessive pile of work gets done. These four time management strategies can help. Let’s get started.

Frequent logouts are a frustrating experience for users, especially on servers with short session lengths configured. In v5.24 and later, you can enable the configuration setting for extending session length with activity to automatically extend sessions and keep users logged in as long as they are active in their Mattermost apps.

Many Mattermost DevOps teams work in “Microsoft Shops”—organizations that use Office 365 apps with the Microsoft 365 business plan—and want to tightly integrate with Microsoft tools to more easily collaborate with the rest of the company. Mattermost E20 was architected from the ground up to be highly flexible. As such, integrating with other platforms including Microsoft is easy. Here’s how.

Recently, Atlassian announced 12 new features to help improve collaboration across software teams. These new capabilities and some help from Sentry & friends aim to help developers spend more time building the products and services their customers want. Here’s a more detailed look at how Sentry integrates with Atlassian products and leverages Bitbucket’s new Code Insights feature.

Usually, organizations use an internal network to prevent unauthorized people from connecting to their private network. By using their own network infrastructure and connectivity, they can maintain their desirable level of security for their data. But it would be convenient for users to connect to that private network while they are away from the office through their own internet connection.

Jira has long been a popular issue tracking tool for development teams, but its scope has broadened quite a bit over the years, and it has bloomed into a more well-rounded project management tool as well. It’s used widely by agile teams to plan, track, and release software, along with numerous other cloud (and traditional self-managed) productivity tools.

Many of you may be reading this blog from home, a remote office somewhere, a family member’s house, or—if Zoom backgrounds are to be trusted—the cockpit of the Millennium Falcon. We’re all learning how to get better at “working where we are,” and that includes optimizing the tool stack you use each day.

Are you currently using Flux with InfluxDB? Have you written a great Flux function that would be useful to the community? If the answers to these questions are “Yes!”, then I encourage you to contribute your awesome work to Flux, so that others can appreciate you and your work. Today, we’re sharing how you can contribute a custom Flux function in a Third Party Flux Package.

Amid concerns of resource scarcity and increasingly complex resolution processes, service desks are constantly under pressure to deliver more with less. This, in effect, forces service desk managers to drive technicians to resolve requests faster, leading to an unhealthy obsession with numbers. Several service desks are known to regard the number of requests closed by technicians as a good yardstick for their performance.