Alluvio Aternity Reviews

Having data from the user perspective has helped us target our activities. Otherwise, we're operating off of a lot of anecdotal evidence. Users would say things like, "Oh, my computer's slow or it's crashing a lot." We wouldn't have that actual, quantifiable data from that user. We also wouldn't have it from the high-level perspective to understand.

There are two most valuable features:

• The ability to monitor crash and health event issues at a user level
• The ability to get performance data, customized performance data from our enterprise production apps, third-party apps, specifically like Microsoft and HP and so on

Most of the other APM solutions don't really monitor third-party apps as much. They can't go in and do the normal monitoring of, for example, Microsoft Word, or something similar.

I think they need to focus more on ad-hoc and customized reporting. They also need to allow the users to be able to create their own dashboards, rather than only be able to use what's out of the box. I do know that this is on their development roadmap, but those were the two things, from our perspective, that jump out.

I'd like to be able to pull data out of Aternity a little easier. It all comes in pretty nice looking charts and things, but we have a hard time pulling out hard data, which is usually what you'll need if you're trying to be actionable.

To deserve a higher rating, we would need some additional data, access to additional data around crashes, and they would need to add more robust reporting or ad-hoc reporting module and customizable dashboards.

I did not have any stability issues in this time span.

I have not had any scalability issues. It's an awesome solution. From a performance perspective, we haven't seen any issues. The agents on each machine sometimes will start eating up too much CPU, but they have a self-moderator and if they do that, they shut off. We haven't had any issues there. From a data perspective, it gets more effective the more data you have, the more you scale up. No, there aren't any scalability issues.

We have run into some issues and we have contacted technical support, which has been adequate. However, because it's such a short time frame, we're still often dealing with the implementation support team, rather than their standard support team. So I don't really know what their support would be like in a normal function.

We have a tech assigned to us, since we're still in the implementation phase. I can't really speak to what their standard support is like.

We were looking for the ability to get some performance data from our third-party enterprise apps, like our Microsoft Office, our internal document management system, and so on. We wanted some data on, from a user perspective, how long it was taking to open, how long it was taking to do specific tasks within the applications. We wanted some data to be used internally for SLAs and to develop KPIs and items of that nature. We have pictures from the backend, from a network or a server perspective, but we didn't have any user data. Collecting that data manually was pretty time-intensive and relatively inaccurate. With Aternity, we now have the data.

I think the next steps, since it's essentially a net new function, we have to start integrating the data as far as developing how we're going to handle SLAs and how we're going to handle the KPI reports and things like that. Immediately, we're using it also as a secondary function to assist with problem and incident identification and resolution, using it there as well to monitor crash data firm-wise and so on.

Initial setup is pretty straightforward for the actual install. We used SCCM to deploy. That was pretty easy; it came in a pre-packaged MSI. I think the more difficult part is training and having your team members understand how to utilize the tool. Their training programs could probably use a little work. I'd say that was about it. From a technical perspective, the implementation was relatively seamless. But from a process perspective, especially if you're not replacing something, it was difficult. So we're still working through that.

Make sure that you have a well-developed plan for integrating it with your existing processes before you roll it out. Other than that, I wouldn't say much. It's pretty easy to roll out and it's really just leveraging it as effectively as possible is what I think you want to make sure you focus on.

It's a monitoring tool. Specifically, it monitors very well the ability to sort large amounts of data into something that is actionable. Once you know how to use it, it's very good at identifying trends underlying in large amounts of data.

It's used to monitor our application performance. Desktop health, network health, things of that nature. We have used it to identify issues impacting large amounts of end users with applications, issues with our network, issues with our group policy setups or exchange, all sorts of stuff.

We've built a task force that I was the head of to resolve some longstanding issues with our existing Windows 7 image. The Aternity application was a key product in helping us not only identify the issue, or at least quantify the issue and begin to narrow down the likely causes of it, but it also allowed us to measure how successful we were at implementing changes, moving the needle in the right direction. It's helped us stabilize our exchange environment.

