Closed jdamick closed 12 years ago
For the standard format I think the following information needs to be required:
1) Transaction ID - UUID that is used to track the request/transaction across multiple processes/resources/events. 2) Business - Ultra, NPAC, Webmetrics, etc.. 3) Product - neustar.biz, Ultra user portal, etc.. 4) Host - The host the resource resides on. 5) Resource - Process name 6) Requestor - Information about what created the request (e.g. IP address, user name, vendor queue, etc..). 7) Result - Successful or not. (code based? text based?) 8) Response Time (us) - Time it took to complete the request. 9) Remainder of message should be arbitrary key=value pairs containing information pertinent to the reporting application/process.
Items 2 and 3 should be combined into a UUID generated during a provisioning step both to slim the message and make sure it is consistent. Similarly the same can be applied to 4 and 5.
ok, thanks - i put the fields from the querying point of view since if those are the ones that you need to query on or see in the result set it will drive what the interface looks for what the services to need to provide..
i may move this over there ..
As a service team I need the ability to provide metrics to a central service in a standard format so that I can see reports or perform lookups on that data at a later time.
Acceptance Criteria:
Tasks (examples off the top of my head):