LogicMonitor Reviews

The biggest things are infrastructure monitoring and alerting. This is mostly for our virtual machines, but it is also for other networking equipment and a few other pieces as well.

We are at the newest update. It is a mix between on-premise Collectors and their software as a service (SaaS), which is the newest update. Our Collectors are also on the newest version right now. While they don't have to be the newest version, they tend to get pretty close to the newest version to work properly.

We have used the solution’s ability to customize data sources to a small degree. We are able to more finely tune all the details of what we are monitoring. This comes down to the false negatives or positives, and being able to alert on the actual details that we want to be alerted on.

The alerting would be number one in my book. The thresholds for getting alerts for different criteria are pretty well-thought-out. We don't get many false positives or negatives on the alerting side. If we do get an email alert or some similar alert, we know that it is something that has to be looked at.

I built a remote workforce dashboard, which is my favorite dashboard. When the company pretty much all started working from home, I put together a lot of different graphs of types of infrastructure pieces necessary for users to be able to work from home and put those all onto one dashboard. Therefore, at a glance, we could view the health to make sure anybody working remotely would be in good shape and be able to work successfully.

The reporting capabilities are pretty effective, if you know what you are looking for. We don't use the reporting features a whole lot. However, when I have gone in to create reports, as long as you know what you want to be included in the report, it's definitely pretty quick and easy to get the reporting started.

Some more application performance type monitoring would be nice. For example, an APM type solution, which would not necessarily completely replace it, but be able to tie into to what we're seeing on the application performance side so we can correlate what's going on with the application versus the underlying infrastructure.

Our company has been using it for four to five years. I personally have been using it within the company for about three years.

It's been highly stable. We have had two brief outages, which lasted less than an hour, in the three years that I have worked with them.

We have two people (at any time) dedicated to deployment and maintenance. They are our systems engineers.

It is easily scalable.

We have about 20 users working with the solution who are mostly systems engineers. We also have some DevOps engineers and a few software architects who use it.

We have 1000 resources that we are monitoring with a couple hundred websites. As our company grows, we do plan to increase usage, but nothing major. It will probably be about a 10 percent increase over the next year or two.

I'd rate the technical support pretty highly. The few times that we have had to put in a ticket for support, they have been very helpful. Every time that I can remember, the issue has always been something on the actual resource being monitored. While not technically LogicMonitor's fault, they were still able to help us quickly identify and resolve it.

Twice in the last three years, we have had brief outages between LogicMonitor and our solution. We received phone calls almost immediately from LogicMonitor indicating this. It was a very quick reaction. We know the issue isn't on our side, which is good, in these particular cases.

LogicMonitor was able to replace at least two different solutions that we had in the past for monitoring. One of them being Logicworks. LogicMonitor was able to monitor a wide variety of websites, devices, and virtual machines. We were able to consolidate some of our monitoring so we are one single source now instead of multiple.

The solution’s automated and agentless discovery, deployment, and configuration has been helpful. I've used some of the automated discovery, especially when we've changed data centers and put a bunch of new hosts into our data center. I used their discovery tool. It was able to find and pull in most of the resources that we actually wanted. Even though I wasn't there for the initial deployment, for the times that I have used it, it seems very helpful. There are still some manual processes and checking that we do, but it has helped out a lot.

Out-of-the-box, it was able to monitor vSphere virtual machines, which was the biggest for us. We also have network load balancers, switches, and firewalls that it was able to pull in. We had to do very little to get it monitoring and reporting correctly.

We have definitely seen ROI with LogicMonitor. We used to provide 24/7 IT support for our users. We have since been able to change to operating just within normal business hours for IT support, and LogicMonitor was a large part of being able to accomplish that.

LogicMonitor has reduced our number of false positives compared to how many we were getting with other monitoring platforms. We have seen a 50 percent reduction in false positives, possibly more.

It really just comes down to making sure that we're getting alerts on something that actually does need attention.

We're starting to look into the solution’s Artificial Intelligence for IT Operations (AIOps) capabilities for things like anomaly detection, root cause analysis, or dynamic thresholds to see if it might be useful for some of our services.

Take a look at your environment and at what level of detail you will need for monitoring. One of the advantages to LogicMonitor is just monitoring your vSphere environment without monitoring the individual VMs within it. You still get a lot of detail about those VMs as instances. To put a VM in as a resource, instead of an instance, you get a lot more granularity on the operating system side for what you can look at. However, just monitoring your vSphere environment alone gives you a surprising amount of detail.

