Enrichments

The Enrichment Manager allows the user to define Enrichment Rules which automatically update the data in UCMDB. Each rule is defined for a specific TQL query, and sets out the actions to be performed over each resulting instance of the TQL query result.

Dos and Don'ts: A poor enrichment design may tax the system resources. The Enrichment Manager allows the user to efficiently deal with discovery issues and modeling errors . Enrichment Manager allows the user to define Enrichment Rules which automatically update the data in UCMDB.

• Define enrichment as active only if you need it to run continuously on UCMDB changes.
• Be careful when changing application and system parameters like internal settings.
• Use a pattern based model to create only one model CI.
• Avoid conflicts : Split enrichment creation into two enrichments to avoid Data-In merge operations.

Logs to troubleshoot enrichments:

• cmdb.enrichment.detailed.log
• cmdb.enrichment.log

Internal and External Fuse Settings - Enrichment

Setting Name	Display Name	Default Value	Refresh Rate	Display in UI	Description
enrichment.business.view.max.allowed.Links.creating	Enrichment Business View Max Allowed Links Creating	15000	Reboot	FALSE	Enrichment business view max allowed links creating
enrichment.business.view.scheduler.cron.expression	The cron expression of the pattern-based-model scheduler	000/12**?	Immediate	FALSE	The cron expression of the pattern-based-model scheduler
enrichment.business.view.scheduler.interval	The frequency of pattern-based-model updated per day	12	Immediate	FALSE	The frequency of pattern-based-model updates per day in hours
enrichment.business.view.scheduler.type	the type of the pattern-based-model scheduler	1	Immediate	FALSE	The type of the pattern-based-model scheduler represented as integer value [1=interval, 5=cron]
enrichment.calculator.manager.async.thread.pool.size	Enrichment Admin Manager Async Thread Pool Size	5	Reboot	FALSE	Async private thread pool size for enrichment admin manager
enrichment.in.memory.calculate.cis.chunk.size	Enrichment In Memory Calculate CIs Chunk Size	20000	Reboot	FALSE	Enrichment In memory calculate CIs chunk size
enrichment.max.allowed.cis.changes	Enrichment Max Allowed CIs Changes	1000000	Reboot	FALSE	Enrichment max allowed CIs changes
enrichment.model.changes.chunk.size	Enrichment Model Changes Chunk Size	20000	Reboot	FALSE	Enrichment model changes chunk size
tql.group.enrichment.active.count	TQL Group Enrichment Active Count	200	Reboot	FALSE	maximum number of patterns from group "enrichment" allowed to be active
tql.group.enrichment.initialized.count	TQL Group Enrichment Initialized Count	200	Reboot	FALSE	Maximum number of patterns from group "enrichment" allowed to be initialized
tql.group.enrichment.result.size	TQL Group Enrichment Result Size	1000000	Reboot	TRUE	TQL group enrichment result size

Enrichments Tips

Need for an Enrichment: There must be a valid reason for enriching a CI. Always ask the stakeholder WHY? Always differentiate the enrichment requirements between a good to have enrichment versus must have ones.

Design it in style: Be very specific! For example, you are trying to enrich your AIX servers CI with an attribute update, which is creating a query select the lowest CI in the CI type manager.

Review active enrichments every quarter: It is always a good practice to review the active enrichments every quarter. Deactivate/delete the enrichments that you do not need anymore.

Organize: Always organize your enrichment rules in proper buckets. This helps to avoid confusion.

CI Creations: If an enrichment rule is designed to create new CIs, always look at the total number of CIs and relationships it is going to create.

Plan Enrichment Schedule: Once the enrichment is created, you have full control of scheduling. We have seen customers keep the OOTB scheduler and forget to personalize it. If an enrichment rule is not critical, try to schedule it weekly or monthly. Do not run all the enrichment rules at the same time. This will tax the system resources.