The topic is related to the data collection from different sources like OA, Sitescope (SiS), Azure,... and how the collected data is stored in the OBR.
Since the very beginning we have the problem that it is not so easy and very time consuming to map the column names in OBR with the data collected from agents.
We faced this problem when we started to use OBR and now with Sitescope and Azure we face it again. In order to create such a mapping list, we as the customer have to do a reengineering of the Content Packs.
Based on the XML files we as customer need to figure out which column matches the collected metric.
Even for Sitescope and Azure we detected the staging XMLs are very complex and one column can have data from different metrics. And honestly reporting operation people do not always know what all the metrics mean in detail.
This task for us is time consuming and since the SW vendor can also change the mapping we need to verify it for every product release.
Further on, our customers like to know in detail what kind of data we collect, the expect a detailed description of the collecte metrics and in case something is missing a good reason why it is missing.
Therefor we request:
1. for all Content Packs a detailed documenation that shows the mapping from the source to the table column
2. the document should provide a detailed documentation and should go beyond of the current explenations like provided for the OA Metrics
For us the ability to explain the collected data is business critical.
If it is not available we are facing the risk (especially in the cloud business) to loose customers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.