The biggest lesson I've learned is you need to understand what role your different devices play in your infrastructure in order to successfully monitor them. Get a detailed list of the devices that you do have in your environment that you want monitored and why you want them monitored. The why you want them monitored will tell you what different things you might want to be alerted on because LogicMonitor will collect a lot of information about your devices. Narrowing down what you actually want to be alerted on is the important part.

I would rate the solution as a nine out of 10.

We use it in a few different ways:

• For general monitoring of operating systems. 
• Leveraging some customized offerings, specifically for creating application monitoring. 
• Some external site-to-site monitoring in various places, ensuring that our websites and external pieces are available over an Internet connection. 

It has given us a clearer view into our environment because it's able to look in and pull things off of the event viewer or log files. We have been able build dashboards and drill down on things, which has helped improve our time to respond. Also, in the case of specific conditions being met in X log, we have been able to get in and take a look at that a lot faster rather than trying to connect and parse through the log and figure it out. It's able to flag that and work us towards a solution faster than normal.

We have a few custom data sources that we have defined, especially for our application. It is able to leverage a specific data source and build monitoring rather than just having it be a part of the general monitoring. It is segmented and customized for what we actually need, which has been pretty helpful.

Custom data sources have given us a bit more information from a point in time and historically viewpoint. In the console, it is easy to compare week-over-week or month-over-month traffic and numbers. As changes are made in the environment, we can look and have better historical knowledge, and say, "We started seeing this spike three months ago and this is the change we made," or, "We started seeing this CPU usage reduced after the last patch or software update." It lets us be able to compare and get a better insight into the environment over a longer period, rather than just at a point in time, when investigating an issue.

The solution has allowed us to have specific alerting for specific messages. If we know that X messages on a notification let us know this state has happened, we can then set that to be either an email notification or a tracking notification. In the cases of a log meaning that we have a specific issue, we can have it send an email and let us know. Thus, we have a better, faster response. We also have integrations with PagerDuty, which allows us to be able to make things very specific as to the level of intervention and the specific timing of that intervention. It has been nice to be able to customize that down to even a message type and timing metric.

The solution’s ability to alert us if the cloud loses contact with the on-prem collectors has been helpful to know. E.g., if we are having an issue with our Internet connection or some of our less monitored environments, such as our lower environments in different data centers where we don't have as heavy of monitoring. Therefore, it's helpful to have that external check there versus our production environments which are heavily monitored. Typically, we are intervening before it times out to say that it's lost the connection. It's been helpful to have that kind of information. This way, we know either via a page or email if there is any sort of latency or a timing issue with it connecting to the cloud. It's been helpful that it's not just a relying on the Internet connection at our site, but is able to see into our environment, then it monitors when there are connectivity or timeout issues.

We use it for anomaly detection because our software is designed to function in a specific way. Therefore, anomaly detection is helpful when there are issues that may not be breaking the software but when it is running in a nonstandard way, then we can be alerted and notified so we can jump on that issue. Whether the issue will be fixed it in the moment or handed off to development to find a solution, it's helpful to have that view into how it's running over the long-term.

It is a pretty robust solution. There are a lot of customizations that you can put in for what you want it to be checking, viewing, and alerting on. As we get alerting and realize that that's not something we need to be alerted on or it happens to be normal behavior, a lot of that information can be put back into the system, to say, "Alright, this may look like an anomaly, but it isn't." Therefore, we can customize it so it gets smarter as it goes on, and we're really only being notified for actual issues rather than suspected issues.

It's been helpful to be able to have some information to be able to pass along to development that's very specific as to what the issues are. E.g., we can see an anomaly during periods of time while this is running, then pass that along so development can figure out, "Is it a database issue, an application issue, or possibly a DNS level issue?" They also determine if there are further things that need to be dug into or if it is something that can just be fixed by a code change. 

The solution’s automated and agentless discovery, deployment, and configuration seems to work pretty well for standard pieces, like Windows servers and your standard hardware. It has been able to find and add those piece in. Normally, if I'm running into an issue with finding something, it's usually because it's missing a plugin or piece that just needs to be implemented, which just needs to be added in manually. However, 99 percent of the time, it finds things automatically without a problem.

