Once I got it installed, I like the way it discovered my environment and gave me the capability to map application dependencies. The ROI certainly looks attractive. I would like to have had more time to use it, but the installation took longer than I'd allocated for the entire POC. Once I got a Faddom tech on the phone, we were able to iron out the last few challenges, but that took almost two weeks and put me past my deadline. Review collected by and hosted on G2.com.
The documentation was complicated and often conflicting. One document led me to believe I could use a Faddom-provided AWS CloudFormation template to roll it into a test AWS VPC I set up. Faddom Support later confirmed there is no such template and I had to go back and create the VPC flow logs manually. One set of documentation indicated I should use AWS Traffic Mirror to capture the netflow data needed for dependency mapping. Faddom Support and other documentation later confirmed Traffic Mirror is not supported by Faddom and that I should use VPC Flow Logs. I also ran into some permissions issues with accessing the VPC Flow Logs. I can't say if the delay was because of AWS or because of Faddom, but the changes I made to the permissions didn't seem to propagate to Faddom in a reasonable time period. Review collected by and hosted on G2.com.
The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.
This review contains authentic analysis and has been reviewed by our team
Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.





