A new User Account option, Operator, has been added. The Operator role is similar to the Viewer role (read-only user role). The Operator role can only view data in the system and cannot make updates, however, the Operator roles has two additional privileges: Postponing monitoring for a device, Silencing alerts, ...
Humankind was made to desire success. Everybody wants to be successful. Everybody wants to see successful results of their work. Same at work when you are on a project, same at home when you are trying to make a delicious meal. And the most satisfying feeling afterwards is when you get appreciated, which always is not the case at first couple of trials.
Today’s economy has created a new class of worker: the IT consultant. This lone warrior often manages multiple websites, responding to anything from outages to update requests and every code debug in between. If one can manage the never ending onslaught of servers, API calls and transactions these sites rely on each day, it’s a pretty decent living. The key is removing all the menial work that overwhelms and stifles productivity.
At the intersection of safety and performance, you’ll find Rust — Stack Overflow’s “most-loved programming language” for three years running. Rust provides the control needed to ensure optimal performance while offering relatively high abstractions at zero-cost.
I use performance monitoring tools primarily to find slow and buggy code. At the start of development, I typically use the tools more for finding software bugs. Once the codebase is at a relatively stable phase, then I shift my focus toward finding less performant code. Which is why I turn to tools like Retrace to help with profiling for better performance.
Traditionally in white-box monitoring, error reporting has been achieved with third party libraries, that catch and communicate failures to external services and notify developers whenever a problem occurrs. I’m here to argue that for managed services this can be achieved with less effort, no agents and without performance overhead.
As containers and orchestrators have surged in popularity, they have created highly dynamic environments with rapidly changing workloads—and the need for equally dynamic ways of monitoring them. After all, orchestration technologies like Kubernetes, DC/OS, and Swarm manage container workloads both at the node level and at the cluster level, which means that you need to gather insights from every layer to fully understand the state of your infrastructure.
Source maps are awesome. Namely, because they are used to display your original JavaScript while debugging, which is a lot easier to look at than minified production code. In a sense, source maps are the decoder ring to your secret (minified) code. However, they can be tricky to get working properly. If you’ve run into some trouble, the tips below will hopefully help you get everything in working order.
Service level objectives are an important tool for maintaining application performance, ensuring a consistent customer experience, and setting expectations about service performance for both internal and external users. We are very pleased to announce the availability of a new monitor uptime widget that makes it simple to monitor the status of your SLOs and communicate that status to your teams, executives, or external customers.
It is not uncommon to have multiple monitoring solutions for IT infrastructure these days as distributed architectures take hold for many enterprises. We often hear from Google Cloud Platform (GCP) customers that they use Stackdriver to monitor resources as well as Grafana and Prometheus for container monitoring. We’ve heard lots of requests from customers to be able to view Stackdriver data in Grafana effortlessly.
