Likelihood to Recommend If you are familiar with IBM Rational Suite products, RequisitePro will add up due to the synergy between other components. Beyond that, if your business is not structured to an adequate development methodology or lacks the degree of maturity or necessary resources, probably RequisitePro does not add much value. If you work with developers in the requirements analysis, they probably prefer to use an SVN repository.
Read full review SolarWinds Loggly is great for capturing and organizing logs from 3rd party sources such as NGINX. Without SolarWinds Loggly it's really difficult to manage the logs overtime, find traffic patterns, and identify issues before they become a problem. Anyone who is routinely searching through massive log files could quickly benefit from the SolarWinds Loggly and it's capabilities.
Read full review Pros Capability to query bugs on multiple criteria and export it to csv for triages. Simple and intuitive user experience and clearly planned defect life cycle There are other features like assigning the defect to pull request, clearly explaining defect by attaching screenshots, detailed description etc If you are using other IBM tools for requirements documentation, this tool integrates very well Read full review Putting our logs in one place and making them searchable. We use AWS, and CloudWatch has always been a little frustrating in this regard (though it has gotten better recently). Deriving metrics from our logs. I think log-based metrics is such a good idea because your logs are the ultimate source for truth in regards to what the hell is going on inside your app. I have really loved the simplicity with which I can just count certain statements and call that a metric because just through the normal course of development certain log statements just naturally become a straightforward recording of an event having occurred. Alerts. I actually have a few complaints about email alerts, but just the way I was able to set them up so easily has been huge. Since we started using Loggly, there have been at least 3 bugs that Loggly exposed that were frankly very bad. And withoutt Loggly or without a user reporting them, we would have never known they were happening! This is stuff I tried to set up in CloudWatch in various ways, but because of my own ignorance or perhaps the complexity/limitations of CloudWatch (or the complexity of my stack?), I wasn't getting the information that I needed until I was able to just tell Loggly to send me an email whenever the word "error" showed up. Read full review Cons Performance can be an issue. Make certain the server is sized properly There is a large difference in capability of the Thick Client Version compared with the web based version. Make certain each job function has proper access to be able to do what is required of them. Learning curve is not too steep, but would suggest having someone with experience setup the repository. Highly suggest getting a contractor to assist to get the repository up and running. Read full review Not all searches are intuitive. We have to use a log aggregating device to ship our logs to Loggly as our network devices can not connect on an encrypted protocol. I would prefer if we could use some sort of VPN-based connector to ship logs securely. Sometimes when drilled down, it can be difficult to fully reset a search term to back all the way out of a drill down. Read full review Likelihood to Renew Most likely as it's one of the powerful tools in the organization. We needed this tool to track all the process related documentation and also to capture signatures.
Read full review Management is not open to having an agent sending the data to the cloud instance.
Read full review Usability Please keep in mind that this all has to do with you you customize the user interface. It becomes very easy to house all of your requirements, but it may and can make life difficult for you if you do not think ahead of how you want the app to work and house your data
Read full review Loggly's easy setup, very good customer support, and intuitive interface make Loggly very easy to use. User access management is also very easy as we can tailor the experience for each of our developers to access the information they need without having to wade through other information. While there was a slight learning curve in how to view the logs the way some specifically wanted, everything was possible and quite easy to do.
Read full review Support Rating IBM has good support and knowledge base. With the wealth of information on their site and the support desk, we were able to quickly resolve issues. It is smart to build up a COE and a group that manages the software otherwise it is quick to be able to lose the knowledge as team members are assigned different duties
Read full review The support team have been great when we have logged tickets or had issues, most of the time it is down to user training, however we have had a couple of bugs that they have been able to iron out for us.
Read full review Implementation Rating It was pretty simple.
Read full review It has good architecture, which focus on ese of use.
Read full review Alternatives Considered IBM clearquest would the BEST option if you are looking for managing change requests, managing project workflows, generating reports on status of requests. The reason being: cost, cost and cost. It almost handles everything that you would need for your project including bug tracking unless you want something really fancy (like HP QC) with a higher cost that supports a wide variety of needs which you might need to evaluate based on your project needs. For example, if you would be really making use of all those additional features provided by HP
Quality Center . To be honest it depends on your project size, the skills of team members and of course budget!
Read full review We were using
Zabbix . While it is an open-source solution that you can install for free the following things were limitations of the solution. 1) The scale and uptime of the solution are now your own problem. Since we were hosting at AWS this meant we still had a cost of the AWS solution. 2) The product is complicated from a configuration standpoint. In order to get anything meaningful out of it, you had to invest a lot of time and effort. We did consider NewRelic. I have experience with that product and do think that it is a solid alternative. Ultimately experience with the simplicity and speed of deployment with Loggly encouraged me to suggest using this again.
Read full review Return on Investment IBM Rational ClearQuest has provided a workflow that works without unique software methodology. As a result we deliver complete software products to our clients in a 6 to 8 week development time frame. As a result of our highly customized implementation, we have 8 resources supporting IBM Rational ClearQuest. Three of the resources are full time configuration management staff that administer and support the tool set and the other 5 are from the testing group that handle ClearQuest user support issues in addition to their testing duties. Read full review Unfortunately, we hit our logging cap on a weekly basis and we lose logs after that. We have lost logs after hitting the maximum during service outages. We have become accustomed to not being able to rely on having them, then things go poorly. Read full review ScreenShots SolarWinds Loggly Screenshots