-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
Overview
Aggregator upon deployment is provided with the Timestream details (region, name, etc).
The aggregator then takes in the URL for the load balancer (or service discovery) in order to take in data
The data is then aggregated to the data output format that we agreed upon in miro
Per request
- Latency
- Request
- Response
Per Test Script
- Script runtime
Per Region
- Number of requests
- Number of Errors
- Average Script Runtime
- Test runtime
Per Test
- Test runtime
Implementation
Tasks
- DA.1: send url of data aggregation to load generator #11
- DA.2: Aggregate data into predetermined format #12
- DA.3: Every n seconds send aggregated data to timestream db #13
- DA.4: Discuss if the server will be a subscriber to LB #14
- DA.5: Determine Timestream Schema #28
- DA.6 Increase write re-tries on timestream client of aggregator engine #52
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels