In this article we will speak in details about the "Service Level" concept for devices and how it works.
Every device which is discovered for the first time will get the "Service Level" as "Production", the same concept apply for any device added manually or via the API/Bulk import, if the service level not specifically set to any other value, the default is always "Production".
This value is not something we change based on a discovery process result, which means if device failed during the scan the service level will be kept as "Production".
Service level can be defined by the discovery job itself by defining the value there, for example:
VMWare, *nix & Windows jobs
Or SNMP jobs
Using the service level defined on the job settings page, means that all devices discovered through these jobs will get this value automatically, but we need to remember that this value will not be changed to anything else automatically.
The recommended approach to change this values based on the auto discovery jobs behavior, let say if the device has not been updated for a certain amount of times which means it is not exist anymore, we can use the "Auto Clean" rules option to change the default value to any required value for example "Decommissioned"
And we can also apply the "Asset Lifecycle" Event approach to change this value, as soon as we define an asset lifecycle even to any device on the system
We can add or rename the current service levels values under this URL
replacing D42-IP with your instance IP or FQDN, for instance if you rename the "Production" level to any other value this will be the default value for any newly discovered device.