Operations | Monitoring | ITSM | DevOps | Cloud

The onboarding experience sets the tone for a new developer — beyond the interview process, this will be the developer’s first impression of the company and the job. The onboarding process should be thoughtfully designed and should give the developer the tools they need for success and autonomy. Before you start crafting your onboarding process, think back to your first few days at the organization.

This need for AIOps was simmering conveniently and gradually reaching its threshold when the pandemic suddenly hit the world, pushing organizations into remote work. The sudden, global-scale change raised challenges for IT operations teams to monitor and detect incidents in a distributed environment and maintain cybersecurity and compliance. While the pandemic pushed some organizations into the reality of remote work, others were already on their way to digital transformation.

Put simply, managing incidents—big or small—is good for business. Not only is it a regulatory requirement, but also a factor in your profits. Your customers expect smooth operations, good customer service and protection. A dedicated incident management tool can help protect all of these. While many may think of incidents as an IT or DevOps issue, it’s hard to over emphasize that they can happen in any department.

As we get ready to wish the term SASE a happy 4th birthday, it seems odd that there is still a great deal of confusion in the market about what SASE really is and how it relates to a ‘Zero Trust’ architecture. For many, SASE is a framework for secure network design; for others, it’s seen more as an architectural approach to delivering Zero Trust. So why do we have this confusion when Gartner defined SASE back in 2019?

A security bill of material (SBOM) is an inventory of the entire building components of a software application. These components include open source libraries, dependencies, commercial components, licenses, patch status, version information, upgrades available, CVEs, etc. Having an SBOM of a codebase or piece of software provides deep visibility into core components that help quickly identify and mitigate the security and licensing risks associated with the software supply chain.

No matter what application you’re building and who your target customers are, everyone can agree that it’s critical to avoid broken deployments. To aid in this goal, many tools and concepts have been invented, with Kubernetes preview environments being one of them. In this post, you’ll get a deeper understanding of how preview environments work, how organizations are using them, and how you can get started yourself.

A neatly setup access control telling which user can do exactly what on an incident management platform can save a lot of time and hassle in the future. In the past, Spike.sh had only 2 roles - Admin and Member. The only difference in these roles were that only Admins can remove members. It was fairly simple and most users liked it. However, with larger teams coming onboard, it gets a little difficult to control for admins. So, we have empowered the existing system by adding two more roles.

The primary DNS server hosting a zone or multiple zones acts as an authoritative DNS through which DNS administrators manage zone files and perform DNS changes like adding, deleting, and updating DNS records.

Managing your own time series database is painful. We’ve moved from servers to services, and yet, monitoring metrics data is primitive. Our managed time series database powers mission-critical workloads for monitoring, at a fraction of the cost.