[
https://issues.apache.org/jira/browse/MESOS-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259440#comment-15259440
]
Jay Guo commented on MESOS-5269:
--------------------------------
Agreed. However, WebUI currently relies on JSON attributes returned by endpoint
/metrics/snapshot, e.g. {{slave/uptime_secs}}. We have two options to duplicate
returned attributes:
1. Duplicate the metric itself. Although this results in possible inconsistency
of {{slave/XXX: valueX}} and {{agent/YYY: valueY}}, since metric->value() is
called twice.
2. Duplicate the field in JSON before return. This simply manipulates JSON
string before returning it. Although it's in libprocess and having this kinda
operation there is quite awkward.
Ideas?
> Replace Master/Slave Terminology Phase I - Update Metrics
> ---------------------------------------------------------
>
> Key: MESOS-5269
> URL: https://issues.apache.org/jira/browse/MESOS-5269
> Project: Mesos
> Issue Type: Task
> Reporter: Jay Guo
>
> process::metrics::Gauge slaves_connected;
> process::metrics::Gauge slaves_disconnected;
> process::metrics::Gauge slaves_active;
> process::metrics::Gauge slaves_inactive;
> process::metrics::Counter messages_register_slave;
> process::metrics::Counter messages_reregister_slave;
> process::metrics::Counter messages_unregister_slave;
> process::metrics::Counter messages_update_slave;
> process::metrics::Counter recovery_slave_removals;
> process::metrics::Counter slave_registrations;
> process::metrics::Counter slave_reregistrations;
> process::metrics::Counter slave_removals;
> process::metrics::Counter slave_removals_reason_unhealthy;
> process::metrics::Counter slave_removals_reason_unregistered;
> process::metrics::Counter slave_removals_reason_registered;
> process::metrics::Counter slave_shutdowns_scheduled;
> process::metrics::Counter slave_shutdowns_completed;
> process::metrics::Counter slave_shutdowns_canceled;
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
