Operations | Monitoring | ITSM | DevOps | Cloud

Just launched: Push notifications via Pushover. Get outage and recovery alerts on all your devices, wherever you are... It's already weekend. Which means time away from the keyboard, and hopefully less screen-time from our always-around electronic devices. You don't want to go to dinner wondering if your online services are up and running, and also you might want to tone down the number of times you check your email. That's why we added the missing link to our alerting system.

Performance is not something you should compromise on, and it's important to have a healthy development process that improves as your application grows. If your PHP application is not super-fast, it will be much harder to scale and maintain. You need to identify errors in the early stage to fix them as soon as possible. And if you don’t know where your bottlenecks are, you can’t fix them.

As the complexity of software systems explodes, so does the amount of data that gets generated by instrumenting these systems. This poses a problem for our users — especially those who are in charge of observability teams and observability platforms at large enterprises. They have to strike the right balance between cost management and giving teams the freedom to instrument whatever they want. Often observability leaders are supporting dozens of teams that are using hundreds of dashboards.

JWT stands for JSON Web Token, is a famous technology that comes with its own controversy. Few people find it quite beneficial, while others feel one must never use it. Nonetheless, in this article, we shall discuss the reason behind this controversy, understand JWT in detail, and when and why one must use it. We'll cover the following section in this blog. JWT (JSON Web Token) authentication is a process or method used to verify the owner of JSON data.