The flexibility to be able build a custom monitor is its most valuable feature. Because it's just a general CPU or memory, it doesn't always give you a full picture, but we can dig into it, and say, "These services are using this much, and if these services are using more than 50 percent of the CPU, then alert us." We can put those type of customizations in rather than use the generic out-of-the-box things with maybe a few flags. It's been very nice to be able to customize it to what we need. We can also put in timings if we know there are services restarting at 11 o'clock at night (or whenever). We can put those in so as long as it's doing exactly what we want it to do, which is restarting the service, then it won't monitor us. However, if there are any issues or errors, then it monitors us right away. That's been really helpful to leverage.

We use a few dashboards. A couple are customized for specific groups and what they maintain. As I am doing projects, I'm able to make a quick dashboard for some of the things that I'm working on so I can keep track without having to flip between multiple pages. It seems pretty flexible for making simple use cases as well.

I have a custom dashboard which monitors each site and does virtual environment monitoring, such as CPU, memory, timing, etc. It was easy to get in place and adjust for what I wanted to see. It has been one of the go-to dashboards that I have ended up utilizing.

We can kind of get a single pane of glass and be able to view specific functions, whether it be sites or the entire environment. We are able to quickly get in, see what's going on, and where issues are coming from rather than having to hunt down where those issues are. Therefore, it's helped us more with our workflow than automating functions.

The solution’s overall reporting capabilities are pretty powerful compared to ones that I have used previously. It seems like it has a lot of customizations that you can put in, but some of the out-of-the-box reports are useful too, like user logon duration and website latency. Those type of things have been helpful and don't require a lot of, if any, changes to get useful content out of them. They have also been pretty easy to implement and use.

It needs better access for customizing and adding monitoring from the repository. That would be helpful. It seems like you have to search through the forums to figure out what specific pieces you need to get in for specific monitoring, if it's a nonstandard piece of equipment or process. You have to hunt and find certain elements to get them in place. If they could make it a bit easier rather having to find the right six-digit code to put in so it implements, that would be helpful.

Personally, I've been using the solution for about a year. We've had it in place for about a year and a half, but I came to the organization about a year ago.

I don't think we've really had a time where the application or monitoring nodes have failed. The connection to LogicMonitor has been very stable. We haven't had any connection issues to the SaaS offering. It's been pretty resilient and stable from our end.

The scalability seems fine. Every time we've had to expand and add elements, we've not run into any delays or issues with it. It seems to expand with us as we've needed to use more features. We haven't had any issues with delays or timing. It's been able to handle what we've thrown at it.

There are at most 10 users at our company, who do everything from application monitoring to platform engineering to some developers who have access into the solution for some monitoring pieces. Varying segments have been able to get in and they all seem to have had pretty good luck with accessing and using it.

We are using LogicMonitor pretty extensively. We're using it from low level environments, development, quality assurance, all the way up to user testing and production. We have leveraged it in as many segments and parts of the business as we can. It has been really helpful to have it be able to handle different workloads, but also be customized. This way, we're not getting triggered at 2:00 AM because a switch is on in the office reporting an issue, instead we can adjust those timings to report for specific times of the day rather than any time during the day.

We have about 1,000 totals including VMs and physical devices.

The technical support has been pretty good. I haven't had to leverage it, but some of the people I work around have taken it on when we have had questions or issues to leverage the process. They seem to be fairly responsive and the timing of it is usually good. We are usually hearing back in minutes instead of hours. We haven't had any major issues with them.

We've eliminated three different monitoring tools by leveraging LogicMonitor. We had two different in-house, custom built tools that were used for a long time that we were able to roll off, and we also used Nagios. I have also used Zabbix and Orion.

LogicMonitor has reduced our number of false positives compared to how many we were getting with other monitoring platforms. We leveraged the solution to focus it down and only look at the specific things that need monitoring, e.g., rather than every time a service is down we get notified, instead if it's not a critical service, then we can just get a flag, go back, and check it. This is rather than getting spammed with hundreds of emails about specific things being down. Thus, we can customize it for what we actually want to know and need for non-issues.

It had already been implemented before I joined the company. We've added a few functions since then, but the core and initial launch of it had already been implemented and heavily used at that point that I joined.

We have definitely seen ROI.

We have seen probably a 80 or 90 percent decrease in false flag alerts.