The latest thing we did with it, specifically, was track down an issue in which our end users were disconnecting from Exchange on a alarmingly frequent basis. It allowed us to figure out what was going on, implement a solution, and then validate the solution was in fact working.

The product itself is actually extremely solid. The support of Aternity, specifically their client success management and after-sales support and training leave a lot to be desired. They've gotten better with my last engagement with them, which was beginning in May.

We're still ongoing with a little bit of training. We recently switched from their on-premise Aternity 7 version to their cloud SaaS-based Aternity 9 product. Largely, once you get the product and you have it set up and get it installed, the relationship management after-sales leaves a lot to be desired. The product itself is actually really, really fantastic.

Between the Aternity 7 and the Aternity 9 version, they've made a whole repolish of the UI. They rethought the entire UI to make it usable for folks that haven't spent 40 to 60 hours training in the product, like I have.

We're getting a lot more value out of the product from every single level of IT, all the way from our service desk up to our executives and back down. They've done a very good job at innovating on the product. It's more so the support and professionalism of their client success managers and after-call support that leave a lot to be desired.

Their product is a 10. The support is a five. I'm going to average them out to about a seven and a half to an eight. I hope they're able to continue to improve. I want to make clear they have improved and I've been much more impressed with their support recently than I was over the last three years.

I hope that's not a function of an ongoing engagement and additional large sum of money that we've tossed at them in order to set up the new product. If they can improve on their support, then they would be in a really, really good position.

I have been using this product for close to three years.

We did have some issues with the SQL database side of the product, when it first stood up, and the application server would lock up. Not always, but there was a period of maybe six to eight months when the application server - or the IAS services specifically - would stop functioning, or we would get some deadlocks on the database. It was a task to deal with Aternity support to really identify those particular issues, but overall, the stability of the product was pretty good. I think we'll have less of those issues now that we don't have to maintain our own servers. It's all handled in the cloud. I imagine that since it's a high-availability service, considering it's a cloud-based application, that we will likely not see those issues moving forward. If we do, I won't have to fix them.

I have not had any scalability issues at all. The deployment of the actual monitoring agent is probably the easiest thing we've deployed through SCCM in years. It's very, very simple. It's easy for us to upgrade. It's silent. It doesn't impact the end user when we install it. It's extremely scalable. We currently have it monitoring all of our end user workstations, which is approximately 1,600 computers.

We do have it on some of our servers, but not all. We're looking to scale that up in the new environment, which will equate to roughly 800 servers, as well as another 12 to 15 for our Citrix infrastructure. Overall, we're close to 3,000 total endpoints being monitored by the product, and it's extremely easy to install and configure. We package it. We put it in SCCM and it installs. It's really, really simple.

Recently, technical support has been fantastic. Prior to us being involved in an ongoing engagement with them, it was a little rough. We had to constantly follow back up with them. My calls and emails, depending on urgency, were not necessarily met with what I believe would be an acceptable SLA, especially considering the expense of the product. It's not a cheap product by any way, shape for form. Recently, the engagements that I've had with them have been far improved. We had two particular issues with the product when we moved to the Aternity 9 environment.

The first one, the installation of the agent itself removed a couple of registry values on our end users machines that caused a piece of our Citrix to not function for our entire environment. They not only identified the issue, provided me a solution I could deploy over group policy within less than three hours, but they also delivered me a new agent version the next day that had the issue resolved, which I was extremely impressed with. I had a four-hour down time. They did a really, really good job of taking care of that for me.

Then I had an issue where the application was not displaying fully correctly in Internet Explorer. Once I submitted the ticket for that, and it was a lower priority, they contacted me within 24 hours, and we had a solution implemented within 48 hours. I would say they're definitely trending in the right direction. My hope is that it doesn't fall off once we're done with our active projects.

