Hi! Our organization has a wish to use CMDB to create an overview over integration/data transfer in our organization. I'm aware of the possibility to use OOB CI relationship types like "Exchanges data with/Exchanges data with", "Exports to/Imports from" or create custom relationships to achieve the same results (i.e "Integrated to/Integrated to" or similar variations). This could give us a pretty good overview for both applications and CIs, by applying this logic from Business Application <-> Business Application on a logical level, and/or Windows Server <-> Windows server on a physical level.
However, in some cases systems have multiple integrations i.e the ERP system can send multiple types of data to one system on different integrations. On a general level this approach lacks a bit or granularity, as in :
Are there multiple integrations
What endpoint/technology is used to send data
What types of data is integrated
Is the integration push or pull
Who owns the integration
Who developed the integration
Typing this out I realize it might be a better approach to create a new CI type to collect the aforementioned data, and use relationships to do "Business Application" <-> Integration CI <-> "Business Application" or something similar, but it does sound like a lot of work.
Does anyone have any recommendations to best practices or solutions to data/integration overview in cmdb? Is this more hassle than value to implement?
