JIT Access, sometimes referred to as just-in-time provisioning or just-in-time privileged access management (JIT PAM), is a security strategy that grants users access privileges for limited time periods. Access is granted on an “as-needed” basis. For example, if a developer requires access to a specific platform for a week or as part of an on-call access to production duty, a JIT Access system can provide that access and automatically revoke it after the time period ends.

One of the biggest challenges observability teams face today is gaining end-to-end visibility into their cloud native apps, including modern browser frontends. Without that visibility, you potentially open the door to bad end-user experiences that can hurt customer satisfaction, reduce search engine discoverability, and interfere with overall business goals. This is the exact challenge we address with Grafana Cloud Frontend Observability.

As part of our recent failure testing project, we ran into an interesting failure mode involving the OpenTelemetry SDK for Go. In this post, we’ll show you why our apps stopped sending telemetry for over 15 minutes and how we enabled keepalives to prevent this kind of failure from happening in the future.

Application Performance Monitoring (APM) tools are essential in software development landscape. As applications become more complex, ensuring they perform optimally has never been more critical. APM tools allow developers to monitor, diagnose, and optimize applications, ensuring a seamless user experience. In this article, we'll explore the top 10 APM tools available today, highlighting their features, pros, and cons to help you make an informed decision.

Whether an enterprise operates in technology, healthcare, financial services, or another business vertical, cybersecurity must remain top of mind. In addition to the numerous international cybersecurity regulations, like the NIST Cybersecurity Framework, GDPR, and other mandates, enterprises must also prioritize cybersecurity to mitigate downtime, protect sensitive data, and uphold customer trust and brand reputation.

Monitoring used to be so easy. Servers had names and lived down the hall, or across the street. If things weren’t working, you could turn them on and off again. Database filling up? Just throw another hard drive in there. Too many simultaneous requests? Rack another server and install a cache. Fast forward a couple decades, and things have gotten much more complicated.