ITAM Configuration
The module configuration, as defined by Deepser, is accessible from the “System > IT Asset Configuration” section and is visible only to System Administrators to ensure maximum security and control:
In this section, you can configure:
- Device Types: Define and manage the different types of devices tracked in Deepser.
- Device Subtypes: Specify subcategories for more detailed asset classification.
- Scan Jobs: Set up and manage jobs for scanning devices to gather necessary data.
- Monitoring Rules: Establish rules for monitoring scan jobs and other system activities to ensure proper functioning and performance.
- Remote Collector Configuration: Configure settings for remote collectors to efficiently collect and manage data from devices.
These options allow for comprehensive customization and management of the asset management system to meet your organization’s specific needs.
In the configuration section of the Asset Management module, it is possible to manage types and sub-types of Assets added in Deepser.
To access their configuration, go to the System>Asset Configuration>Device Type or System>Asset Configuration>Device Subtype section in Deepser back-end.
Device Type
In the configuration section of the Asset Management module, you can manage the types of assets added in Deepser.
To access their configuration, go to the System>Asset Configuration>Device Type in the Deepser back-end.
From this section, you can configure a new device types in addition to the default ones by clicking the button in the top right corner.
Device Type Configuration
In the device type edit or creation process, the following screen will appear:
For the device type configuration, the following fields are available:
Field | Description |
Name | A text field for entering the name of the device type. |
Code | A text field where you can add a unique code for the device type. |
Description | A text area field where you can add a description. |
Position | A text field that accepts a numerical value, representing the order of this device type in the grid. |
Status | A select field that indicates whether the device type is enabled or disabled, determining if it can be used for the device model. |
Icon | A file uploader field where you can upload an image to be set as the icon for this device type |
Device Subtype
In the configuration section of the Asset Management module, you can manage subtypes of assets added in Deepser.
To access their configuration, go to the System>Asset Configuration>Device Subtype in the Deepser back-end.
From this section, you can configure device subtypes for each existing device type.
Device Subtype Configuration
In device type edit or creation, the following screen will appear:
For the device subtype configuration, the following fields are available:
Field | Description |
Name | Text field with device type’s naming. |
Code | Text field where you can add a unique code for the device type |
Type | Select field with all the Device type. You can link the device subtype with a type. |
Description | Text area field where you can add a description |
Position | Text field which accepts a numerical value, that represents the order of this device type on the grid. |
Status | Select field which indicates if device type is enabled or disabled in order to be used on the device model. |
Icon | File uploader field, where you can upload an image, that will be set as an icon for this device type. |
Job Rules
To configure a Job-Rule go to the System > Asset Configuration > Scan Job > Job Rule section in Deepser back-end.
Through the query-builder ‘Device Filter’ you can define a condition, which is tested on devices; if this condition is satisfied then the device data is automatically set as defined by the query-builder ‘Set Device Values’.
In the case of multiple Job Rules, their execution order is decided on the assigned ‘Priority’ value (descending order).
Note: the rule is executed every time the Remote Collector sends data related to a device.
Scan Jobs
- SNMP: SNMP scanning involves querying SNMP agents running on network devices to gather information about their configuration, status, and performance.
- WMI: WMI scanning involves querying Windows-based systems using WMI to gather detailed information about their hardware, software, and configuration.
- SSH: SSH scanning involves attempting to establish SSH connections with various hosts on a network. This type of scanning is used for unix devices.
- Ping sweep: Ping scanning involves sending ICMP echo requests (ping packets) to a range of IP addresses within a network. By analysing the responses, a scanner can determine which hosts are online and responsive.
SNMP Scan
Form fields have the following meaning:
| Field | Meaning |
| Name | Name of the Job. |
| Port | UDP port used by Remote Collector to communicate with devices. The default is 161. |
| CRON Expression | Cron Expression, it is present in every type of scan, allows you to define the run interval of the job. |
| IP Range | In this field, you can define the range of IP addresses to scan. You can indicate:• One or more IP addresses• One or more ranges of IP addresses• One or more subnets, specified by CIDR notation |
| IP Range Exclusion | In this field, you can define which IP addresses should be excluded from the scan. The compilation rules are the same as in the ‘IP Range’ field. |
| Remote Collector | Through this Select, it is possible to declare which Remote Collector will execute the Job. |
| ICMP Check | Through this select field, you can decide to perform an SNMP scan only for IPs that are reachable by ping. |
| SNMP Version | SNMP protocol version used to perform the network scan, options are:• SNMPv1• SNMPv2c• SNMPv3 |
| Community | For each device, the Remote Collector will attempt authentication using each of them (following the insertion order) until it gets a positive response. The community strings must be saved within the Deepser Password module.Note: In case of the SNMPv3 version, the username that will be used will be the one set in the ‘Username’ field present in the record of the Password form. |
| Authentication Mode | Only for the SNMPv3 version, it is necessary to set the authentication mode. |
| Auth Protocol | Only for the SNMPv3 version, indicate the possible Auth Protocol. |
| Priv Protocol | For the SNMPv3 version only, indicate the possible Priv Protocol. |
| Auth Password | For the SNMPv3 version only, enter the Password if the selected Auth Protocol requires it. The Password must be stored within the Deepser Password module. |
| Priv Password | For the SNMPv3 version only, enter the Password if the selected Priv Protocol requires it. The Password must be stored within the Deepser Password module. |
| Status | State. If ‘Enabled’ the Job will be sent to the Remote Collector to be executed. |
| Job Status | Job execution status. It can assume the values ‘Running’ during execution by the Remote Collector or ‘Stopped’. |
| Job progress | Progress-Bar indicating the percentage of execution of the Job. |
| Run Now | Once the Job has been saved, using the yellow button on the top right ‘Run Now’ you can run it immediately. |
Once the Job has been configured and finally executed, the collected Devices will be visible in the Asset>Device section in Deepser back-end.
WMI Scan – Windows Devices
At this point, the form for configuring a WMI Job will open.
Form fields have the following meaning:
| Field | Meaning |
| Name | Name of the Job. |
| Type | By this field, you can choose if the job you are configuring is a scan (‘Scan’) or the ‘Agent Deploy’. |
| CRON Expression | Cron Expression, it is present in every type of scan, allows you to define the run interval of the job. |
| IP Range | In this field, you can define the range of IP addresses to scan. You can indicate:• One or more IP addresses• One or more ranges of IP addresses• One or more subnets, specified by CIDR notationUno o più indirizzi IP |
| IP Range Exclusion | In this field, you can define which IP addresses should be excluded from the scan. The compilation rules are the same as in the ‘IP Range’ field. |
| Remote Collector | Through this Select, it is possible to declare which Remote Collector will execute the Job. |
| ICMP Check | Through this select field, you can decide to perform a WMI scan only for IPs that are reachable by ping. |
| Password | Specify one or more passwords to access devices.For each device, the Remote Collector will attempt authentication using each of them (following the insertion order) until it obtains a positive response. Passwords must be stored in Deepser Password module. |
| Use LDAP Server | This field indicates if an LDAP integration is needed. |
| LDAP Server | LDAP server. |
| LDAP Server Password | Password for authentication to the LDAP server.The password must be saved within the Deepser Password module. |
| LDAP Filter Type | You can set one of the proposed LDAP filters or specify a custom filter. |
| LDAP Custom Filter | Custom LDAP filter. |
| Status | Status. If ‘Enabled’ the Job will be sent to the Remote Collector to be executed. |
| Job Status | Execution status of the Job. It can assume the values ‘Running’ during the execution by the Remote Collector or ‘Stopped’. |
| Job progress | Progress-Bar that indicates at what percentage of execution the Job is at |
| Run Now | Once the Job has been saved, it is possible to run it immediately using the yellow ‘Run Now’ button on the top right. |
Once the Job has been configured and executed, collected Devices will be displayed in the Asset>Device section in Deepser back-end.
SSH Scan
At this point, the form for configuring an SSH job will open.
Form fields have the following meaning:
Field | Description |
Name | Name of the Job. |
Port | The port used for SSH connection. The default SSH port is 22. |
Cron Expression | Cron Expression, it is present in every type of scan, allows you to define the run interval of the job. |
IP Range | In this field, you can define the range of IP addresses to scan. You can indicate: • One or more IP addresses • One or more ranges of IP addresses • One or more subnets, specified by CIDR notation |
IP Range Exclusion | In this field, you can define which IP addresses should be excluded from the scan. The compilation rules are the same as in the ‘IP Range’ field. |
Remote Collector | Through this Select, it is possible to declare which Remote Collector will execute the Job. |
ICMP Check | ICMP Check to YES is used to test the reachability of a host on an IP network. |
Password | A multiselect password field through which you can specify one or more passwords to access devices. For each provided password, the Remote Collector will attempt authentication in the order they are listed until it receives a positive response. This field is related to the Deepser Password module, so you need to store the passwords you want to use in that module before they can be utilized here. To use the passwords in this field, you must set the “Use Password” field to “Yes” in the Password record. |
Status | If ‘Enabled’ the Job will be sent to the Remote Collector to be executed based on Cron Expression. |
Job Status | Execution status of the Job. It can assume the values ‘Running’ during the execution by the Remote Collector or ‘Stopped’. |
Progress | Progress-Bar that indicates at what percentage of execution the Job is at |
Run Now | Once the Job has been saved, it is possible to run it immediately using the yellow ‘Run Now’ button on the top right. |
Once the job has been configured and executed, the devices discovered during the scan will be visible in the grid under the Asset > Device section in the Deepser back-end.
Ping Sweep
At this point, the form for configuring a Ping-Sweep job will open.
Form fields have the following meaning:
| Field | Meaning |
| Name | Name of the Job. |
| CRON Expression | Cron Expression, it is present in every type of scan, allows you to define the run interval of the job. |
| IP Range | In this field, you can define the range of IP addresses to scan. You can indicate:• One or more IP addresses• One or more ranges of IP addresses• One or more subnets, specified by CIDR notation |
| IP Range Exclusion | In this field, you can define which IP addresses should be excluded from the scan. The compilation rules are the same as in the ‘IP Range’ field. |
| Remote Collector | Through this Select, it is possible to declare which Remote Collector will execute the Job. |
| Create Device | By this Select field, you can decide if you want to create in Deepser the Devices that represent the scanned IP addresses by marking them as ‘In Service’. |
| Change Device Service | By enabling this option it is possible to change the service status of a device.When a previously added device is unreachable, it will be marked as ‘Not in service’. This behavior also applies to the reverse case. |
| Status | State. If ‘Enabled’ the Job will be sent to the Remote Collector to be executed. |
| Job Status | Job execution status. It can assume the values ’Running’ during execution by the Remote Collector or ‘Stopped’. |
| Job progress | Progress-Bar indicating the percentage of execution of the Job. |
| Run Now | Once the Job has been saved, using the yellow button on the top right ‘Run Now’ you can run it immediately. |
Once the Job has been configured and executed, the Devices found during the scan will be visible in the grid in the Asset>Device section in Deepser back-end.
Remote Collector
You can find more details about its complete configuration here.
To check and verify all configured Remote Collectors (RCs), go to System > IT Asset Configuration > Remote Collector. By clicking on an RC record, the following screen will appear:
For Remote Collector editing or creation, the following fields are available:
Field | Description |
Device | Readonly field containing the relation to the device that originated the Remote Collector. |
Name | Field for setting a custom name for the Remote Collector. If the RC was created via agent, the name will be pre-filled based on the name of the device configured as the RC. |
One Time Password | OTP Fieldautomatically created on Remote Collector creation. It can be used for the RC configuration. |
Status | With this field you can Enable, Disable or set the RC in Pending status. On creation, the default status is “Pending”. |
Monitoring
To access the Monitoring section, navigate to System > IT Asset Configuration > Monitoring. In this section, you can:
- Configure Monitoring Rules: Select “Rule” to set up, view, or edit monitoring rules. These rules define the criteria and thresholds for monitoring device metrics and trigger alerts or actions when certain conditions are met.
- View Monitoring Events: Click on “Event” to review execution information and historical data related to monitoring rules. This section provides insights into rule triggers, alert statuses, and any actions taken based on the monitoring criteria.
These functionalities enable effective management of IT infrastructure by ensuring that potential issues are detected and addressed promptly, thereby minimizing downtime and optimizing performance.
Rule
Clicking on the Add Rule button will open the following screen:
For a rule configuration, the following fields are available:
Field | Description |
Name | Text field that identifies the rule. |
Status | Select field which can ‘enable’ or disable the rule. |
Devices | Query Builder field where you can filter the devices for which this rule will be applied to. |
Metrics Type | Select field with the available metrics type of the device. |
Metric | Select field where you can choose the metric on which the rule will be based on. |
Threshold | This field specifies the threshold value for the selected metric. When the metric exceeds this value, the rule triggers an alert or action. |
Threshold Period | Numeric field which sets the time period over which the threshold is evaluated. It ensures that temporary spikes or anomalies do not trigger unnecessary alerts. |
Event Code | A unique code identifying the event executed by this rule. |
Event Impact | Select field describes the potential impact of the event, such as ‘Low,’ ‘Medium,’ ‘High’. |
Model | Select field where you can set a model like operation, activity, which will be created after the rule is triggered. When a model is selected, a new query builder will appear that allows you to set the information for the model record you want to create. |
Event
In the “event” section of the monitoring, you can see all the rules executed based on your configurations. Therefore, this section contains the log of the rule executions.
Clicking on a single log record we can find information about the executed rule and its related information.
This detailed view helps in understanding the context of rule triggers, evaluating the effectiveness of the monitoring rules, and troubleshooting any issues that may have arisen.
