What is Pingdom?
Who uses Pingdom?
Here are some stack decisions, common use cases and reviews by members of with Pingdom in their tech stack.
Alerts when/if site goes down. Pingdom
Observes the Azure WebSites and keeps the Azure WebJobs up and running. Pingdom
RUM, uptime Pingdom
Basic uptime and response time monitoring of site Pingdom
Server/Website monitoring Pingdom
Here are some stack decisions, common use cases and reviews by companies and developers who chose Pingdom in their tech stack.
We currently monitor performance with the following tools:
- Heroku Metrics: our main app is Hosted on Heroku, so it is the best place to get quick server metrics like memory usage, load averages, or response times.
- Good old New Relic for detailed general metrics, including transaction times.
- Skylight for more specific Rails
Controller#actiontransaction times. Navigating those timings is much better than with New Relic, as you get a clear full breakdown of everything that happens for a given request.
Skylight offers better Rails performance insights, so why use New Relic? Because it does frontend monitoring, while Skylight doesn't. Now that we have a separate frontend app though, our frontend engineers are looking into more specialized frontend monitoring solutions.
Finally, if one of our apps go down, Pingdom alerts us on Slack and texts some of us.
Platform Update: we’ve been using the Performance Test tool provided by KeyCDN for a long time in combination with Pingdom's similar tool and the #WebpageTest and #GoogleInsight - we decided to test out KeyCDN for static asset hosting. The results for the endpoints were superfast - almost 200% faster than CloudFlare in some tests and 370% faster than imgix . So we’ve moved Washington Brown from imgix for hosting theme images, to KeyCDN for hosting all images and static assets (Font, CSS & JS). There’s a few things that we like about “Key” apart from saving $6 a month on the monthly minimum spend ($4 vs $10 for imgix). Key allow for a custom CNAME (no more advertising imgix.com in domain requests and possible SEO improvements - and easier to swap to another host down the track). Key allows JPEG/WebP image requests based on clients ‘accept’ http headers - imgix required a ?auto=format query string on each image resource request - which can break some caches. Key allows for explicitly denying cookies to be set on a zone/domain; cookies are a big strain on limited upload bandwidth so to be able to force these off is great - Cloudflare adds a cookie to every header… for “performance reasons”… but remember “if you’re getting a product something for free…”
#Datadog #Relay42 #Monitoring
With Datadog unveiling their Synthetics product (https://www.datadoghq.com/blog/introducing-synthetic-monitoring/), we at Relay42 are considering moving out of Pingdom.
The rationale is simple:
90% of our monitoring is on Datadog, apart from the external requests. It'd be nice to identify regional issues in one place, so this is great in our monitoring consolidation efforts.
The lack of a non-community Terraform provider for Pingdom
We have yet to get in the beta and test it out but we feel very excited about this announcement.
Since we don't like uptimes below 100%, we want at least to be notified when this thing happens. Pingdom
We use Pingom to monitor the availablility of our own and customer's services Pingdom
We use Pingdom to ensure that our internal monitoring services are operational. Pingdom
- Uptime & Response time reports
- Multi-step transaction monitoring
- Email, text & twitter alerts
- Multiple check locations
- Root cause analysis
- Public and email reports
- Monitor that your websites and servers are working- Pingdom tests your websites and other infrastructure components as often as every minute to make sure it is all up and running.
- Be the first to know if something breaks- When an error occurs, you can get alerted via email, text (SMS), Twitter, or a mobile notification to your Android and iOS device.
- Easily spot trends in your performance- The results of all tests that we perform are saved, and we use that data to create graphs of your site's historical uptime and performance.
- When it breaks, find out why- If an issue occurs with one of your sites, we use additional tests such as a traceroute to help you find out where the problem is.
- Identify broken and slow website interactions- Monitor parts of a website like the login, search, check out, or other user interactions that are important to you.
- Use it wherever you are- You can use our mobile apps for Android and iOS to view report data and the current status of your sites while on the go.