You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2014/03/04 10:36:25 UTC

[jira] [Commented] (TS-2608) API to introspect metric semantics

    [ https://issues.apache.org/jira/browse/TS-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13919182#comment-13919182 ] 

Leif Hedstrom commented on TS-2608:
-----------------------------------

Isn't this really a fundamentally missing piece in librecords?  It feels that we ought to add something to RecordsConfig.cc, which then could get passed along into various APIs etc.

One easy thing could be to update this:

enum RecAccessT
{
  RECA_NULL,
  RECA_NO_ACCESS,
  RECA_READ_ONLY
};


Although the overlay of semantics there could be wonky. But, e.g.

enum RecAccessT
{
  RECA_NULL,
  RECA_NO_ACCESS,
  RECA_READ_ONLY,
  RECA_READ_ONLY_GAUGE,
};

Alternatively, we add another member to struct RecordElement, but that means changing a lot of APIs such that the GAUGE vs not-Gauge info is passed in and out properly.


> API to introspect metric semantics
> ----------------------------------
>
>                 Key: TS-2608
>                 URL: https://issues.apache.org/jira/browse/TS-2608
>             Project: Traffic Server
>          Issue Type: New Feature
>          Components: Management API, Stats
>            Reporter: James Peach
>              Labels: api-addition, api-change
>             Fix For: 5.0.0
>
>
> We ought to have an API that apps can use to query the semantics of a metric.  For example, there's no way to know whether a metric is a counter or an instantaneous value. {{traffic_top}} hard-codes a number of these, and I've taken the same approach for my [epic|https://code.google.com/p/epicnms/] plugin.
> As an extension, it would also be helpful to know the units (e.g., bytes, seconds, count).



--
This message was sent by Atlassian JIRA
(v6.2#6252)