You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/12/09 23:14:12 UTC
[jira] [Commented] (TS-3231) add metrics to represent configuration
freshness
[ https://issues.apache.org/jira/browse/TS-3231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14240153#comment-14240153 ]
ASF subversion and git services commented on TS-3231:
-----------------------------------------------------
Commit f8be3681a0831d842b934628f2a9b31416ddb873 in trafficserver's branch refs/heads/master from [~jpeach@apache.org]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=f8be368 ]
TS-3231: track when process restarts are required
Start checking the record update type when we process reconfiguration
events so that we can publish metrics to tell the operator when a
restart is required. Note that is is only as accurate as the
RecordsConfig definitions, so YYMV.
Add the following new metrics:
proxy.node.config.restart_required.proxy
proxy.node.config.restart_required.manager
proxy.node.config.restart_required.cop
> add metrics to represent configuration freshness
> ------------------------------------------------
>
> Key: TS-3231
> URL: https://issues.apache.org/jira/browse/TS-3231
> Project: Traffic Server
> Issue Type: Improvement
> Components: Configuration, Metrics
> Reporter: James Peach
>
> It's not always obvious when the configuration needs to be reloaded or when services need to be restarted. Add some metrics to track this so that that operators can act accordingly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)