IBM Terraform (formerly Hashicorp Terraform) is a cloud infrastructure automation tool used to create, change, and improve production infrastructure, and it allows infrastructure to be expressed as code. It is available Open Source, and via Cloud and Self-Hosted editions.
$0
SolarWinds Pingdom
Score 8.3 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.
AWS CDK is like a cloud-specific alternative to Terraform. As its name suggests, it's from AWS & only works with AWS, a job it does excellently. If your cloud provider is not AWS, then you really only have Terraform to choose. If you are on AWS, it boils down to which one you …
IBM Terraform is better as the providers just work. Ansible is still finicky with their community modules for cloud, especially for Azure. We do not need to build execution environment containers like Ansible. Using statefil for drift analysis is also helpful to review changes …
Dbt was fine, but you end up with an extremely bloated repo/project. Often where all of the models are the same, named similarly, and generally just doesn't adhere to the concept of DRY coding. In Terraform we're able to template a lot of this work and dynamically generate …
HashiCorp Terraform is much better than Cloud Formation. For one, the language is just easier to use, but more importantly, the provider ecosystem is much better in HashiCorp Terraform than in Cloud Formation.
I'm beginning to look at Pulumi. In my opinion, it looks like it would be a good replacement for HashiCorp Terraform, and it has the advantage of configuration via scripting, rather than via HCL, which is HashiCorp Terraform configuration markup language. In my opinion, the …
We have used Vagrant to develop our application in a virtual box environment and prepare it to be packed with Packer. The image created from these two tools will be deployed by Terraform.
We are using Consul for service discovery and as a job locking so we don't have two jobs or …
CloudFormation is only for AWS so if you're trying to deploy to another cloud provider then Terraform is your product. Terraform has lots of public support so you can find answers to questions by Googling. CloudFormation is easy to view the resources/services that are …
Terraform is a large step ahead of the previous generation of infrastructure-as-code providers. I'd never go back to, e.g. Puppet or Chef, Ansible, etc. That said I think that Pulumi has a good chance of displaying it, in no small part because the Terraform language itself …
AWS CloudFormation is better if you just want to stick with AWS because it's integration with AWS is better, provides auto-rollback in case of failures, and has GUI to manage and view the stacks built. Terraform is better when we want to stay cloud-agnostic. Terraform is better …
I can't find these applications listed, but other IaC tools I have used include: AWS CloudFormation, Azure Resource Manager Templates, and GCP Cloud Deployment Templates. For a comparable tool, I have the most experience with CloudFormation.
Chef and Terraform are not apples to apples because Chef is more focused on config management, whereas Terraform is more focused on provisioning. However, I can say that where they do overlap in configuration management is that Terraform is the preferred tool because it has an …
Terraform is the solid leader in the space. It allows you to do more then just provisioning within a pre-existing servers. It is more extensible and has more providers available than it competitors. It is also open source and more adopted by the community then some of the other …
Terraform is open source and has strong community support. It is cloud-agnostic versus competing products like AWS cloud formation, hence has a distinct advantage. The scripts once set up are easy for developers to administer during development, hence during production …
- Terraform syntax is much easier to read and learn than Cloud Formation.
- Terraform already supports AWS as well as several other cloud providers.
- Terraform is backed by a great and supportive open-source community.
Terraform shares the methodology of creating configuration files for your infrastructure with tools like CloudFormation. However, Terraform is cloud-agnostic unlike CloudFormation which is AWS specific. Terraform can be used to maintain AWS and OpenStack clusters …
CloudFormation is the lingua franca of AWS. You certainly can't go wrong using it, but I like the syntax and open-source nature of Terraform. That's mostly a personal preference. I have not tried any other non-Amazon tools for provisioning AWS. And, of course, the AWS tools …
At least during our investigation thus far, all of these companies have a more responsive support organization and are more actively maintaininbg and supporting their products. They are also all significantly more expensive.
I have used Datadog's testing, and it is far more in-depth but more expensive. Pingdom was simple and easy to set up and very reliable, but Datadog had more advanced features but also cost a lot more and wasn't as simple to set up.
We have been with Pingdom since before it was SolarWinds Pingdom. It remains stable and solutions driven and has done so for many years. While it has many features we do not utilize, we are always looking to see which ones we can start to use when we have time. Some of the more …
We have only used Pingdom for these needs, so I can't speak directly to competitors. That being said, for the reasons we used Pingdom it was fantastic value and the fact we never bothered to look for a competitor speaks volumes about our satisfaction with the product.
We use a mixture of atlassian products and chose to use this at the beginning of 2020 when our org switched to full remote work posture. While it was nice having integration with opsgenie and our jira ticketing system it did not provide quite the mixture of flexibility and …
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 …
It is very suitable for our organization as metrics that it provides like disk space, CPU usage and availability of application, etc. And the main thing is it has good integration with OpsGenie and Jira software so when our application is down or has any issue then we get a …
Some of the products mentioned here are much more "holistic solutions" for monitoring, analyzing, logging, alerting, etc., but for the use case, we use SolarWinds Pingdom. I think that SolorWinds Pingdom is much simpler and friendlier for configuring and maintaining. We …
we migrated from site 24x7 to pingdom because we have been facing issues with the monitoring and alerting. Our customers would reach out to us first rather than our monitoring tool notifying us that there is a problem. Its administration is also very complicated and compared to …
We have looked into using New Relic Synthetics to achieve the same results we are achieving with Pingdom, ultimately Pingdom is significantly cheaper for essentially the same functionality.
We selected SolarWinds Pingdom based on the feature set we desired, which was simply a monitoring solution for our websites and other critical network services. The decision to use SolarWinds Pingdom was based on the simplicity of their mobile app and website.
Newrelic has some simple uptime monitoring but it has very unclear pricing, which depends on how often you ping. And for our needs the next pricing bracket was way too much, maybe 10x. This could make sense if we were going to use the other monitoring capabilities of NewRelic …
8 because it's currently best-in-class and is completely essential to use in contrast to not expressing your infrastructure as code. That said, new contenders are nipping at its heels, and I expect stronger tools to emerge in the coming years. Hopefully the Terraform team is able to keep pace.
Pingdom is well suited to monitor any of your public facing IPs, so you receive an alert by text message or email when the IP you are monitoring does not respond for a given length of time, from an impressive 10ms to 30s. This allows you to be pretty granular with the alerting. It's less appropriate for monitoring IPs on your LAN, unless you NAT these through your firewall.
Alerting, particularly the integration with PagerDuty.
Reporting: the ability to go back and view the history of each status check (including details about every failure) as well as graphs and reports over a longer time period.
Weekly uptime report emails are very convenient.
Programmatic configuration is possible with a third-party Terraform plugin.
The errors generated by the plan and preview commands are pretty cryptic, it can be hard for newcomers to the scripting language to understand how to address problems.
Access controls around workspaces is limited which makes it harder to secure reduce the scope of teams ability.
Analytics around user usage, applies and plans would be helpful for managemenet.
there should be some threshold value for when an application is not reachable, it should alert after 30 seconds and keep sending hello packets for those 30 seconds and if still there is no response, then it should send the alert.
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 syntax itself is pretty straightforward. The documentation is well-maintained & easy to follow. Most cloud providers, even smaller ones, maintain official provider libraries, making discovery & learning a breeze. Some, like GCP, even provide high-level libraries on top of their own more primitive provider, making building complex infra much more manageable. The language itself is cloud-agnostic, so you can literally manage resources from multiple providers in a single Terraform repo.
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.
Terraform's performance is quite amazing when it comes to deployment of resources in AWS. Of course, the deployment times depend on various parameters like the number of resources to deploy and different regions to deploy. Terraform cannot control that. The only minor drawback probably shows up when a terraform job is terminated mid way. Then in many cases, time-consuming manual cleanup is required.
Terraform is community driven but does offer support for it's Enterprise product. When contacting the team at HashiCorp we have always gotten resolution to our issues. They have been very responsive in returning our calls and answering our questions as they come up. We are currently using the open source model.
Customer service from Solarwinds has always been stellar. We've never gone unnoticed, even though we're currently within their tail segment. They're a great partner to us and indeed an important one. When we've had to submit a ticket, we've always received a response within 24 hours. I'd highly recommend SolarWinds to any organization with a server network
dbt was fine, but you end up with an extremely bloated repo/project. Often where all of the models are the same, named similarly, and generally just doesn't adhere to the concept of DRY coding. In Terraform we're able to template a lot of this work and dynamically generate assets based on variables instead.
We have only used Pingdom for these needs, so I can't speak directly to competitors. That being said, for the reasons we used Pingdom it was fantastic value and the fact we never bothered to look for a competitor speaks volumes about our satisfaction with the product.
Using code, we are able to build and deploy cloud resources faster and more consistently than producing the same resources in the console manually.
For applications that share architectures, we can reuse code to expedite development. We can also do the same with modules that are shared across the organization.
By defining all of our resources as code, we can deploy complete environments with "batteries included." For example, we can use code that spins up servers in a cloud provider and at the same time, creates monitors with in our monitoring provider. Likewise, when the servers are decommissioned, the monitors are decommed along with them. In the past, the creation and decom of the monitors would have been a disjointed, manual step. With Terraform we get it all with one "terraform apply."
It has helped our organisation keep up to date about any site traffic fluctuations and help us make educated decisions on appropriate server resources for the site
The service is relatively inexpensive making it easy to cost into our maintenance charges