Nice tutorial mate. The only thing I would change on it is the notification method. I would create a notification rule upon update to the cmdb_ci_server table if field changed to retired. Using notification rule we have the advantage of leverage email templates as well standardising the email body as per organisation's policies.
If the device has not actually been decommissioned ("Retired") but may be off for some reason, and ServiceNow marks the device as "Stale", and that device comes back online and ServiceNow marks the "Install Status" as "Installed" again, you now have what is called a Zombie CI. Do NOT automate the lifecycle in your tool. Just because you CAN do it it does NOT mean that you SHOULD do it.
Thanks for the suggestion. This was done when we didn’t had discovery and second we had some issues for cloud discovery which created CIs which were never retired. But again your point is taken.
Nice tutorial mate. The only thing I would change on it is the notification method. I would create a notification rule upon update to the cmdb_ci_server table if field changed to retired.
Using notification rule we have the advantage of leverage email templates as well standardising the email body as per organisation's policies.
Thanks and nice idea.
Thank you !
Thanks
If the device has not actually been decommissioned ("Retired") but may be off for some reason, and ServiceNow marks the device as "Stale", and that device comes back online and ServiceNow marks the "Install Status" as "Installed" again, you now have what is called a Zombie CI. Do NOT automate the lifecycle in your tool. Just because you CAN do it it does NOT mean that you SHOULD do it.
Thanks for the suggestion. This was done when we didn’t had discovery and second we had some issues for cloud discovery which created CIs which were never retired. But again your point is taken.
Too blurry.