Quality and commitment to AWS Add-on

[terrencebenade]

Just looking for some feedback on where we are in the lifecycle of this Add-on and the commitment to quality. Is it alpha, beta, RC? Having spent a few weeks now trying to use the plugin I have had many problems and perusing this channel I can see many unanswered questions and lots of threads that are un-responded to. Many of the issues from my limited experience point to issues in quality and basic functionality.

This is not a community plugin but a closed source Splunk TA. So correct me if I am wrong, would one expect a level of fit and polish and prescribed by the Splunk licensing costs.

Given how long some of these questions are pending/unanswered when can we reasonably expect these issues to be resolved if ever?

In short are Splunk committed to the quality of the TA and can we expect more frequent releases of a higher quality or are we better off building the functionality we need ourselves?

[rpille_splunk · Accepted solution]

Hi Terrence,

Yes, we absolutely are committed to this TA's quality. We just released a new major version of the AWS add-on yesterday. Please check it out and see if it resolves your problems. The Fixed Issues list in the release notes show that we have addressed quite a few issues in this release: http://docs.splunk.com/Documentation/AddOns/released/AWS/Releasenotes#Fixed_issues
If you have any problems with any of the documentation, please send feedback on the documentation and someone will email back to you to follow up.

Also, this is a fully supported product, so the main channel for getting help is to file a Support ticket if you experience any issues.

I hope this helps!