[Music] hello my name is jason smith and i'm the outbound product manager for iton visibility at servicenow today we're going to go through the agent client collector for itom visibility the agent client collector for itom visibility utilizes a push-based methodology whereby we install agents on servers and end-user computers the agents run periodic checks according to policy and ultimately initiate communication with the mid server and the mid server initiates communication with the instance ultimately the cmdb is being updated via a secure data flow servicenow has a unified agent strategy and this is made possible by the agent client collector framework the agent client collector framework is the agent itself manages communication between the agent and the mid server and also between the mid server and the servicenow instance multiple service now products provide plugins to the agent for example itomhealth provides a plugin whereby we can gather metrics and events from servers and applications agent client collective for visibility is primarily concerned with discovery the agent client collective spoke allows you to execute process flows so that you can run queries and commands on remote devices the agent client collector ships with a standalone version of os query this allows you to run sql queries against a virtual database and it's literally as simple as things like select star from processes where command line like java select star from sudoers or select hostname cpu type from system info let's take a look at a demo first thing i want to do is look at the installation instructions so i'm getting a message here saying that the api key is not yet defined that's just telling me that we haven't set up the mid server for communication with the agent client collector yet there's detailed instructions for many different types of operating systems of course we have msi packages for windows but we also have packages for other systems like debian we also have rpm packages that is used for various other linux operating systems setting up the mid server to use the agent client collector is very simple i've already got the mint server installed so we'll go there and then simply click on set up agent client collector listener this is a port that you can choose i'm going to choose this one okay so web sockets is now available on that mid server and then we can grab the mid server api key we're going to need that as part of the installation of the agent we could choose to generate a new key but in this case i'm just going to copy that one and then i'll use that as part of the installation of the agent so now we're going to install the agent on a windows server i've already downloaded the msi package do the install like this paste the api key in there and i need this ip address and then the port that i chose that's fine so this is telling us that while yes the agent can execute commands it can only execute very specific commands that you allow you could remove this to execute any command that would run under the authorization of the service account that's running the agent but right now we're just going to leave this like this and the installation of the agent is now complete and it's telling us where we could look into the log files after the agent is successfully installed we can have a look at the agent health dashboard to get an overview so in this case we see that the agent has been installed on one windows server this is the record for the agent and we can drill into the server record the agent was able to correctly identify the attributes of the server in addition to correlating to the virtualized layer so you have things like file system software installed running processes serial numbers and tcp connections complete and correct discovery so how does this work we have policies in this case i've got more than one application so i've got monitoring and i've also got the acc for v installed here group by application and it is this policy that i'm interested in this is the enhanced discovery policy a policy is a collection of one or more checks to be executed by the agent in this case we've only got one check these are the commands that will be run by the agent and they will be run at this schedule so in this case it's once a day and then you're able to use the filter to choose which computers this will be executed on so for instance you could choose servers at a specific location or maybe just desktops if you want to take action on the agent you can use the flow designer and make use of the agent client collector spoke this spoke ships with content in the form of flows and also actions for example we could use this flow to restart the agent let's have a look at managing compliance for remote workers for this flow we will run a number of checks if it's a windows server and if it's a linux server then we'll run additional checks so for instance on the windows server we're going to verify that the firewall is in fact enabled so i've already run the check this is the check results and we can see here for instance that we were looking in the os query virtual database to see if the firewall was enabled and we have an answer here back that yes the firewall was in fact enabled flow action responses are put in this table so action responses under agent client collector spoke and here is an example so this is where we're checking to see if the firewall was enabled and this is the response so you're able to use this data for additional processing as necessary the agent client collective for visibility utilizes push-based methodology and is powered by agents installed on servers and end-user computers the agent client collector spoke allows you to extend the system of action so that you can run queries and do commands on remote computers for software asset management customers the agent client collector for visibility allows you to do software metering thank you