[
https://issues.apache.org/jira/browse/AURORA-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538809#comment-14538809
]
Joe Smith commented on AURORA-1282:
-----------------------------------
Yeah, but changes to stats are fine- I think what I'm going after is avoiding
the huge burst of log messages at scheduler-startup. I actually agree that the
slashes improve readability, so would actually like to keep it.
[~StephanErb] great point- [I agree with you that it should be called
regardless|https://github.com/twitter/commons/blob/afbca0b5ded2d6cf2d918bd0d7c85e43dc9919cf/src/java/com/twitter/common/stats/Stats.java#L69],
it's just that in practice, I'm checking {{/vars}} on my scheduler and seeing
slashes instead of underscores, but cannot confirm where that might not be
followed through.
> twitter.common.stats.Stats warns about exported metric names
> ------------------------------------------------------------
>
> Key: AURORA-1282
> URL: https://issues.apache.org/jira/browse/AURORA-1282
> Project: Aurora
> Issue Type: Bug
> Reporter: Stephan Erb
> Assignee: Joe Smith
> Priority: Minor
>
> The Aurora log file gets spammed with lots of warnings for each service/job:
> {code}
> W0417 11:10:06.046 THREAD159 com.twitter.common.stats.Stats.validateName:
> Invalid stat name sla_testcluster/test/myservice_mttr_nonprod_ms exported as
> sla_testcluster_test_myservice_mttr_nonprod_ms
> {code}
> Any proposals how we might get rid of them or silence them?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
