![]() ![]() If not, escalate to senior staff." It has sped that up quite a bit. It allows us to route tickets appropriately and then, they already have little checklists that pop up for common alerts that say, "If it's this and this, try this. It has been great just because of the integration with our PSA ticketing system and the way we can set triggers, priorities, and levels of urgency with notes and all the other cool features they have there. It has been great to allow our teams to focus on high-value tasks and delegate low-level tasks to junior staff. ![]() What used to be a four-hour fix is now done in 30 minutes. We are able to get that information really quickly, and we don't have to go back and forth. It has saved an insurmountable amount of hours of network outages and down networks. ![]() Now, we have a live reactive changing diagram that allows our network guys to go straight to the actual device that's causing the network issue somewhere in this region and start troubleshooting that right away versus having to troubleshoot three, four, or five devices in that general area blindly, and then, eventually getting to the device they need to work on. We can see what's going on with all our devices which we couldn't see before without having to log into each device individually, or we had to use a diagram that we made when they were set up and refer to that. The way Auvik portrays the network from the outside looking in is like being Zeus on a little cloud. Once you get your IT team members used to it, when you're having an issue, for example, while trying to SSH to something, they will go to Auvik first just because they have the geographic map, and they have these little dummy-proof exclamation marks. It makes it a lot easier for our IT teams to have visibility into remote and distributed networks. ![]()
0 Comments
Leave a Reply. |