Metrics from v2/queue seems missing

[karthimohan]

Hi I am looking for the below Metrics from v2/queue endpoints. Dont seem to find it. Could you please let me know if this is exposed as a different name or is this not included in the docker image version 0.3.1?

marathon_queue_delay_timeLeftSeconds
marathon_queue_delay_overdue

[karthimohan]

@matt-deboer @dylanmei Could you please update me on my question?

[matt-deboer]

@karthimohan sorry about the delay (wasn't watching this one for some reason);
to clarify, were the 2 metrics you mentioned present in prior versions, and you find them missing from 0.3.1? or were they never present?

[karthimohan]

@matt-deboer Thanks for the response. I dont think it ever present in the prior versions. I see the exporter.go only extracts metrics from v2/apps and these 2 metrics are from /v2/queue

[janisz]

Marathon 1.4 introduced more metrics in /v2/queue endpoint that are helpful to debug problems with deploying applications. Frome 1.4 release notes: https://github.com/mesosphere/marathon/releases/tag/v1.4.0

Insights into the Launch Process - AKA: Why isn't my app starting?
Marathon tries to schedule tasks based on app or pod definition, which incorporates resource matching, role matching, constraint matching etc. There are situations when Marathon cannot fulfill a launch request, since there is no matching offer from Mesos. It was very hard for users to understand why Marathon could not fulfill launch requests. For users that run into such situations, it was very hard to understand the reasons for this. This version of Marathon gives insight into the launch process, analyzes all incoming offers and gives the user statistics so it easy to see, why offers were rejected.
The statics can be fetched via the /v2/queue endpoint. See the REST API Reference.
Marathon shows the offer matching process as a funnel, so it easy to see how many offers were rejected in which step. It gives this information for the whole launch attempt as well as the last offer cycle.