hello everyone today we're gonna see a webinar on a native Asian based monitoring and service nate'll you know giving the webinar today's myself Chris Dao Chad Whaley and Cameron Stone first quick a little bit about fruition partners essentially we are how IT harnesses the power of the cloud we're a cloud integration firm with a specialization in innovation and IT Service Management were founded in 2003 and we are the premier partner of ServiceNow calm we offer technology enable professional services supported by a team of over a hundred cloud experts and and delivered over 150 you know enterprise implementations where we build and manage mission-critical cloud solutions on the ServiceNow platform so this is just a quick quick note today about the team that's bringing you this webinar so this is my team the products and platform team we focus on basically platform development so what does that mean if you have a ServiceNow implementation and you've rolled out you know a few of the modules and the IT Service Management suite maybe incident change seemed to be asset what have you you know what's next we build custom enterprise scalable applications you know to manage almost anything in the enterprise that's not under that umbrella we take the basic building blocks of ServiceNow the best-in-class workflow engine that the database system the cloud SAS nature of the tool email handling and processing and we build you know enterprise scalable applications we've done some very amazing work as you know partners like coca-cola Blue Cross Blue Shield and some of those some of the greatest social networks in Silicon Valley where we build custom solutions managed data centers to manage access management to build up ServiceNow systems that integrate with telephone systems would take inbound call and route them directly in the ServiceNow and a lot of tickets and issues we've even built solutions for clients like Fermilab where you know lab equipment is integrated with the ServiceNow platform it actually makes outbound calls issue arise to support technicians to maintain a top level of support so that's what the platform team is and we also focus on on products as well where you know we build custom solutions on some of the platform as you see here for instance Bomgar we have an integration suite that will enable remote desktop and remote support and control directly from ServiceNow whether it's clicking on a CI and taking control of that CIO remotely from your desktop or allowing you know one-on-one session support sessions with your end-users all that can be enabled within ServiceNow we have a you know partner partnerships with folks like Clio that allow us to do integrations with telephone systems the route calls you know to end from ServiceNow make outbound calls and SMS is estimate send SMS messages directly from your instance I also do some very exciting things with Google basically you know when you get a notification or approval request and you are you know Google Gmail Enterprise client we can bring that ticket bring in incidents bring in approvals directly into your ServiceNow instance directly in your email and then obviously many other integrations and and a custom you know products based on demand per client request integrating things like Google App Engine Amazon Web Services you know whatever we need to meet the specific nature of the requirements that you guys have okay and so just just a quick note on our approach on transformational IT we have a number of line of businesses internal to fruition partners we do education ITIL foundation and master level training with a pass rate of 93% we also do you know serves now specific specialized training where we teach folks how to be admins and advanced developers we also do process consulting and obviously for implementations we do you know process re-engineering and design will come in your organization take a look at the tools you have and the people you have and then re-engineer that yeah specific to you you know IT Service Management and and the ServiceNow model and and and obviously kind of with that a ton of automations integration and process automation you know just making an entire you know ITI organization as streamlined as possible using service catalogs automate as many requests to take as many kind of the manual steps out of top-level service and support delivery to your organization so we essentially do deliver a deep practical knowledge of service now local technology and and and practical you know operations management with each engagement and with that I'd like to introduce Chad Whaley and Cameron Stone better that we'll do a deep dive on basically server management and agent based monitoring with that I'll toss it over to them so it's it's not gonna be death by PowerPoint today I promise I'm really going to going through about six or seven slides just kind of lay the groundwork on what exactly we're going to be going through when I do the demo but basically we want to take time today to really demonstrate how the ServiceNow platform can be used to build customized solutions that really eliminate a lot of the gaps that exist between the tools where you're executing your processes and managing your efforts like ServiceNow and the tools where that actual look is being done once they get ready to implement what they're doing so some of the monitoring tools from the other management tools that teams have to manage their actual systems kind of bridge that gap and and bring most of that into service now now with this example in today's webinar we're really going to demonstrate that through the use of a custom-built agent based monitoring solution but the big piece is that it's managed natively inside a ServiceNow so there's there's no separate interface there's no special integration everything's kind of built off of that ServiceNow platform so all the activities you do in service now is actually driving activity outside in the real world so why is monitoring a good example to cover this kind of thing if you look at monitoring tools there's there's some challenges with them when you start talking about taking the things that monitoring management teams do and bringing them into an IT service management tool and process execution bi-directional information is extremely difficult to build between multisearch management tools where you're doing your incident in event management and the systems where that data is actually being defined and tracked you have to build custom integrations for getting those two tools to talk to one another correlation and suppression can also be a bit of a challenge because now you've got two environments that are trying to collect the same bits of information but they're not necessarily talking the same language ServiceNow CMDB realize heavily on relationship management and relations between items you're a monitoring tool may or may not do that and if it does it may do it in a data structure that isn't the same as how ServiceNow manages the CMDB there's also challenges around escalations so if an event is happening quite a bit so you're getting a lot of chatter from your monitoring tools you know how does that escalate up to maybe from an event to an incident or increase the priority or severity of that event or incident those are all things that have to be worked out on a case-by-case basis when you integrate different systems because the the flow of the data and the manage the management structure that information may not be the same data alignment you know those are that's a component that goes into the other items I just talked about but really foundationally you have two different school sets that you're trying to get to speak the same language and those metrics may not even exist in a lot of cases one of my more common examples that I see is a monitoring tool we'll only have a concept of a priority whereas in ServiceNow and you're trying to manage excuse me you're trying to manage your I told processes from an incident and event managers and event management standpoint using a combination of impact and urgency to drive a party so when that monitoring tool tries to send a priority over what kind of assumptions do you have to make about the impact and urgency so that there's no ambiguity between what you know what that I told process means what flow that I took process needs to go through and what that event really is trying to tell you and then from a versioning and auditing standpoint it's it's extremely difficult to keep some of these environments in sync because a lot of the reporting that you get out of a monitoring tool is more associated with the alerts themselves and not necessarily with managing those alerts so that if something changes in that environment or if you know if someone changes a monitor or if you roll out a new version where's that new version deployed currently where do we have gaps those types of things can be difficult because those tools weren't necessarily built with some of those I told practices in mind now there's also some opportunities where you can add or improve some of your processes that are either working or just aren't quite aren't quite there yet fewer tools and integrations is a big one if you can eliminate a tool or eliminate an integration that's support cost that's administration that's just general team overhead that you can eliminate so you can focus on doing the things that are more added value for your business change management is another huge one so imagine being able to have your monitoring solution implemented inside of service now and those monitors are tied back directly to CIS and in effect they're actually see eyes themselves so when someone brings forward a change to say upgrade a business application that you're monitoring with a live foul monitor that enters the change management process you can see it on the you know the business relationship maps you can see it when you go to the cab so you have immediate visibility to the fact that well this application is being upgraded maybe my log file monitors for this application need to be updated because the log file for that app is now moved those types of things it can take that monitoring team really embed them into the change management process so that monitors are are much easier to keep current and you're not finding out that the monitor is no longer effective after the changes already been implemented you can get in front of that request management's another big one since these monitors are actually defined and managed inside of the tool the request management process can tie directly into it so if you deploy a request management or if you have a service catalog you can build the requests let the users fill out the monitoring information requests on what they want and then if you have a goal for automation or if you have runbook things like that you can actually automatically provision based on those requests so a user wants to monitor a service on a Windows server they go into the Service Catalog find the request for monitoring a service on a server fill it out hit submit then based on the workflow if it gets approved or if it's something that you envision is not being required for approval it the system would go in automatically provision create that monitor and then the agent on that server would pick that up and start monitoring as soon as that's approved and created there's also bulk updates in imports so for those of you that are already inside a service now you've probably seen the list edit feature some of the other bulk update capabilities that are inside the tool from an administrative point of view because those features exist in ServiceNow it becomes extremely easy to manage these monitors and these these configuration items from a mass update standpoint so if if someone does replace or upgrade an application and the log files changed you can either do an import but do a list update to all of the monitors for that application no matter what agent that it's deployed on you can do the bulk update to change that location rather than have to go visit each one individually and then push them out or deploy them and you know wait for the server to come back up if it's down for maintenance those types of things are no longer necessary and then from a reporting standpoint it's very it's very nice being able to tie the reporting of the alerts and events that are coming into the system directly back to the monitors that were defined to generate those events you can see reports like which of my monitors generating the most events and then let's say you also want to tie event to incident management or even problem management you can walk that down to say show me show me which events end up in generating the most incidents or the most problems and then you can use that to focus on the ones that are have the highest opportunity for revamping you can use that to identify which ones maybe need to be expanded to go into more more in depth so you can get more proactive with them so they are turning into incidents as much you know all those types of post activity reporting and process improvement reporting as available by having all this encapsulated within the same tool set the architecture of the what we built here is a little bit twofold there is a custom developed agent that does run on a server it is a c-sharp application basically the training as a service that agent will check in with the ServiceNow instance on some interval typically you would do this type of thing once or twice a day for this demo it's doing it every couple of minutes just so that we have some speedy results once it checks in to the ServiceNow instance it's actually going to download all of the policy configuration settings for its agent so all of the policies that it needs to use to monitor all these instructions it pulls those down and also checks in with the instance to say hey I'm here I'm healthy I'm alive then it runs every again at an interval but for a demo it's running every minute but it will cycle through all of those policies every minute to check to see if there's anything that it needs to take action on some policies you may want to learn every hour some of them you may want to learn every minute the agents going to look every minute to check and see if there's any policies that it's now their turn to run on the service mail side assuming the agent detects or executes a policy and detects an event it's going to afford that event up to service now and then ServiceNow is going to make a couple decisions using strands from scripts it's going to look to see if the agent is disabled or if the policy is disabled maybe the agent or the policies under maintenance if it's disabled then it will suppress that and not create the actual incident and the reason we do that is there may be some lag time because these monitors are running very frequently there may be some lag time between when you actually start your change and when you actually indicate that or actually turn that agent aw so you can indicate the Bajan is is in maintenance and then the five or ten minutes it takes you to log onto the server and actually physically stop the agent you won't get events in between that gap that's based on your definition not the actual in the agent is running or not there's also a check to see if there's already an active ticket for this particular monitor so if you've got an event to monitor the see drive if it sends that event and then later on it tries to send another one if that event is not closed it will suppress it completely there's also another check to see if it's being suppressed so because these monitors are related to one another as sea-ice you can actually put in a suppression policy so I can say that the monitor for service 1 2 3 is suppressed by the disk monitor because in my environment if the disk is full then this service typically fails so you can actually put in that suppression and it will log that it's suppressed it but it doesn't actually create the event and then there's a there's an extra scenario where it doesn't actually suppress the event but if you supply a parent monitor full monitor so if I say you know process monitor one is a parent of process monitor to any events they get created for process monitor 2 will select any active events for its parent monitor as its parent event and now I will actually show that when we get into the demo you can see it a little more visually from a technical standpoint some of the components that we used to build this out on the ServiceNow side we use the table extensions so you know the events that we're generating are built off of the task table so you can still do you know your your your workflow or your own task management practices the the definitions of the monitors and agents are extended off of the CMDB so they're actually classes in the scene DB that way we inherit all of the benefits and capabilities that come with CMDB and the relationships and the fields and those types of things we also use a web service import set that's the primary component that allows us to communicate between the agent and ServiceNow all of the instructions that come from it ServiceNow or get set to ServiceNow by the agent are being done through the use of these web services and input sets now we use the transform map on the incoming events so the events that are being sent by the agent are managed inside of a transform map that's correlating the fields so you know it's translating the fields that the agent uses into the fields in the actual events table and it also does the post processing activities where we check to see if there's already an active defense we check to see if there's already to see if there's a parent or if it needs to be suppressed that's all done in the transform app script there's also a seem to be relationships I mentioned you know having the policies as CIS allows you to relate them together and that seemed to be relationship capability is really what's at the heart of us being able to drive suppression correlation and then from an agent standpoint I mentioned this earlier but the agent technology is basically a custom-built c-sharp application it's running as a service on the the server and it uses web services to communicate up to ServiceNow now before we get into the demo you know why an agent there's there's a bit of a battle that always rages between you know different schools of monitoring should I use an agent based monitoring solution or should I do it agent list both sides really have good points but they also come with their own sets challenges in our case an agent was preferable because we're really trying to do in-depth service in depth monitoring on a server and there that really goes beyond the capabilities of what SNMP can really do for you so putting an agent on there allows us to monitor the server in a way that's efficient not only from a server performance standpoint but also from a network standpoint if we were to try to monitor some of this stuff with an agentless monitor we would have to use RPC calls or use WMI to remotely connect and those types of things can typically chew up a lot of network traffic especially when you start talking about deploying this type of thing to a global enterprise where you may have sites who have limited capacity on their local traffic but we are actually shooting for a hybrid model we're looking at adding some network level monitoring some device you know network device level monitoring that is based on SNMP we don't have it to demo today but Cameron stone is on the call and he's really kind of spearheading that agentless piece of it and he does actually have a proof of concept that we've gone through in the last couple days and it's that's working very well so hopefully pretty soon we'll also have some SNMP based agent loss monitoring that we can demo for you and with that we'll go into the demo so my fruition instance here you see at the top I've just got my my free site application and free sites just what I decided to call this we've got a couple things that we're using to manage here we've got the agents so these agents are actually the physical representations of the agent this is what the agent checks in with this is how we know what version they're on it's it's really the central place well we can have common understanding of what agents we've deployed what servers are employed on what status they're in that type of thing this is really nice because we have a last check-in field that we've added so I mentioned the agent checks in and talks to our ServiceNow instance on an interval this check-in allows me to add a glance understand what's the help of my environment right how how many agents do I have that are not communicating with me and then if I do have some I can very quickly trace back to the server and see if there are any open chain records for that device there's also the version version is another nice one if you're going through an upgrade so let's say you have version one deployed and your gut grading diversion - as you start pushing that agent out and deploying that into your environment the agent itself will automatically check in and tell the instance what its version number is so you can see I've got two old ones here that have not checked in in a while and they were on version one or point one and now my new agent is version 1.01 so I can see that this one has checked in it's healthy and it has been upgraded to the new version so if you have you know if you're an environment where you have thousands of servers you can easily get reports to show you you know how many of your agents are on the old version how many of your agents have not checked in in the last 24 hours those types of things now we also have the monitors so I'm gonna open the agent record here and you'll notice at the bottom because each monitor is tied to an agent I can see all the monitors for this specific agent so it's very easy there intuitive view where you can kind of go into an agent and see what that agents doing and then you can drill down directly into a monitor and then from the left nav I can also go and see all of the monitors for this environment now the monitors themselves are structured in a way that basically the the administrator the user is going to supply all the information that the agent needs in order to not only watch the server or watch the environment for that event but also what that event needs to do once it when it occurs so we've got the agent that this monitors for if we wanted a correlation to another type of monitor we could put that here we have what assignment group we want this moment to be assigned to and the beauty of this is you can put this directly into this event but if you're using the assignment rules portion of ServiceNow where you can use conditions to decide who to assign it to you can easily use that to decide where these events get assigned because they're extended off of tasks and the assignment rules work for any task so you can harvest code it in here or you can do a conditional based approach to decide who gets assigned to the relate CI is basically a field where we can hard code what configuration item to relate to this event when it fires again this could be blank or you can use other logic to decide what CI it is if that information is available to you we have a status field or we can identify if this monitor is currently installed in working or if we're doing maintenance on it these are the out-of-the-box statuses I haven't modified them some of these may or may not make sense based on your environment but that's easily manageable by identifying you know what choices you want to be available we also have a type so the type of monitor will drive the content of the form so this one is a Windows disk so you can see it's asking me what's the distain and then what prefer free percent I want if it was a process you can see now it's that it's switching over the process name and preferred state same thing with service so it's got its gonna tailor the form to simplify your data entry so you don't have to you know know which fields are required and which ones aren't it's going to tell you all of that so it's an intelligent form we also have the check every field the check every is basically polling interval so how often does the agent need to check to see if this service is running or to see if this disk is full and we've got to set the five minutes and you can go to hours days it just depends on you know your individual case for that particular monitor we also have the impact urgency and priority this does align with service nails out-of-the-box matrix for defining priority if you're not using that or if you prefer to have your own you can certainly modify that to either only use priority or use a different calculation model that's perfectly perfectly capable so capable to meet your needs down towards bottom we also have the related items and this is where I mentioned that we're doing suppression so this particular disk monitor will suppress the service one and process one monitors so this process monitors for the cmd.exe process and the service one is for the SNMP trap process so if this if this disk policy has fired and there's an active event which you can see down at the bottom there is here's an active event so this one is currently in flight because this is active these two policies will not generate new events they will come in and enter the queue but the transform process will prevent them from cutting incidents or cutting events because they're being suppressed and instead it's logged in here so you can see transform we suppress that event because this event is firing right so you still have this what's being suppressed in case something that you don't want to be suppressed as being suppressed you can go in and clean some of that up you can do reporting and kind of get all that capability as well so that's a disk monitor I'll show you some of the other ones here's a process so again we just supply a process name and then whether we want it to be running or not running and then we also have the service one same thing running you're not running and then you just supply the service name one really cool feature about this let's say you're a discovery customer or let's say you have services in your CMDB you can easily take this field and turn it into a reference field so that you actually physically reference the CI for that service and you don't have to type it in you don't have to go look it up all you have to do is use the use the magnifying glass and go find it you can do that before the service you can get for the process to disk any of that and then the final monitor type we have is the log monitor and this one's a little more complex we're actually using a couple things to get to this but basically we supply what type the type of monster it is and how often we monitor but then we also have log patterns so down here is where we supply what we want to look for in that log so if I click on the pattern you can see we've got the path to the log file whether or not it's a custom one or it's a Windows Event one I'll show you we supply what type of or what word we want to watch for I've got this simplified just so that the demo goes you know so it's not too tough to look at in the demo but this this will take a regular expression so I could do you know regular expression meditation and that it would take that so it's just a regex pattern you can supply same thing for the exception so if if when the lock file reads or when the watch or monitor reads out and will align in the live file its going to look to see if it contains the word error and if it does contain the word error but it does not contain one report then it will fire the effect but if it says you know error I have removed policy 1 2 3 then it will not fire the event because it having removed then it means it's an exception to the rule and this can also be a regulation the pattern threshold is how many times that this pattern has to match between check intervals so if you're checking it every 5 minutes and you want this to happen five times in five minutes and all that's considered in national events then you may just put five or three or higher than any one pattern options you do things like ignore case reply name and all kinds of fun stuff with the pattern options really just regular expression there's also the event log so this is a custom log file so if the other applications which writing to a text-based log file that's what the simple one is the Windows one is a little different you still use the pattern that you also supply which lock so application and their system log or if you have your own custom log you can add that in here as well you supply what type of event and these are the you know the other box event types in the you know windows event management system so you got aerial wanting information you've got source so typically applications will have a specific source that they use and then you can match on specific numbers so an event 100 in that five hundred we're doing event match an exception so to put up here in these fields is what will automatically generate this pattern so this is the config file basically for this particular pattern and then this config is the whole collection of all this is all of the config patterns for this particular policy so all four of these will roll up into this big config file if that agent will download and use when it checks the monitors now why you know what are we going to get out of doing all this work well we get the events right so these are events that have been firing I turn a bunch of these off they've been kind of generating throughout the day then you can see I've got my dis spaces over my own percents I've got some log matches I've got some servers services down so if I open this particular policy or this particular event I can see there was a lot of nice detected by this particular policy and then this is the line that it detected conflict so that's the actual line from the log file it gets copied into the and then at the bottom if this were appearance that was those the chip as well I think I have one anymore so here's a parent's event and you can see down here these are the children so this service is down and because this particular process made me tied to that parent baby made me type of that service they've generated both events and then put them together as a parent-child type correlation and then as I showed you earlier if there were suppression going on and see these events are being suppressed so if I go that that's 36 the fact that this disc is currently full according to this policy means that that particular monitor was not being allowed to generate an event from a technical standpoint for those of you on the call that may be interested in web services side of things this is the event queue so the this is the queue or all of the events that are coming in to put prior to them being transformed into an actual event so you know before they are suppressed you get suppressed like this one this one was suppressed it's still in the key so you can still report on total number of events and all that but you're preventing them from causing teams to have to go to work by closing them out because you basically decided that yes and you sent me this event but it's not a candidate for anyone to do any kind of action on it not open up one more here so you can see generated the policy so I can trace back and forth between all of these environments and then from a policy or from a monitor I can see all the events so as you can see there's a lot of potential here there's a lot of capabilities there's you know room to grow you want to have the SNMP based monitoring there's there's a lot of things that we want to extend this to but I think it's a really good start really shows you know some of the benefits of being able to use the platform the ServiceNow create and design solutions that you don't have to be afraid of I think you know if you look across the industry there there's a lot of apprehension the word customization gets used and you know to some degree that's best justified its you know you want to be careful customizing out-of-the-box things and you don't want to take know something that a vendor designed to do on purpose and completely change that so ServiceNow approach that is not to just tell you you know don't don't on apply the late incident works they give you a platform where you can basically build your needs of what you do into a solution that doesn't necessarily butt heads with their vision right being able to create your own tables that extend off of tasks being able to create your own fields that align into the data types can be done and ServiceNow in a way that doesn't prevent you from being able to upgrade it can be done in a way that allows you to manage it long term just scale it up to larger market environment businesses continue to grow and become more successful it's a it's a very robust platform that really eliminates a lot of the need or all of that angst around you know what happens if I build custom tool that the demos over before we jump in answering questions I will say if there's some questions I don't get to today please stay in touch with us I will I will try to follow up on any questions we didn't get to verbally through email and then following the on the webinar follow us on Twitter we've got our Twitter handle here find us on Facebook loss on again and then you can also visit our website for supporters calm for those of you who into our website but it's been a while I'm encouraged you to go back recently recently just did a website and it is awesome I love a new structure it's a lot easier to find stuff things like our most recent webinar right there on the front page so you know it really finds the way around and really sling what things we do what we're all about on that website a lot more efficiently than you probably could have a few experiencing results and just a quick note on the webinar today a webinar is recorded it will be posted hopefully sometime next week the transfer process we get to your friends or your colleagues who pull up some questions here develop agent ice being all related to Windows we are looking at moving those out in doing Linux and H parts and some of the other operating systems as I mentioned where Cameron has already made great strides and doing as these pieces network devices and you know SNP level monitoring servers but the plan right now is to take take a really solid implementation of the Windows model and then extend that same structure over to Mike's environments and add a couple other things like the assist log based monitoring data points that are available and extend what we've got into use those so that's that's coming question about how the agents is packaged it is in an MSI format it's basically it's a service installer that's generated it's a fully supported that's fine you have things like a foundation or if you have tools you can certainly build the agent installation process into that and again another one of the beautiful spot service now is if you have sort of catalog you can't automatically provision that as well so user submits the source catalog request I have a monitor on a server it's approved the run with automation workflow or your integration while mentally keep that to come off and put up into their service catalog request the types of mileage there seems to be a good bit of interest in us monitoring the Linux environments and that's that's very near coming there's like a question really good question on how how to assign a monitor for all servers so let's say you have I'm gonna watch an event for every single server there's a couple ways to do that you know service panels out of the box bulk important list edit processes you could dump all your servers in hotel and then define that monitoring otherwise if that's a common use case it's extremely simple to go into service we create the class for my actions and there's some type of automation that will dynamically create those either pull that information down on some kind of schedule or you would need to have it basically you know be configurable to talk to our instance instead of its central management environment so Nagios is you know one of the more open source ones so now yes that would be a good example of where you wouldn't necessarily have to use not uses core implementation you could you know kind of take that and update some of the config files and some of the content of Nagios to have it point to our instance to get its instructions rather than you know look back to the central environment for its config files and just a couple more and then I think we'll be done can I take advantage of existing SNMP meds that's a really good question I would expect that it could but I think Cameron would be a better person to answer that since he's doing the SNMP portion camera use are you still on yes can you yep perfect so did you hear the question here me yes basically any any noobs that are gonna be installed on the mid server are accessible so from whichever vendor you might be using if you get the mid library and install it on the mid server we have access to those nibs and can pull just about anything out there so any ol IDs it's it's pretty much endless with the SNMP I'm mainly focused with the networking stuff at this point as we are working on the Linux side as well so between Linux and the Linux agent the Windows agent and then the SNMP devices for network we pretty much should have everything covered great I appreciate you helping me with that one there's only two more questions one of them was what server platforms I mentioned earlier Windows is there now Linux is coming I'm you know when we do Linux we'll do it in a way that it's it's more UNIX based so that way it's extendable to hbox or Linux from a Windows standpoint it'll work on pretty much any version of Windows post Windows 2000 so 2003 2008 2008 r2 I've pretty sure to work on mm but it's be honest with you I haven't tested it on that yet so I don't want to give you a firm yes or no on it but if you have a use case for that we can certainly talk it through and see um you know if there's anything we need to watch out for with monitoring Windows 2000 and then I'm not entirely familiar with the tool that's mentioned this question but since we're using PRTG Network Monitor I don't recognize that acronym off the top of my head but as I mentioned the big thing there is when you define your monitoring config there you're providing a data set you're providing the content and the monitor to tell whatever monitoring tool all the information it needs in order to you know execute that monitor and watch for that event so assuming that network monitoring tool can take input from an external system and use that input to create define or activate a monitor then that's certainly a candidate for this type of this type of integration or or custom application and I think that is it for the questions so unless we get another question here in a couple seconds I'll wrap it up again check us out on social media sites hit up our new website it's beautiful and I just want to thank everybody for Dallin and today hopefully we've at the very least generated some ideas for you on how maybe you can take service nails development platform and you know add either custom tools or add some some robust enhancements to your current processes you can really go beyond just doing you know IT Service Management and really take it to a level where you're adding tools and capabilities that helps you know your individual IT teams execute and manage their environments more effectively through automation through much tighter you know coupling not just integration but actual data coupling so that you can realize even more value out of the investment that you make in your ITSM tools and with that do one last check and with that thanks again I hope you all enjoy the rest of your days