Prevent ITOM Cloud discovery to discover Retired machines

Nisha30 · ‎05-14-2026

Hi Experts,

There are many threads and explanation documentation , but opening a fresh one to understand as what would be the best way to stop discovering Non-operational / Retired servers from cloud.

We have discovery in place but

This consumes license and hence need to restrict .

Is scripting needed here to avoid insert of new CI (retired) or in CI CLASS MANAGER the identification rule resolved this problem.

New to RTE so if anyone can suggest

Thanks

thomasbueck · 2 weeks ago

@Nisha30 IRE Data Source rule for vmis and for source 'SG Azure' and checkbox 'Insert not allowed' => no vmis will be created via 'SG Azure' => from my understanding not what you want

Before BR on insert with condition
'Discovery Source is 'SG Azure'
In the script write an if statement like:
if(install_status!=1) current.setAbortAction(true);

This should fit your needs

Kind Regards

Thomas

View solution in original post

MushtaqMir · 3 weeks ago

Hi,

Happy to share my inputs. Yes, we can prevent insertion of any retired cloud resource into CMDB. If it is cloud discovery, then need to create a filter in the extension section where we can define criteria for CIs that need to be excluded.

If you are using Graph Connector, this can be achieved by using a transform map script. However, please note that this may lead to upgrade issues as it is treated as a customization of the Graph Connector.

thomasbueck · 2 weeks ago

@Nisha30 Just tick "Insert not allowed" and you will not get any VMware virtual instances from SG Azure anymore.
It's brute force, but it should fit your use case

Nisha30 · 2 weeks ago

HI @thomasbueck

Sorry did not get .

DO i need to create BOTH as shown in both images + Insert Not Allowed -CHEKED

As we do need to get Data BUT only Operational Ones

Thanks

thomasbueck · 2 weeks ago

@Nisha30 as MushtaqMir stated you can modify the transform map, which is the elegant way, but it has the downside that you own the map afterwards - I wouldn't do it.
My first try would be a before insert BR rule. There you check the state and if it's not operational you will not create the vmi - this would be my way to proceed.

Nisha30 · 2 weeks ago

Hi @thomasbueck But if I do setup both

IRE Data Source Rule

and

Reconciliation Rule

Will that insert only operational ones ???? Then no need to create BR. Sorry I am not clear just want to avoid update to OOB unless mandatory for this to achieve.

Thanks