Uploaded image for project: 'DC/OS'
  1. DC/OS
  2. DCOS_OSS-2204

DC/OS Metrics Meta-Data Injection Fix

    Details

      Description

      I am looking for two things regarding DC/OS Metrics injected meta-data, the goal is to have a persistent dashboard for soak cluster data-services(especially for data-service related scheduler stats we publish to monitor our scheduler-services health).

      1. Currently, each metric has associated cluster_id, we need cluster name,  for example, SOAK110 or SOAK111 should be injected in addition to the id like clusterid:ec223acb-5f08-4bf3-956c-51159552a64b, it is very hard to map to the name of the cluster.
      2. For each metrics now we have associated  executor id and its framework id , e.g metrcis = offers.received where executor id=executorid:data-services_confluent-kafka.66dd6cc3-17ef-11e8-9d8c-5251a46f3edd and frameworkid:aaf0a62f-a6eb-4c1d-80db-5fdd26fe8008-0000(which is marathon framework id), in addition to what we should have Task Name(like confluent-kafka-kerberos.data-services)and the if the task is framework itself e.g for data services, all marathon tasks are framework, so we need its service name, otherwise if you reinstall services/or scheduler is crashed, we loose the track.

       

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                philip Philip Norman (Inactive)
                Reporter:
                sukeshroy Sukesh Roy (Inactive)
                Team:
                DELETE Observability Team
                Watchers:
                Ben Wood (Inactive), Chris Lambert, Chris Lambert (Inactive), Gabriel Hartmann (Inactive), Kevin Klues (Inactive), Mahendra Kutare (Inactive), Philip Norman (Inactive), Seth Mason (Inactive), Sukesh Roy (Inactive), Todd Greenstein (Inactive), Viktor Harutyunyan
              • Watchers:
                11 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support

                    NextupJiraPlusStatus

                    Error rendering 'slack.nextup.jira:nextup-jira-plus-status'. Please contact your JIRA administrators.