> On Dec 20, 2023, at 11:07 AM, Miles Libbey wrote:
>
> Could these tools do something like call traffic_ctl config get
> proxy.config.metric_prefix instead of loading the full records.config?
Good idea. Yeh, they probably could, requires more work than I was willing to
invest at the time. :
Could these tools do something like call traffic_ctl config get
proxy.config.metric_prefix instead of loading the full records.config?
On Mon, Dec 18, 2023 at 9:03 PM Leif Hedstrom wrote:
>
>
> > On Dec 18, 2023, at 21:20, Walt Karas
> wrote:
> >
> > Is the current naming based on some SNMP MI
>To distinguish from “config” ? I mean, it’s obviously a metric or stat at
this point already :).
What I meant by this is, how do we know that `ats` means only `metric`? and
not a config record. Anyway, I am +1 to drop the `proxy.process` . I am
just inclined to have a prefix which can be used to
> I did indeed try this route first, but it was difficult to find a
solution that works with our tools. traffic_top (etc.) doesn’t read
records.yaml, so it won’t know a change to the prefix.
I think it will be doable to have a record_alias.json or something like
that that traffic_ctl/top/etc maps
