Cradlepoint in Boise offers the all-inclusive NetCloud Solution Packages for branch, mobile, and IoT networks combine tailored NetCloud services with fit-for-purpose hardware and a comprehensive support plan. NetCloud Solution Packages are cloud-managed and deployable anywhere in days, not months. Cradlepoint acquired the NetCloud technology with original developer Pertino in December 2015, and integrated the platform into their own services by early 2016.
N/A
SolarWinds Pingdom
Score 8.2 out of 10
N/A
SolarWinds Pingdom is a website uptime monitoring and alert tool, with additional reporting and Real User Monitoring capabilities. Pingdom is part of SolarWinds’s DevOps package, enabling full-stack monitoring as a service.
The platform and product selection as a whole covers a lot of range. The pricing is low enough and the levels granular enough that even customers that only need the use of a few features of the product can buy into the ecosystem with reasonable investment and grow with confidence without having paid too much. One thing that this enterprise company gets is this: Many small companies need enterprise-class features but don't have the user count to justify purchasing enterprise-class solutions. It is not that they don't need advanced features, it's just that enterprise vendors assume that small companies only have basic needs. It is not true, but you can't buy a solution that is only sold in hundreds of seats if you have 25 users in your company. Cradlepoint NetCloud does a good job of getting this right. You can buy a single seat or hundreds of seats, and the price is truly commensurate with your seat count. Everyone gets the enterprise features, you only pay for the seats you need.
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
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.
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.
Device management is nearly the same as if you logged in locally, giving a familiar feel to the interface. Device group management can be cumbersome when pushing firmware updates.
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.
Every time I have engaged support, it has been a satisfying experience. Because they cover such a wide range of applications, I do have to spend more time explaining our intended results and rationale than I would have to do with a more focused vendor, but it's a minor tradeoff for the value of saved time in every other aspect of the solution.
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.
It is much easier to group your devices within NetCloud prior to deployment. We ran into issues of lost/changed settings when grouping devices that had already been deployed
The cost of equipment, lines, and services was over 1,000 times the five year cost of Cradlepoint (formerly Pertino) when looking for a complete WAN replacement. Using small Linux devices (Intel NUCs) instead of expensive networking hardware provided equal service levels when we needed passthrough site-based access, rather than buying specific hardware from a vendor (including even Cradlepoint, though the integration is great and I do recommend their devices - especially for their cellular data redundancy features)
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
Amazon CloudWatch is specific to AWS resources and cannot be easily use outside of the AWS Ecosystem
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.
