F5 Beacon vs. SolarWinds Pingdom

It is very well suited in complex, multi-cloud application environments where it provides holistic, application-centric visibility by ingesting data from NGINX and other telemetry sources. It helps troubleshoot performance issues in high-availability and regulated environments where outages have a high impact on strict SLAs. It is less appropriate in situations where organizations rely on unmaintained or archived integrations.

I believe the scenarios we used it for were quite well covered, from the executive perspective. The downtime alarms worked very well and were easy to setup, uptime monitoring tools were clear and easy to use, even for non-technical people (C-level) and the SLA management tools allowed us to spend less time, and have less friction, with our clients

Incentivized

• Accelerated troubleshooting and root cause analysis
• Unified application visibility across hybrid environments
• Business level insight & KPI correlation

Incentivized

• The alerts are very responsive offering quite detailed timing information
• The UI for reports is very clear and set up of reports is very intuitive
• Customer service was good when there were problems - e.g. lapsing billing causing reporting to go down

Incentivized

• F5 needs improvement in Platform Stability and Maintenance gaps.
• It has limited built-in insights and relies heavily on customization.
• Application modeling and data ingestion setup is complex.

• The PagerDuty integration could be a lot better. When you use the PagerDuty integration, it doesn't send any information about which check failed! It just sends a message like "Timeout (> 30s)" -- this isn't very helpful when we have hundreds of checks. We've worked around this by using both the PagerDuty and Slack integrations and having them both post to the same Slack channel. But this means that when an engineer is paged from PagerDuty, they have to go to Slack (or Pingdom) to find the details about the page; it's not available on the page itself.

Incentivized

Recently added features have made Pingdom less intuitive for our requirements. While Pingdom has a broad offering and remains a good value, it is becoming more than we need. Our customer base is becoming more and more global and Pingdom still lacks Asia-Pacific monitoring, which we will need within a year.

The reason of giving above rating of 10 is that it offers intuitive, centralized dashboard which reduces the need to switch between multiple tools making it easier for IT teams to quickly assess application health. Moreover it offers easy correlation of technical and business metrics by linking application performance data directly to business KPIs. the major benefit of using Beacon is that it simplifies troubleshooting workflow which reduces Mean Time To Resolution hence improving productivity and minimizing downtime.

Incentivized

Pingdom is easy to use, very intuitive and has a very short learning curve. From the onset, we've been able to jump in and leverage the tool to accomplish our goals for page speed performance and discover the insights we need to make improvements. Its a well-designed tool and makes for a good user experience.

Incentivized

Interface is unnecessarily complicated and frequently responds slowly.

Support responded the same day to my query, as I was setting the product up but couldn't find the setting I needed. This was successfully resolved in a short time frame, so I was pleased with how quickly we were able to get this resolved. I haven't needed to contact support since.

Incentivized

F5 Beacon is best for F5-centric, hybrid, app-centric visibility, whereas Datadog is best for cloud-native, distributed observability. F5 beacon is superior for understanding BIG-IP flows, WAF, ADC behavior at the app level. It has a unified view of F5-powered applications. F5 Beacon simplifies troubleshooting across multicloud F5 deployments. Beacon provides business logic level visibility.

1. PRTG Network Monitor was a far more complicated tool to use and set up albeit it does both Internal and External monitoring. The setup wasn't intuitive and there are too many configuration options to complete to form an alert
2. Amazon CloudWatch is specific to AWS resources and cannot be easily use outside of the AWS Ecosystem

Incentivized

• Positive: Reduced downtime costs
• Positive: Improved IT efficiency
• Positive: Better business-IT alignment
• Negative: Scaling costs in large enterprises.

Incentivized

• Honestly, we have 4 other products that overlap this functionality whose organizations provide far superior support. At this point it is an unnecessary expense.
• In my opinion, their lack of support responsiveness and commitment has impacted our IT agility.
• Its time to explore other alternatives.