Previously, we had several monitoring applications, but nothing that really is able to draw a large picture the way that Aternity is. Did we use other products? Yes. To any level of success? Definitely not. There's really not anything like it on the market that we've been able to find. The algorithms that it uses and the ability to aggregate such a large amount of information in a way that make it really, really easy to use for every member of IT. I use this product every single day. I'm probably the most knowledgeable user of the product, and it's extremely powerful. I really don't know of anything on the market that's like it. The product is phenomenal. I really can't speak highly enough about how powerful the product is, and recently they cleared the one major hurdle with the product in that it wasn't very user friendly.

The on-premise setup was relatively complex. The transition to the cloud platform was really easy. Really, really, easy. One, because the professional services team did all of it for us, but just by the nature of the product and how it functions, the setup of it is always going to be somewhat complex. Specifically, in designing the signatures and the monitors for very specific activities and actions that are undertaken within an application, or on a server. There's always going to be a level of complexity.

Once you set it up, it's very, very easy to maintain. It's considerably easier to maintain when you don't have to maintain your servers, which is where we're at now. There is always an inherent level of complexity, but the upgrade from our on-premise environment to the cloud-based was extremely easy. They were able to import all of our existing settings, with a few exceptions, into it. The training on it has been absolutely fantastic. It's pretty easy. They even gave us training on how to author and signature the monitors themselves, which has allowed us to expand our ability to support and customize the application in real time in a way that allows us to get more out of the product then we were already doing. We were already getting a very large amount of value out of the product.

Because we can proactively see the productivity and performance of employees and people working on behalf of the company, we're able to see degrading performance and address the root cause prior to business impact.

The most valuable feature for me is being able to monitor the productivity of every employee in the company as well as third-party, outsourced companies that work on our behalf.

And I also monitor cloud services. It can take that much workload.

I would improve the dashboard, the presentation player.

I did not encounter any issues with stability.

We have it right now pretty much enterprise-wide, so it's very scalable.

Technical support has been top-notch.

We evaluated other companies such as a product from a company called Lakeside Software.

Initial setup was straightforward.

I'm rating this solution as high as possible because of the unique insight that it provides and the dynamic nature of the product.

If we have an application that appears to be causing problems, like if users are seeing slowness, we'll go back to Aternity and look at the data. From there we'll try to get info about where things might be going wrong and then send it to whichever team needs to take a look at it, such as the network team or the application team. It could be a desktop issue, in which case we can try to see at least where the problem is using Aternity.

The item we use the most and what upper management wants is the SLA reports. It's a good summary of how the applications are performing over time from month to month.

We're two versions behind so some items have probably been taken care in the newer versions. In our current one, I think the workflow needs improvement. I wouldn't say our desktop is an issue to be able to click into it deeper and then move to where the problem is on the desktop site. From what I've seen in the demos of the newest version, have already improved on that.

On the server side we had a web app for a while, the web portal into the Aternity console would just freeze and crash, and then we had to reboot the servers and then it would come back up. I contacted support and they were able to find out what the problem was and we got it resolved.

We haven't grown all that much really as far as number of workstations. We are having more and more people jump into the console side of it and I don't think there's any issues there.

It's pretty good. Sometimes the response could may be a little better but overall it's pretty good.

This is the first solution we had.

I don't know because I wasn't involved with the initial setup. I came into it a little after the initial setup but I have done upgrades since then and those are done through support hours and Aternity just walked us through it. They remote into the machines and then we just let them do the upgrades for us, so I would say pretty simple then.

Make sure you're set up correctly. In order to get the actual full view of what's going on we would recommend to deploy the agent to all of your computers instead of just some of them.

The version that I've seen, the one thing it doesn't do which I don't know if it's really meant to do is that you're getting all the view from the client side but sometimes it's not possible to look on the server side at anything that's happening on that side of things. It's good to see what the users are seeing but doesn't do a great job of digging into what the problems could be on the backend. It'll kind of tell you if it's the backend or not but from there it's limited.