We move our people so they're able to be more proactive on things, rather than having to deal with parsing through and figuring out if something is an issue or a non-issue, that cuts down on our personnel time of managing the day-to-day processes. That's been helpful. At least from conversations I've had with management, they've seemed to have found it to be a good investment and solution for getting our normal work done, but also for making sure that we're ready to go if something does go wrong.

It definitely pays for itself in the amount of time we're not spending with false errors or things that we haven't quite dealt with monitoring. It has been good cost-wise. 

I would definitely recommend LogicMonitor. It's something to look at either when signing up for a trial or for a use case process . It's been a great product. It has customizations when you want them, and out of the box solutions if you don't want them. It works and is reliable. Compared to other monitoring platforms I've used in the past, it seems to be the most powerful and robust that I've dealt with.

The solution monitors most devices out-of-the-box, such as, Windows, Windows Server, Linux, F5 load balancers, Cisco firewalls, and Cisco switches. Those have been pretty easy to monitor. Our issues have been with one-off or nonstandard platforms that we've implemented. Otherwise, everything has been pretty easy to implement.

I would rate it as a solid nine (out of 10).

We primarily use it for unified observability, network compliance, and the benefit of an easy-to-administrate SaaS-based solution.

I'm familiar with LogicMonitor, mainly through my clients. Its key features include network discovery, user-friendly dashboards, and robust reporting capabilities.

Once you have your data within LogicMonitor, whether it's for network, server, or storage data, your LogicMonitor has many dashboards built out of the box. So, all your data is consolidated in a nice, efficient way. Suppose a customer needs to provide reports to management or understand which devices have been added during a certain period or are out of compliance.

LogicMonitor needs to invest more in APM functionality. The solution's core focus is infrastructure monitoring, but LogicMonitor is endeavoring to expand into the APM space with the tool. It works adequately but could benefit from additional investment to enhance its performance.

I have been using LogicMonitor for three to four years.

I've had no issues. I rate the solution’s stability a ten out of ten.

The solution is suitable for enterprise customers. Twenty users are using this solution.

Scalability is excellent. Many other solutions cannot scale up to a sizable footprint without hiring more staff, allocating more resources to infrastructure, or obtaining additional budget.

They offer various support levels to clients, allowing them to choose the level of service they prefer. Typically, enterprise customers opt for premium support or even higher levels. With round-the-clock availability and resolution within an hour or two, custom support is also available.

Positive

The initial setup is easier than other solutions, so we partnered with LogicMonitor.

The pricing can vary yearly or monthly, depending on the clients we're working with and their size and scale. For example, the pricing for a customer with ten thousand licenses versus a hundred licenses can vary.

LogicMonitor is a SaaS-based solution, but users can deploy it wherever they want. They can deploy collectors in the cloud, on-premises, on their servers, or VMs. It's flexible in how it can be deployed. However, unlike many other monitoring tools, you don't need to set up a lot of infrastructure.

For an enterprise customer, LogicMonitor may not be considered excessively expensive. It tends to have a higher price tag compared to legacy monitoring solutions, yet it offers more value. Smaller customers with only a few hundred licenses might perceive it as pricier since they have fewer items to monitor and fewer demands. The true value of the solution shines in large, intricate environments where it can effectively monitor hundreds of devices.

In terms of advice, anyone currently using a monitoring solution is likely aware of its shortcomings. I suggest not hesitating to challenge the status quo and explore alternative solutions. LogicMonitor, among others, represents a significant step forward in SaaS-based monitoring solutions. These platforms offer considerable value with minimal ramp-up time and learning curve. Considering a solution like LogicMonitor, it's crucial to identify the gaps in your current monitoring environment. I encourage you to try it; reach out to a reseller, such as myself, or directly to LogicMonitor to explore the platform. It's one of those situations where seeing is believing; you need to experience the value firsthand.

We haven't had any issues with LogicMonitor. All of my clients have loved it and are renewing their subscriptions. It has been fantastic compared to many other tools we've used, especially in the reusability space.

Overall, I rate the solution a ten out of ten.

LogicMonitor is predominantly used in modern cloud monitoring tools. You have servers that you want to monitor for performance, CPU, memory, and so on, or you have a cloud environment that you want to monitor for EC2 instances, ALBs, and more. 

