DAZN have been reviewing the following three Prometheus drivers,
- Generic_Prometheus_Collector_1_0_0_4 [DMS-DRV-6657]
- Generic_Prometheus_Docker_Container_1_0_0_2 [DMS-DRV-6765]
- Generic_Prometheus_Base_Component_1_0_0_3 [DMS-DRV-6662]
Testing has highlighted some questions in regard to the way that these drivers interact. After reviewing the the help documents that are available with the drivers, we are hoping to clarify how metrics collected via the ‘Generic_Prometheus_Collector’ driver are transferred over to either or both of the ‘Generic_Prometheus_Base_Component’ and ‘Generic_Prometheus_Docker_Container’? (At the moment we have data showing on the Generic_Prometheus_Collector driver, however nothing is appearing via either of Dataminers ‘Generic_Prometheus_Base_Component’ or ‘Generic_Prometheus_Docker_Container’ interfaces. We are also unclear where to import or deploy deploy configurations within the ‘Prometheus Base component’ driver)
Hi,
-The Generic Prometheus Collector is responsible to retrieve the data. In that element it is configured what data to be queried and where to pass the result to.
-The Generic Prometheus Docker Container and Generic Prometheus Base Component are used to create elements that will contain the parameters where the queried data will be stored. These drivers should be considered as a starting point: they contain the needed communication logic to be done with the Collector driver, but these do not contain any parameters yet to store the data. It is the intention that these Docker Container, or Base Component, drivers are always modified and parameters are added.
In the Collector driver, Query Table, there will be a row for every query to be executed, that query can then be linked to a destination element (from a modified Base Component driver) and the (newly added) parameter name in that Base Component driver where that result of the query should be stored.
For more info about the Collector driver, see this help in the catalog.
For more info about the Base Component driver, see this help in the catalog. Look for the Notes section that explains on how to add the Single Numeric, Single String, and Table Column parameters.
To summarize: In the collector there is defined what queries to be executed and in what element/parameter the result should be stored. As the query can be anything and dynamically creating a parameter at runtime is not possible yet, this parameter that should store the result of the query should be manually added to the base component driver.