Operations | Monitoring | ITSM | DevOps | Cloud

In the wake of recent events like the SolarWinds hack and the White House executive order on cybersecurity, DevSecOps and security are top-of-mind for most DevOps and security professionals. How to efficiently adapt or adopt a sound DevSecOps practice has become a priority, especially with the U.S. government’s impending mandate requiring software applications to be vetted, and to create a trusted Software Bill Of Materials (SBOM) for each one.

A multi-tenant architecture is essentially a framework in which a common instance of a software application is used to service several client applications or tenants. This multi-tenant architecture has found extensive adoption in SaaS applications, which cater to requests from tens and thousands of clients. The main reason for the adoption of multi-tenancy is the efficient and optimal use of resources and funds, along with delivering seamless service.

We’re happy to announce the release of new muting features for Datadog monitors. Scoped monitor muting allows teams to eliminate unnecessary alerting during scheduled maintenance, testing, auto scaling events, and instance reboots. Your teams will therefore be able to filter out expected events and quickly pinpoint critical issues in your infrastructure. Previously, monitor muting was binary: all-or-nothing.

We are happy to share the v0.3.0 release of Rancher Desktop. This release brings more stability, some new features, and a fresh look to the UI. This screenshot shows the preferences screen while in dark mode on Mac. In the lower left corner the status when performing an action is now displayed. This status will tell you when Rancher Desktop needs to download something, such as a version of Kubernetes you have now used before, or when another step is happening.

If you need your teams to act, you need to alert them where they’re already looking. Yet yesterday’s DevOps practices demand individuals to wrangle with uncorrelated events, multiple UIs, and siloed technologies. Tomorrow’s DevOps must enable teams with: To practice DevSecOps, you’ll need to know where a vulnerable build has been deployed into production, and where to find the corrected build that should replace it.