Integration Hub ETL
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi
I have a question about Integration Hub ETL
When should the Integration Hub ETL be used?
How does it differ from defining and performing ETL transformations yourself?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
IntegrationHub ETL should be used when you want to make sure your CI integrations actually honor IRE and when you want to do as much as possible "low code". ETL is sort of rigid so any heavy custom logic might be very hard to implement with it. For example we had a requirement to make initial check for inserts to compare two different field values to make sure if the record exists already and that wasn't possible with ETL due to IRE.
If you have simplistic CI data and can use for example the serial number as is for correlation, then ETL should work fine for you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hi @HS7 ,
IntegrationHub ETL should be used when you want a low-code, IRE-compliant way to bring CI data into CMDB and perform standard transformations without heavy scripting. It ensures data integrity by automatically using the Identification and Reconciliation Engine.
It differs from manual ETL because custom scripts give full flexibility, while ETL is more rigid and best suited for clean, structured data and standard CI updates. If the integration requires complex logic or custom correlation, manual scripting is usually the better approach. Additionally, IntegrationHub ETL offers easier long-term maintenance with visual transformations and better governance.
If I cleared your doubt mark this response as helpful and accept the solution.
Regards,
Tausif Ahmed
