Perfomatic:SendingData: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 71: Line 71:
* still have to have the scripts provide a link to the results added to the db
* still have to have the scripts provide a link to the results added to the db
* would be nice to have Talos send a start/end of data notification; right now Talos sends data and hopes that it has been added correctly and does not attempt re-sends or any sort of error handling - if we sent start/end of data notification would could do some smarter data processing and also do re-sends on failure
* would be nice to have Talos send a start/end of data notification; right now Talos sends data and hopes that it has been added correctly and does not attempt re-sends or any sort of error handling - if we sent start/end of data notification would could do some smarter data processing and also do re-sends on failure
== Sample Send Data ==
Two different types of data to be sent:
# A single value to be stored as the 'average' in the test_runs table
# A set of (interval, value) pairs to be stored in the test_run_values table, 'average' to be calculated by collector script
First type will be called 'AVERAGE' second called 'VALUES'.
All data is formatted using comma separated notation.
* for sending interval, value pairs
START
VALUES
machine_id,test id,branch_id,ref_changeset,ref_build_id
interval0,value0,page_id0
interval1,value1,page_id1
...
intervalEND,valueEND,page_idEND
END
* for sending a single value
  START
  AVERAGE
  machine_id,test_id,branch_id,ref_changeset,ref_build_id
  value0
  END
541

edits

Navigation menu