Operations | Monitoring | ITSM | DevOps | Cloud

As I’ve often talked about before, we have a “big tent” philosophy at Grafana Labs. We believe our users should determine their own observability strategy and choose their own tools; Grafana allows them to bring together and understand all their data, no matter where it lives. In practice, that means that we want to support data sources that our users are passionate about.

Get started with Gremlin's Chaos Engineering tools to safely, securely, and simply inject failure into your systems to find weaknesses before they cause customer-facing issues. API gateways are a critical component of distributed systems and cloud-native deployments. They perform many important functions including request routing, caching, user authentication, rate limiting, and metrics collection. However, this means that any failures in your API gateway can put your entire deployment at risk.

Passwords are dying. The cost of creating and maintaining passwords is becoming untenable. Which can be seen in the rise of users logging in with social products and developers outsourcing their pain to Auth0 and the likes. We decided to sidestep the password based authentication and went passwordless on our new product. Read on to see how you can go passwordless too.

When it comes to conversations around application architecture or working with integrations between applications, you’ve likely heard a couple terms pop up a few times: microservice and APIs. You might also have run across the common misconception that microservices are just a way to implement APIs so they can communicate with each other. As you’ll see in this article, there are alternative ways to architect our microservice applications.

Sales engineers play a significant role in bridging the gap between internal teams and customers. This shared services team has product experts who possess a sound technical background and a deep understanding of customer expectations. With that, they support several business functions like Sales, Customer Service, Research and Development, and so on. Sales engineering professionals can wear many hats because of their in-depth understanding of the products and the business itself.

'SCOM is here to stay'. Please read the following extract from an article written by Richard Benwell, CEO at SquaredUp. Gartner predicts that 30% of Enterprise IT spending will be on cloud and outsourcing by 2023. That’s 70% spending on non-cloud and outsourcing – the in-house infrastructure and software we have today. And if you’re running traditional Windows and Linux workloads at scale, SCOM remains the best tool on the market.

For those who have been keeping up with our series on IT Service Management (ITSM) beyond IT, welcome back! If you’re new to this conversation, it isn’t like a podcast where I’ll send you back to part one, but you may find it helpful to visit the previous recommendations for other internal service providers. Reflecting on 2020, we saw how powerful collaboration in the service desk could be in maintaining users’ productivity and achieving broader business goals.

It’s important to ensure the logging and monitoring of a service is as consistent across environments as the code itself. However, it can be expensive and cumbersome to test the logging functionality with the usual required log exporters, database infrastructure, and processing requirements of normal production-grade solutions.

Our product and engineering teams have spent a significant amount of time over the past year working on a new dashboard experience in SentryOne® Portal to give you the upper hand in monitoring your servers and diagnosing performance issues. Providing control over the way data is displayed is one of our most requested features, and we’re excited to satisfy this request with custom charts.

Sweating IT assets, ever heard of them? It might seem nonsensical to imagine an IT asset perspiring from being overworked, but it’s actually not a far-off analogy. When a business delays the purchasing of new technology as long as possible, it’s called ‘sweating assets.” Companies have their reasons for this strategy, but it usually comes down to one thing: an attempt at cost-savings. Do sweating assets actually help to achieve this and where do they miss the mark?