Our LogicMonitor keeps track of everything. LogicMonitor basically gives you the ability to monitor the infrastructure side of your application ecosystem.

The most valuable feature of LogicMonitor is the infrastructure monitoring capability.

Dashboarding capabilities could be enhanced.

It is cumbersome, you must do it all at once, and then you must repeat the process every now and then. If you ask me, I would rather it be automatic because they know what I monitor. If they have a template that they can provide, I can create a dashboard without even trying. 

The issue right now is that I'll have to combine tens of widgets to create my own dashboard which is a little time-consuming and inconvenient.

I have been working with LogicMonitor for seven years.

We have the latest version. LogicMonitor is a SaaS product.

LogicMonitor is a stable solution.

LogicMonitor is a scalable product.

In our company, we have 5,000 users.

Technical support is good.

The initial setup is easy.

The deployment took one day to complete.

They are expensive for the cloud.

If you only want to use LogicMonitor in the cloud, there's a better tool available. But if it's for traditional infrastructure monitoring, it makes sense; it's a useful tool. 

However, if you are a cloud-native organization and want LogicMonitor, I believe it will be a costly investment because there are many better cloud monitoring solutions available.

There are numerous options, including CloudWatch itself, or Grafana with a connection to a CloudWatch data source. You can use Grafana to monitor as well as others, there are numerous tools available.

They are good, I would rate LogicMonitor a nine out of ten.

Right now we have two or three clients that have medium to large data centers, and we use LogicMonitor to give us an overview of the status of the infrastructure: if there are any holes or any issues either with memory, CPU, or storage devices, such as how much storage is consumed. 

One of them is an insurance company which has a presence here in Puerto Rico and in the U.S. It employs about 5,000 people and has two data centers in Puerto Rico and two more in Florida. Their main data center is in Atlanta with disaster recovery in North Carolina. That one is what I would consider a large environment. We also have a medium-size company in the communications area here in Puerto Rico and has about 2,000 employees. It covers all of Puerto Rico. We monitor their infrastructure in terms of servers, storage, and backups, among other things.

We are also monitoring things such as vCenter, its data infrastructure, and NetScaler networking cards. We have a complete overview of the health of the client at a specific moment. 

We're using the SaaS solution. Everything resides on the LogicMonitor cloud. We just have connectors to extract the data from different servers that we have.

It keeps us informed whenever we have an issue. Once it's been configured and LogicMonitor is gathering the information through the connectors, it keeps me and my supervisor informed of any issue on the customer's platform. Sometimes they don't notify us if they're going to reboot a server, so we get notified whenever the server is rebooted. Or if there is a server having memory processor or storage problems, it keeps us one step ahead of such situations. If they call us and say that they have a problem, we can say, "We noticed that you rebooted the server," so it gives us an advantage.

The solution provides granular alert-tuning for devices. For example, in virtual environments you have to take into consideration that the virtual machines have available vCPUs. There is a specific metric called "vCPU per CPU percent" and we monitor that data point because it will let us know whenever we have too many virtual machines for the available CPUs on a hypervisor. That has helped us a lot. We do automatic reports on that every morning, just to check how the virtual environment is behaving in terms of the availability of vCPUs.

We also use its AIOps for root cause analysis and it is very good. We do have to adjust the thresholds at times for specific points that we are looking for, but once that is done, it works like a charm. We have no issue with that at all. We get the alerts we want at the time that we need them. This definitely helps us to be more proactive in resolving issues and preventing problems because we don't have to waste time entering, for example, vCenter to look for metrics. Checking one of the clients could easily take me more than an hour, just to check that everything is fine. With LogicMonitor, we receive the alerts whenever there is an issue and that allows us to work more easily and be more proactive instead of being reactive.

It has also helped us to automate. Depending on the kind of alerts, the person who works in a specific area is notified, so I don't get all the alerts myself. We have storage, virtual infrastructure, and Citrix. So whenever there is an issue with Citrix, the person from Citrix is notified. If it is with storage or infrastructure, the right person is notified.

In the morning, without LogicMonitor, it could take about an hour to an hour and a half to go through every system. Right now, I just check my dashboards and I know if there's something that needs to be addressed. Most of the time we get notified either by email or by SMS if there is something that we need to take care of, in terms of infrastructure and storage. Looking at the dashboard takes about 15 minutes and we know that everything is working fine.