One of the things we wanted to do is we have a number of call centers that are at a disparate, some of them are partners, some of them are owned and operated, and when we have an issue reported from a call center, we could end up with forty people on a phone call trying to figure out what was going on. They're running around, w'ere reporting in individual workstation, this agent says, "Hey, I got this problem and it's over here," and you got to stop and document that. Then they have another guy who says, "I got this problem over here," so you have all these disparate pieces of information that you have manually correlate with a bunch of people on a phone call for hours and hours and hours.

With Aternity you can gather that perspective quickly, it's gathered automatically, so that slow response time or issues with the application, hung workstations or network issues, you get that perspective right away. It eliminates a lot of the time spent troubleshooting.

All of it, but it depends on who the end user is. The folks that support the applications, like the signatures that we've developed, it gives them feedback on their application performance. The folks that deal with the IT with their desktop in the call centers like it because it gives them visibility into the desktops that they wouldn't otherwise have. Then the guys that are responsible for our mobile devices like the mobile aspect. The reason they like the features is they didn't have them beforehand - it's visibility they didn't have prior to this tool.

For instance, the folks in the call centers if they wanted to look at a workstation that wasn't performing or was having an issue, they had to go to the workstation or remote into the workstation. They had an agent that kept having issues with her machine and they couldn't tell what was going on, every time they looked at it it'd reboot. With the Aternity tool they were able to see she was actually powering the thing off and then saying, "Hey, I can't do my job," so there were some shenanigans. It gives good visibility into what the behaviour is of the agent interacting with the workstation as well as interacting with the applications.

From the application owners perspective, we have real user monitors out there in the call center and we've got sniffers that capture the transactions as they come across a network, and synthetic transactions and that sort of stuff going on, but it really didn't give them that view from the call center agents workstation. It gives them a more realistic picture of what's going on than from a networks perspective. You're actually now getting it from the workstations perspective. Then the wireless guys, (the people that are dealing with the handhelds), that's just visibility we didn't have and there are a number of tools. Since we already had Aternity deployed in the call center, it was a natural extension.

Signature development process requires deep technical expertise in the application and in the use of their studio tools that help you create it. I know they're aware of that and I know they're focused on making stuff simpler. I think in version nine we'll probably see improvements. That's the biggest thing for us, and unless you're creating those signatures on a daily basis, that needs to be your full-time job to maintain the expertise to do it properly. We're still depending on their professional services to help us with that.

In v7, we had some stability issues and those all got resolved, but the first six months of being up we had some stability issues. Now we're on v8, and looking to upgrade to v9. So far, it has been rock solid. It's completely stable, I can't believe it's stable as it is.

Well we overbuild. Our environment is overbuilt, we're built to handle twice the workload that we have. Our model is you live and die by your peaks. All of our stuff is built to handle those peaks. That's just a natural for us, we overbuild it. We haven't had workload related issues.

It was good. One of the things that just for me, I came from a field service background, I worked for Digital Equipment back in the '80's and '90's, and there when you provided customer service you had a fifteen minute call back time. Nowadays you send an email or open a ticket online and you hear back in four hours and so your primary communication mechanism is by email or by updating a ticket on a website. I like phone calls, and that's just a general trend in the industry. I like a phone call back, but that's not anything anybody's doing, so that seems to be lacking in the industry. There are no better or worse than any other, as far as response time.

We didn't use a different solution.

It was straightforward. We used their professional services to do it because we hadn't been exposed to it before, and our environment is sizable. It's not like we installed the app on one box, it's broken up into six components plus an Oracle backend database, so it's a pretty sizable implementation. It's not that complex to manage and maintain. Regarding the installation - unless you're doing it every day, you probably want their professional services to help you.

We evaluated some different solutions. One that we looked at was more for agent behaviour evaluation than it was for monitoring. The analysis there was too deep for our purposes. We wanted the instrumentation that would tell us when there's an issue, and you can certainly do that with both tools, but the other tool is a lot more about understanding that agent's individual actions, and it was just a different tool. We do have other tools, there's RUM and Synthetic Transactions going on as well. This was an enhancement to that.

