Since we launched Grafana Mimir — the most scalable, most performant open source time series database in the world — we have answered many of your questions about our latest open source project, including how to pronounce it. (All together now: /mɪ’mir/.) We have also walked through how we scaled Grafana Mimir to 1 billion active series.
As the Azure cloud administrator, you need to know who is accessing your cloud resources, how they are access it, what they access, what changed, when they access and from where, etc? Azure AD (Azure Active Directory) provides answers to above by storing the information in two logs, the information stored in them is extremely valuable for troubleshooting, monitoring and for general security related work, the logs are.
When you’re troubleshooting an issue, finding the root cause often involves finding specific logs generated by infrastructure and application code. The faster you can find logs, the faster you can confirm or refute your hypothesis about the root cause and resolve the issue! Today, we’re pleased to announce a dramatically simpler way to find logs in Logs Explorer.
Resource Public Key Infrastructure (RPKI) is a routing security framework that provides a mechanism for validating the correct originating autonomous system (AS) and prefix length of a BGP route. Route Origin Authorization (ROA) is a cryptographically signed object within the RPKI that asserts the correct originating AS and prefix length of a BGP route. For as long as the internet has existed, the challenge of securing its underlying protocols has persisted.
Do you know how to improve project transparency? If you are trying to unlock higher levels of team productivity, you need to consider project transparency. When it comes to pushing projects forward and making progress, all key stakeholders must have access to the information they need to effectively complete tasks. Sometimes, it’s impossible to predict what information stakeholders will need to access.
By now, most of us know that migrating workloads to the cloud isn’t like simply moving software from one server to another—especially in a complex enterprise infrastructure with many interdependent services and components. There are a lot of things that can go wrong: technical public cloud provisioning issues, security and compliance challenges, lack of cloud skills, wrong public cloud service provider (CSP) selection, unexpected costs, and more.
The phone rings. Your email pings. Your marketing team just told you about a flood of messages on social media and through live chat that there’s a service outage. You thought your Monday morning would be calm and relaxed since people are just returning from the weekend. How do you start researching all of these incoming tickets? How do you know which ones to handle first? Is this just a hardware failure, or are you about to embark on a security incident investigation like Log4j?
For DevOps teams, delivering quality software has long required reconciling a major tension: In a perfect world, you’d catch every issue in each new release of your application before you deployed the release into production. But in the real world, doing so is tricky, not least because it’s hard to collect data about application performance before the application is actually deployed.
In the present age of cloud-native everything, it can be easy to forget that some applications still run on-premises. But they do and managing the performance of on-premises apps is just as important as monitoring those that run in the cloud. With that reality in mind, here’s a primer on how to approach on-premises application performance monitoring as part of a broader cloud-native performance optimization strategy.
