Extending uptime monitoring with POST, PUT & PATCH methods
Next to our standard uptime monitoring through GET requests, we've added support for POST, PUT & PATCH methods too.
Next to our standard uptime monitoring through GET requests, we've added support for POST, PUT & PATCH methods too.
At Grafana Labs, we field questions about best practices from customers all the time. One company recently asked whether it should run a containerized Prometheus environment rather than a VM-based one. We thought we’d share our answer here too. So: Should you run Prometheus in a container?
To make your application monitoring easier, we’ve built a tighter integration between AlarmsOne and Applications Manager. AlarmsOne already has a Poller-based integration with Applications Manager; however, now it has a webhook integration that will have you receiving alerts in a jiffy.
The OpManager Standard Edition is an intuitive, flexible network and server monitoring solution developed especially for small and medium enterprises (SMEs). If you have big IT management goals but you are held back by a tight IT budget, the Standard Edition is the way to go.
Uptime Robot provided 2 api-key types: a master api_key and monitor-specific api_key. The master api_key can be used to perform almost every action exists in the dashboard and it must not be revealed for the security of the accounts.
This past week some of the Scout team had the opportunity to hang out at PyCon USA in Cleveland. This was the first time the Scout APM team had attended PyCon. It was great to spend some time with an awesome swath of the Python community. With a great booth location situated across the aisle from the innovative and fun Slack booth, we had fun getting to know everyone with a solid amount of traffic heading past our booth over the exhibition days.
This article is a follow up of our previous article where we explain how we deployed a Kubernetes cluster with k3s on a Raspberry Pi cluster.
Some time ago, the Register published an article titled “Lambda and serverless is one of the worst forms of proprietary lock-in we’ve ever seen in the history of humanity”. It received a lot of attention, and vendor lock-in has become a perennially popular question at conferences. But I’m here to tell you that you are probably thinking about vendor lock-in all wrong when it comes to serverless.
These days we spend a lot of time talking about modernizing our stack, modernizing our architectures, using new application components, modern application life cycles, etc. So, what is this all about and why do we spend so much time talking about it? First, there is a lot of self-serving vendor speak involved…starting with cloud providers and closely followed by open source commercialization shops and commercial ISVs (ourselves included) who have to spin the world in their own image.