I do not disagree with you in principle. However, with TPTAPI, we are just providing the operators to an application so that they have direct control over them. In the original design, with the original partners and ETL vendors, it was stressed upon us that our operators cannot write to disk.
Therefore, we provide the operational metadata to them (through event calls; their app can call the operator and query the information they would like) and it is their responsibility to perform the proper logging/reporting.
I, too, like consistency. But in this case, we are limited by what the ETL vendors will and will not allow us to do.
As to operational metadata in general, we are working on an enhancement to TPT that will load all operational metadata to Teradata tables (similar in theory to DBQL).
This will be supported in script-based TPT and not in TPTAPI (for different technical reasons than those stated above).
↧