Help make Spotter better

2. What made you decide to try it out? (What were your expectations?)

3. Did Spotter meet your initial expectations?

Yes

It exceeded them

4. Since registering, have you used Spotter?

Yes

Please share why? (Do you find something confusing or challenging? What would make it easier?)

Please share why?

8. Why are you using Spotter? Please select all that apply:

To scan playbooks after writing to check their quality.

To scan existing playbooks to see if they’re still error-free.

To regularly monitor playbook health.

I haven’t used Spotter yet.

Other:

9. Have you thought about using Spotter for daily playbook scanning (continuous monitoring)?

Yes

Not until now, but that’s a great idea.

11. What don't you like?

12. What could make Spotter more useful for you? (What's missing? Any features you'd like to see?)

13. Are you using any other tools to identify and fix issues in your playbooks? Please select all that apply:

Ansible Lint

Ansible Molecule

KICS

SonarQube

Other

No, I test by trial and error

No, I test on production (I'm a daredevil!)

14. Is there any other feedback, comments, or suggestions you have for the Spotter team? (optional)

Just a friendly reminder: it's one per person, and only for those who share genuine feedback and answer all questions.

E-mail

Which Amazon gift card would you prefer:

Amazon.com

Amazon.co.uk

Amazon.de

Another Amazon region:

Amazon.in is excluded due to payment restrictions.