Operations | Monitoring | ITSM | DevOps | Cloud

The need for automation is becoming more important day by day. The process of integrating written code with already working code and publishing new code to live environments is a very error-prone process. Performing static analysis, running tests, packaging, and versioning are tasks that require a lot of manual effort. It’s also a complex task to solve the problem of deploying the projects we develop to more than one environment, on more than one machine, without automation.

It is the time of the year when we revisit our carefully written 2024 New Year resolutions list and frown at how we could not stick to it religiously. Letting the everyday demands of life and work get in its way. It isn’t amusing to realize we are not committed to our boldly written, heartfelt intentions. However, if you are a networking professional, we have the good news. You can ace your job as well as carve out the ‘me’ time to pursue your 2024 resolutions.

With the number of wireless SoCs on the market, “Just add connectivity” is finally a reality! “Just” does a lot of lifting in that phrase. Connectivity, whether wired or wireless, adds numerous layers of complexity to your device. Treating your connectivity as a black box early in development is easy, but this strategy will implode when thousands of devices enter the field - trust me, I know. It’s not enough to test from end to end a few times in the office.

Cloud computing has made provisioning new servers easy, fast, and relatively cheap. Almost anyone can log into a cloud console, spin up a new server, and deploy an application. And if they need greater uptime, major cloud providers include all kinds of settings, services, and configurations to add fault tolerance and failover. So why is it that many services fail when a single server instance fails?

We’re thrilled to announce that Mattermost has earned the 12th annual DEVIES Award for Best Innovation in ITOps! The award — given to a platform “responsible for acquiring, designing, deploying, configuring, and maintaining the physical and virtual components that comprise IT infrastructure” — was presented on Feb. 21 during DeveloperWeek 2024 to our very own Director of Product Marketing Amanda Cheong and Developer Advocate Andrew Zigler at the Oakland Marriott City Center.

A couple of years ago, I wrote another blog on how Oracle Cloud Infrastructure (OCI) Object Storage can be used as a data lake since it has an Amazon S3-compliant API. Since then, I’ve also fielded several requests to capture logs from OCI Services and send them through Cribl Stream for optimization and routing to multiple destinations. There are two primary methods to achieve this.

Single sign-on (SSO) is an important security function for many business enterprises, especially with the rise of more cloud apps and services. Essentially, an SSO allows a user to log into a device only once with a single set of credentials to gain access to a variety of corporate apps, websites, and data.

As devs, we know the age-old question of, “How long do you think it will take?” oh too well. Regardless of experience and position within the development cycle, this inquiry always comes loaded with expectations and complexities, a concept I refer to as Speed to Delivery Time (SDT). To be clear, SDT isn’t just about marking days on a calendar.

In the early 2010s, Apache Hadoop captured the imagination of the tech community.

Rocky Linux is a community-driven, open source operating system that is backed by CIQ, the primary sponsor and support provider. This OS is a powerful alternative for those seeking a downstream, binary-compatible option to Red Hat Enterprise Linux (RHEL). CIQ supports Rocky Linux as a response to changes in the CentOS project, which is no longer maintained as a stable downstream clone of RHEL.