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

Add more metrics metadata to dimensions

    Details

      Description

      We had a discussion about injecting more metadata into exposed dimensions in metrics json endpoints again with Luis Davim, we have been thinking about injecting extra dimensions after collecting and before injecting into a time series db is the right approach. We’d prefer dcos-metrics to provide more dimensions right away.

      Some dimensions could be seen like redundant since we already have related id values. e.g. we already have task-id/framework-id there, we rather need framework-name/task-name, what do you think about adding ability to add more stuff into dimensions, with optional flags that could allow us to selectively enable if the overhead could impact other users.

      The problem with havin only *-id values available is that we have no easy/cheap way to query the related metadata from Mesos/Marathon.

      Also, we have Marathon labels exposed under dimensions for containers started by marathon, I expect adding marathon app-id there won't create a big impact?

        Attachments

          Activity

            People

            • Assignee:
              klueska Kevin Klues (Inactive)
              Reporter:
              bergerx Bekir Dogan
              Team:
              DELETE Observability Team
              Watchers:
              Bekir Dogan, Philip Norman (Inactive)
            • Watchers:
              2 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.