The first thing I would do is the application owners need to put monitoring and managing the signature set, or the monitor set, that you develop for the applications into their release process. When you do a release for an application, you need to include developing and testing the existing monitors, testing the existing monitors and fixing them if the application breaks them and if the release breaks them. You need to manage your monitors along with the application releases.

We were able to identify bottlenecks in the application code that we had. A good example would be JavaScript, as we found that we had inefficient JavaScript in some applications.

Desktop monitoring, and being able to understand the performance of applications that runs on the desktop.

The thing that I think most companies like ourselves would want would be an easier way to customize custom scripts. It does a lot of out of the box standard monitoring, but there are special applications that every organization have, and right now, creating the custom scripts requires technical resource support from Aternity.

It's fairly robust in terms of its architecture design and development.

We haven't really scaled it as we've only installed it on a customer base of about 300 desktops.

It was straightforward. Because it was a very small agent that we deployed, and did not require a lot of customization. By small agent, I mean the footprint of the agent was very small to install, and it didn't really require a lot of customization.

The product is kind of unique. We used other products in the past, I don't even know the names of them because they were old IBM products dating back to the 60s and 70s. Aternity sort of fits a niche in the marketplace. I don't know of too many tools that do what they do.

I think the nature of, and it's not only desktops, but people that are doing mobile development, that the industry is changing whereby the applications that are being developed today are using more and more of the local processing resources on the client. Because of that, it's important to have tools that can monitor the client performance and look at resource utilization, things such as JavaScript run locally on the client.

It improved our connection to other teams when performing troubleshooting tasks. This is huge when dealing with a large organization with multiple tiers of support, and having an end user utilizing an application that could have number of things go wrong. This deep dive can help mitigate the problem and help align escalations.

The dashboards of this platform are the most valuable, especially the Desktop Health dashboard. This gives you the ability to see the trend in health of all desktops in a historical view.

I would say the reporting capabilities of this product could use room for improvement.I would say the reporting capabilities of this product could use room for improvement. The standard reports that are given are not the greatest, and no custom ones can be created; however, I am told that the latest version of Aternity offers this!

Our only issue with stability was with our previous version, 6.0, and being upgraded to version 8.0.5 was a massive improvement.

I don’t foresee any issues with scalability. We are well aware of the current load that Aternity has on our current infrastructure and we'll monitor how big our environment grows so we can set aside budgets to increase the infrastructure if needed.

9/10. Their technical support is very customer-centric and professional. Their determination is to resolve the problem fast without hindering quality.

We have always used Aternity for end-user monitoring.

It's complex in someways, and our fix to this was to have the vendor perform the installation. We paid a premium for this service.

If the scale of your monitoring will be to go everywhere in an organization, a site license is key.

I would rate this product a 10 because of the way it is able to dive down into the application and report everything that is going wrong with a certain application functions, helping give a full view of the end user’s experience.

Be sure to have a PoC done in a test environment with 100-200 users, if possible, to validate all means of the platform. This will come in handy supporting the tool as an administrator.

The two most valuable features for us are its abilities to validate the customer experience and to measure performance before and after upgrades.

• Intuitive use: The GUI isn’t intuitive and several elements of its design differ in appearance and function with other parts of the interface.
• Reliability: Issues interfering with the deployment and use of the product has made its use reduced in scope.

We've had issues with stability. We have a case pending and instead of fixing version 7.1.7, we're looking to upgrade to 7.1.9 instead.

We've had no issues with scalability.

Customer Service:

Customer service is excellent.

Technical Support:

Technical support is excellent.

We had no previous solution.

The initial setup was complex. There’s a lot of architecture and installation, configuration, and setup of varying pieces to make it all work.

The vendor implemented it for us. They did an excellent job, as usual.

Understand what it does, what it can do, what it can't do, and set realistic expectations.