![\"\"](\"http:\/\/docs.unitplatform.io\/wp-content\/uploads\/2018\/05\/disc1.png\")
<\/a>Menu – Discovery<\/p><\/div>\n
This interface will display a list of all discoveries already added and scheduled. To create a new one, click the add button.<\/p>\n
<\/a>Add Discovery<\/p><\/div>\n
<\/a>Discovery configuration<\/p><\/div>\n
Some requirements are needed to run the Discovery, as follows:<\/p>\n
- \n
- Discovery name:<\/strong> The default is filled out with the date and time of register, but you can change the name.<\/li>\n
- Site:<\/strong> Here you can choose whether the scan will be done locally or on a remote network via the Unit Site.<\/li>\n
- Address or IP range:<\/strong> In this field you must inform the networks or IP addresses with which the Discovery will detect the devices. Use a semicolon “;” for more than one IP address or “ENTER” as a separator. For an IP range, use one of the following formats: 192.168.1.1-24 or 192.168.1.1\/24<\/li>\n
- Credentials:<\/strong> They are required for the Discovery to detect items within the device that was found. For example, if the Discovery detects a device with SNMP, it uses the chosen SNMP credential to detect the items that can be monitored within that device.<\/li>\n
- Schedule discovery:<\/strong> This feature allows you to schedule a specific date and time for the execution, because the scan, depending on the amount of items, can affect the performance of your network. Besides scheduling, you can add a recurrence to run a specific discovery repeatedly and check whether new items or devices have been found.<\/li>\n
- Enable detection of TCP ports:<\/strong> This option allows the Discovery to scan open TCP ports for each detected device.<\/li>\n
- Enable detection of Windows counters (Performance Monitor):<\/strong> When the Discovery detects devices with Windows operating system using Agent credentials, it will list all Windows performance counters avaliable for those devices. This option may cause the Discovery to be slower, but it will bring much more details from Windows devices.<\/li>\n<\/ul>\n
After filling out these fields, you can execute the Discovery by pressing the “Start Discovery” button, or you can save it via the “Save” button if you have the schedule option enabled.<\/p>\n
The results will be grouped by device (device name and IP address) and by expanding the device, the items groups detected and their counters will be displayed.<\/p>\n
![\"\"](\"http:\/\/docs.unitplatform.io\/wp-content\/uploads\/2018\/05\/disc4.png\")
<\/a><\/p>\nThe system will bring the most important items already checked. These markups are suggestions and you can change these items in this step.<\/p>\n
Besides checking and unchecking the item to be monitored, you can also edit it by clicking the “Edit” button on the right side of the service.<\/p>\n
After finishing these steps, click “Save” and the system will start monitoring your devices.<\/p>\n","protected":false,"raw":"The Discovery feature is responsible for scanning networks and detecting devices. In Multisite Monitoring you can create as many discoveries as you like and even schedule them.\r\n\r\nTo scan your network using Discovery, go to Multisite Monitoring > Network Management > Discovery.\r\n\r\n[caption id=\"attachment_670\" align=\"alignnone\" width=\"255\"]
<\/a> Menu - Discovery[\/caption]\r\n\r\nThis interface will display a list of all discoveries already added and scheduled. To create a new one, click the add button.\r\n\r\n[caption id=\"attachment_671\" align=\"alignnone\" width=\"522\"]![\"\"](\"http:\/\/docs.unitplatform.io\/wp-content\/uploads\/2018\/05\/disc2.png\")
<\/a> Add Discovery[\/caption]\r\n\r\n[caption id=\"attachment_672\" align=\"alignnone\" width=\"1000\"]![\"\"](\"http:\/\/docs.unitplatform.io\/wp-content\/uploads\/2018\/05\/disc3.png\")
<\/a> Discovery configuration[\/caption]\r\n\r\nSome requirements are needed to run the Discovery, as follows:\r\n- \r\n \t
- Discovery name:<\/strong> The default is filled out with the date and time of register, but you can change the name.<\/li>\r\n \t
- Site:<\/strong> Here you can choose whether the scan will be done locally or on a remote network via the Unit Site.<\/li>\r\n \t
- Address or IP range:<\/strong> In this field you must inform the networks or IP addresses with which the Discovery will detect the devices. Use a semicolon \";\" for more than one IP address or \"ENTER\" as a separator. For an IP range, use one of the following formats: 192.168.1.1-24 or 192.168.1.1\/24<\/li>\r\n \t
- Credentials:<\/strong> They are required for the Discovery to detect items within the device that was found. For example, if the Discovery detects a device with SNMP, it uses the chosen SNMP credential to detect the items that can be monitored within that device.<\/li>\r\n \t
- Schedule discovery:<\/strong> This feature allows you to schedule a specific date and time for the execution, because the scan, depending on the amount of items, can affect the performance of your network. Besides scheduling, you can add a recurrence to run a specific discovery repeatedly and check whether new items or devices have been found.<\/li>\r\n \t
- Enable detection of TCP ports:<\/strong> This option allows the Discovery to scan open TCP ports for each detected device.<\/li>\r\n \t
- Enable detection of Windows counters (Performance Monitor):<\/strong> When the Discovery detects devices with Windows operating system using Agent credentials, it will list all Windows performance counters avaliable for those devices. This option may cause the Discovery to be slower, but it will bring much more details from Windows devices.<\/li>\r\n<\/ul>\r\nAfter filling out these fields, you can execute the Discovery by pressing the \"Start Discovery\" button, or you can save it via the \"Save\" button if you have the schedule option enabled.\r\n\r\nThe results will be grouped by device (device name and IP address) and by expanding the device, the items groups detected and their counters will be displayed.\r\n\r\n
<\/a>\r\n\r\nThe system will bring the most important items already checked. These markups are suggestions and you can change these items in this step.\r\n\r\nBesides checking and unchecking the item to be monitored, you can also edit it by clicking the \"Edit\" button on the right side of the service.\r\n\r\nAfter finishing these steps, click \"Save\" and the system will start monitoring your devices."},"excerpt":{"rendered":"","protected":false,"raw":""},"author":1,"featured_media":983,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_pt_post_content":"A funcionalidade de Discovery tem como objetivo varrer redes e detectar dispositivos. No Multisite Monitoring \u00e9 poss\u00edvel cadastrar v\u00e1rios discoveries e at\u00e9 mesmo agend\u00e1-los.\r\n\r\nPara cadastrar um Discovery em sua rede, entre em Multisite Monitoring > Gerenciamento de rede > Discovery.\r\n\r\n[caption id=\"attachment_670\" align=\"alignleft\" width=\"255\"]<\/a> Acesso ao Discovery[\/caption]\r\n\r\nNesta interface ser\u00e1 exibida a lista de todos os discoveries j\u00e1 realizados e agendados. Para criar um novo, clique no bot\u00e3o adicionar.\r\n\r\n[caption id=\"attachment_671\" align=\"alignnone\" width=\"522\"]<\/a> Adicionar discovery[\/caption]\r\n\r\n \r\n\r\n[caption id=\"attachment_672\" align=\"alignnone\" width=\"1000\"] Configura\u00e7\u00e3o do Discovery[\/caption]\r\nPara executar o Discovery s\u00e3o necess\u00e1rios alguns requisitos<\/h2>\r\nConforme abaixo:\r\n
- \r\n \t
- Nome do Discovery:<\/strong> por padr\u00e3o est\u00e1 preenchido com a data e hora do cadastro, mas pode ser alterado para qualquer nome.<\/li>\r\n \t
- Site:<\/strong> Essa op\u00e7\u00e3o \u00e9 usada para escolher se a varredura ser\u00e1 realizada localmente ou em alguma rede remota, atrav\u00e9s do Unit Remote Network.<\/li>\r\n \t
- Endere\u00e7o ou range de IPs:<\/strong> Neste campo \u00e9 necess\u00e1rio informar as redes ou endere\u00e7os que o Discovery detectar\u00e1 os dispositivos. Voc\u00ea pode utilizar ponto-e-v\u00edrgula \";\" para mais de um endere\u00e7o IP, ou \"ENTER\" como separador. Para um range de IPs utilizar um dos seguintes formatos: 192.168.1.1-24 ou 192.168.1.1\/24.<\/li>\r\n \t
- Credenciais:<\/strong> as credenciais s\u00e3o necess\u00e1rias para o Discovery detectar itens dentro do dispositivo encontrado. Por exemplo, se o Discovery detectar um dispositivo com SNMP, ele utilizar\u00e1 as credenciais escolhidas de SNMP para detectar os itens que podem ser monitorados dentro do respectivo dispositivo. Existem v\u00e1rios tipos de credenciais e podem ser utilizadas v\u00e1rias em um mesmo Discovery, inclusive do mesmo tipo. Voc\u00ea pode ver mais detalhes sobre credenciais neste artigo.<\/li>\r\n \t
- Agendar Discovery:<\/strong> essa funcionalidade permite voc\u00ea agendar um dia e hor\u00e1rio espec\u00edfico para a execu\u00e7\u00e3o, j\u00e1 que essa varredura, dependendo da quantidade de itens, pode afetar o desempenho de sua rede. Al\u00e9m de agendar, voc\u00ea pode adicionar uma recorr\u00eancia, para visualizar futuramente se novos itens ou dispositivos foram encontrados.<\/li>\r\n \t
- Habilitar detec\u00e7\u00e3o de portas TCP:<\/strong> Permite que o Discovery, para cada dispositivo detectado, fa\u00e7a uma varredura de portas TCP abertas no respectivo equipamento.<\/li>\r\n \t
- Habilitar detec\u00e7\u00e3o de contadores do Windows (Performance Monitor):<\/strong> esta op\u00e7\u00e3o faz com o que o Discovery, quando detectar equipamento com sistema operacional Windows utilizando a credencial do tipo \"Agent\" traga ou n\u00e3o todos os contadores de performance do Windows. Essa op\u00e7\u00e3o pode deixar o Discovery mais lento, por\u00e9m com muito mais detalhes de m\u00e1quinas Windows.<\/li>\r\n<\/ul>\r\n
Ap\u00f3s preencher esses campos<\/h2>\r\nExecutar o Discovery atrav\u00e9s do bot\u00e3o \u201cExecutar discovery\u201d. Ou salvar, atrav\u00e9s do bot\u00e3o \u201cSalvar\u201d, caso voc\u00ea tenha habilitado a op\u00e7\u00e3o de agendar.\r\n\r\nOs resultados ser\u00e3o agrupados por dispositivos (nome do dispositivo e endere\u00e7o IP) e expandindo o mesmo, ser\u00e3o exibidos os grupos de itens detectados e seus contadores.\r\n\r\n[caption id=\"attachment_679\" align=\"alignnone\" width=\"1632\"]
<\/a> Exemplo de resultado do discovery[\/caption]\r\n\r\nO sistema se encarrega de detectar os principais itens e deixa-los marcados por padr\u00e3o. Essas marca\u00e7\u00f5es s\u00e3o sugest\u00f5es do sistema e podem ser alteradas nesta etapa.\r\n\r\nAl\u00e9m de marcar e desmarcar o item a ser monitorado, voc\u00ea tamb\u00e9m pode edit\u00e1-lo, clicando no bot\u00e3o \"Editar\" ao lado de cada servi\u00e7o.\r\n\r\nAp\u00f3s finalizar o Discovery, basta clicar em \"Salvar\" para que os servi\u00e7os comecem a ser monitorados.","_pt_post_name":"como-executar-o-discovery","_pt_post_excerpt":"","_pt_post_title":"Como executar o discovery","_en_post_content":"The Discovery feature is responsible for scanning networks and detecting devices. In Multisite Monitoring you can create as many discoveries as you like and even schedule them.\r\n\r\nTo scan your network using Discovery, go to Multisite Monitoring > Network Management > Discovery.\r\n\r\n[caption id=\"attachment_670\" align=\"alignnone\" width=\"255\"]<\/a> Menu - Discovery[\/caption]\r\n\r\nThis interface will display a list of all discoveries already added and scheduled. To create a new one, click the add button.\r\n\r\n[caption id=\"attachment_671\" align=\"alignnone\" width=\"522\"]<\/a> Add Discovery[\/caption]\r\n\r\n[caption id=\"attachment_672\" align=\"alignnone\" width=\"1000\"]<\/a> Discovery configuration[\/caption]\r\n\r\nSome requirements are needed to run the Discovery, as follows:\r\n- \r\n \t
- Discovery name:<\/strong> The default is filled out with the date and time of register, but you can change the name.<\/li>\r\n \t
- Site:<\/strong> Here you can choose whether the scan will be done locally or on a remote network via the Unit Site.<\/li>\r\n \t
- Address or IP range:<\/strong> In this field you must inform the networks or IP addresses with which the Discovery will detect the devices. Use a semicolon \";\" for more than one IP address or \"ENTER\" as a separator. For an IP range, use one of the following formats: 192.168.1.1-24 or 192.168.1.1\/24<\/li>\r\n \t
- Credentials:<\/strong> They are required for the Discovery to detect items within the device that was found. For example, if the Discovery detects a device with SNMP, it uses the chosen SNMP credential to detect the items that can be monitored within that device.<\/li>\r\n \t
- Schedule discovery:<\/strong> This feature allows you to schedule a specific date and time for the execution, because the scan, depending on the amount of items, can affect the performance of your network. Besides scheduling, you can add a recurrence to run a specific discovery repeatedly and check whether new items or devices have been found.<\/li>\r\n \t
- Enable detection of TCP ports:<\/strong> This option allows the Discovery to scan open TCP ports for each detected device.<\/li>\r\n \t
- Enable detection of Windows counters (Performance Monitor):<\/strong> When the Discovery detects devices with Windows operating system using Agent credentials, it will list all Windows performance counters avaliable for those devices. This option may cause the Discovery to be slower, but it will bring much more details from Windows devices.<\/li>\r\n<\/ul>\r\nAfter filling out these fields, you can execute the Discovery by pressing the \"Start Discovery\" button, or you can save it via the \"Save\" button if you have the schedule option enabled.\r\n\r\nThe results will be grouped by device (device name and IP address) and by expanding the device, the items groups detected and their counters will be displayed.\r\n\r\n
<\/a>\r\n\r\nThe system will bring the most important items already checked. These markups are suggestions and you can change these items in this step.\r\n\r\nBesides checking and unchecking the item to be monitored, you can also edit it by clicking the \"Edit\" button on the right side of the service.\r\n\r\nAfter finishing these steps, click \"Save\" and the system will start monitoring your devices.","_en_post_name":"how-to-execute-the-discovery","_en_post_excerpt":"","_en_post_title":"How to execute the Discovery","edit_language":"en","footnotes":""},"categories":[1,10,8],"tags":[],"class_list":["post-676","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-monitoring","category-multisite-monitoring","category-unit-platform-on-premises"],"_links":{"self":[{"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/posts\/676","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/comments?post=676"}],"version-history":[{"count":11,"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/posts\/676\/revisions"}],"predecessor-version":[{"id":1057,"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/posts\/676\/revisions\/1057"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/media\/983"}],"wp:attachment":[{"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/media?parent=676"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/categories?post=676"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/docs.unitplatform.io\/en\/wp-json\/wp\/v2\/tags?post=676"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}} - Site:<\/strong> Here you can choose whether the scan will be done locally or on a remote network via the Unit Site.<\/li>\r\n \t
- Site:<\/strong> Essa op\u00e7\u00e3o \u00e9 usada para escolher se a varredura ser\u00e1 realizada localmente ou em alguma rede remota, atrav\u00e9s do Unit Remote Network.<\/li>\r\n \t
- Site:<\/strong> Here you can choose whether the scan will be done locally or on a remote network via the Unit Site.<\/li>\r\n \t
- Site:<\/strong> Here you can choose whether the scan will be done locally or on a remote network via the Unit Site.<\/li>\n