RSA Analytics 10.5 release with bunch of known issues
Hi RSA Team,
We are really happy that we will be upgrading our systems to 10.5 release which is being called as very stable release of RSA yet.
I am eager to know what is the reason behind keeping bunch of known issues as its not simple task to check out how many issues are already there even we are on the latest release of any product.
I would really appreciate if you and your team can release automate fix for know issues which you know and can be fixed ASAP.
I have seen the era of RSA Analytics right from version 10.0 release so i am really happy where we stand today as compare with very first release but we need to improve a lot and we are there to provide you inputs on improvement front.
The last question I would ask is, whether it is good to go with RSA Analytics 10.5 now or should wait for another week to see the reviews?
- Community Thread
- Forum Thread
- RSA NetWitness
- RSA NetWitness Platform
We are sitting tight until July.
We also have the v10.0.2 up to current history to go by.
I would like to see a list of issues encountered by current 10.5 customers.
The known issue list given at release is never the current list.
We end up fighting a new release issue for days/weeks that is known within the RSA org.
That's all I ask, a very current known issues list for 10.5. Not here on the public forum obviously but on the SecurCare site.
Thank you for your post and for your feedback. It is always important to hear from our customers and know what we can do to improve their experience with our products. We at RSA believe that we have turned a corner with the release of Security Analytics 10.5, and agree with you that this is our most stable release of the platform to date.
Like any major release of any product, whether it be Mozilla Firefox, Apple iOS, or any other software platform, known issues are often found after the code freeze takes place before a release, at which time they are included in the Release Notes. The majority of the known issues for this release occur only in edge cases and will be experienced by only a small percentage of users. That being said, many of the known issues already have workarounds and/or will be fixed in the next patch (version 10.5.0.1), and those that do not are currently being investigated so that a resolution may be provided shortly.
For the two most recent releases (versions 10.4.1.1 and 10.5.0.0) the Support team also introduced a new initiative to have a knowledgebase article written for every known issue addressed in the release notes in an effort to make it even easier for users to quickly identify and resolve the issues as they are encountered, as well as to simply be aware of them when preparing to upgrade.
Two Master List articles are also published in the knowledgebase that compile the articles into one location, which can be found at the links below.
- RSA Security Analytics 10.4.1.1 Known Issues Master List
- RSA Security Analytics 10.5.0.0 Known Issues Master List
These articles, like every knowledgebase article, are intended to be dynamic and the Technical Support Engineers have been instructed to update them whenever new issues are identified so that they may continue to be used as a current reference point for known issues in the respective versions.
We have been very excited about this new release and, while I cannot vouch for every user experience, I can say that all of the feedback from users that I have personally received thus far has been very positive. If anyone encounters any new issues, please don't hesitate to engage the Support team and we will be happy to assist you and to document the issues appropriately so that everyone's experience may improve as a result.
I appreciate this will be a dynamic list of known issues. That will be incredibly helpful.
One request, Can we get some kind of date information on the 10.5 Known Issues list? Date created & date modified?
Its pretty hard to tell when the list was last updated in current form. I assume there is some kind of content mgmt system behind the scenes. We could just continue to revisit the page over and over and watch the last issue #, currently #30519 to see if #30520 or 21 has been created.
Same goes for the issue detail pages, there is no date created or date modified.
That little detail will make assessments/debugging much easier.
Thank you for bringing this to my attention. I will put in a request to see if we can get a Last Published date included in the Article Properties. In the meantime, I will also work on getting the last modified date added to the Master List articles in a Notes section near the bottom so that users can be aware of when new articles have been added to it.