There are at least two most valuable features for us. I really appreciate the reporting function because it allows me to create dashboards that will be emailed to me during the morning so that I have a complete overview of my client's health, within a specific time frame.

One of the dashboards I use a lot is the storage dashboard. We migrated recently from one storage to another, and it allows me to keep everything in focus: How much space am I using, how much is being compressed, how much is being deduplicated? It also provides predictive functionality: How long will it take to fill this disk? That helps us to make decisions on whether we need to buy more space or we need to move or rearrange something within our storage infrastructure. I like that dashboard very much.

The other valuable feature is the alerts. We receive alerts by email and SMS with escalation schemes, so if we notice that an issue is not addressed in a specific amount of time, it will escalate to the next person in the chain. We can rest assured that specific problems are resolved within a specific time frame. Because we receive the alerts by email and SMS, whether I am at my computer or not, I will still receive the messages through SMS on my phone. That is a really cool feature.

In terms of the overall reporting of LogicMonitor, at first it was a little bit confusing. But once you get the hang of it, it's pretty easy to add the widgets and arrange the information that you need or to filter it. It's pretty easy to use.

The process of upgrading some of the collectors has been a little bit confusing. I need to understand that better.

I've been using LogicMonitor for about three years.

It's pretty stable. I haven't had issues with the collectors being disconnected. Whenever I see that there is no data flowing from the environment to LogicMonitor, it is mostly because somebody has changed a password on the host or on my host. As soon as I fix it, everything just keeps on working, straight up.

I believe we've only had an issue where a collector disconnected from the cloud. It happened to my supervisor and he just removed the collector and installed a new one and everything has been working out fine since. The solution's ability to alert whenever we have a disconnection of the collector to the cloud is an advantage.

It has pretty good scalability. We have added several servers and I haven't seen any problems or issues at all.

The topic of increasing our use of LogicMonitor is being discussed, but it's mostly my manager discussing it with the group of managers and the owner of the company. I am not aware of any plans, but it has been mentioned that there is a possibility of expanding.

I haven't used LogicMonitor's technical support. Every time that I need to validate or make some changes in a configuration, the support page is pretty helpful. I have found the answers to all my questions there, so I haven't needed to contact support.

I don't believe the company had a previous solution.

I wasn't involved in the initial deployment. However, in terms of configuration, I have done many rearrangements of specific hardware and discovery of new equipment. That was pretty easy. It didn't take that much for the configuration, mostly for storage or infrastructure, like hypervisors. It was pretty straightforward. The Help page is pretty straightforward too. You will find what you're looking for.

LogicMonitor monitors most devices out-of-the-box. I was pretty amazed with all the documentation on how to configure specific hardware, like Citrix NetScaler ADC and PureStorage FlashArray. Those were pretty easy to configure. Other things it was able to monitor out-of-the-box include Veeam Backup, NetBackup, VMware, Windows Server — all the versions that we're using are supported — SQL Server, Linux servers, Red Hat, Oracle. Those are a few that come to mind.

I believe we have seen return on our investment because we are receiving alerts and dashboards for specific time frames, so whenever there is a problem with some part of the infrastructure, we're able to provide the customer with valid information on what's happening and what was happening. It allows us to document things whenever root cause analysis is required for an issue.

I don't know much about the pricing. My manager handles that. But I believe that, at least from his comments, the pricing is pretty reasonable for the licensing that we have.

The big lesson I have learned from using LogicMonitor is to pay attention to the alerts we receive. Things get escalated to me whenever guys from the other teams do not acknowledge their alerts. I need to pay attention to those because they will tell us whenever a computer or server is being rebooted or if the drives are getting full.

There are six of us in my company on the services and support side. My manager is the person who actually configures it. In addition to me, there is the principal IT consultant for services and support. I do mostly storage and power infrastructure, in terms of servers. We have two more guys who work with Citrix. And there is another guy who does mostly networking. He works mostly with NetScaler ADC.

I give LogicMonitor 10 out of 10. From the time that I started using it, I haven't had any issues with the software at all. I get notified whenever they're doing upgrades and, whenever I need to do an upgrade to my collectors, I get the information with plenty of time to make arrangements if there is something else that needs to be done. I don't believe there have been any upgrade procedures have been done on the platform that have impacted us in any way. It's been a really stable and trustworthy platform.