[MESOS-6066] Operator SUBSCRIBE api should include timestamps

• Type: Bug
• Status: Accepted
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.0.0
• Component/s: HTTP API, json api
• Epic Link: Operator API v1 Improvements
• Assignee: Unassigned
• Reporter: Steven Schlansker
• Created: 22/Aug/16 21:51
• Updated: 22/Aug/16 22:22

Description

Events coming from the Mesos master are delivered asynchronously. While usually they are processed in a timely fashion, it really scares me that updates do not have a timestamp:

301
{
  "task_updated": {
    "agent_id": {
      "value": "fdbb3ff5-47c2-4b49-a521-b52b9acf74dd-S14"
    },
    "framework_id": {
      "value": "Singularity"
    },
    "state": "TASK_KILLED",
    "task_id": {
      "value": "pp-demoservice-steven.2016.07.05T17.00.06-1471901722511-1-mesos_slave17_qa_uswest2.qasql.opentable.com-us_west_2b"
    }
  },
  "type": "TASK_UPDATED"
}

Events should have a timestamp that indicates the time that they happened at, otherwise your timestamps include delivery and processing delays.

Issue Links

• Is contained by: MESOS-5936 Operator SUBSCRIBE api should provdide more task metadata than just state changes