Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tag keys defined by user #27

Open
psagrera opened this issue Nov 6, 2018 · 3 comments
Open

tag keys defined by user #27

psagrera opened this issue Nov 6, 2018 · 3 comments

Comments

@psagrera
Copy link

psagrera commented Nov 6, 2018

is there any way in which I can define my own tag keys to be inserted into influxdb ?

Example:

I'm gathering data for interfaces sensor (see below config)

    {
        "host": "10.102.187.188",
        "port": 50051,
        "cid": "mac1",
        "paths": [{
            "path": "/junos/system/linecard/interface/",
            "freq": 10000
        }],
        "influx": {
            "server": "172.17.0.2",
            "port": 8086,
            "dbname": "juniper",
            "user": "juniper",
            "password": "juniper",
            "recreate": true,
            "measurement": "/interface_test/"
        },
    
        "log": {
            "file": "test.log"
        }
    }

I'd need "/interfaces/interface/state/parent_ae_name" as tagKey in order to be able of grouping by this field . I know this can be done in jti_openconfig_telemetry plugin just setting the variable str_as_tags = true , that will treat all strings as tags.

Regards

Pablo

@nileshsimaria
Copy link
Owner

JTIMON does not support custom tagging. It is a good feature request, I will add it to the work list.

@psagrera
Copy link
Author

Thank you very much Nilesh.

@door7302
Copy link

door7302 commented May 9, 2019

hello

We use this chain : Telegraf --> influx --> grafana

We use on Telegraf:

Input : jti_openconfig_telemetry
Ouput : influx

Currently Junos doesn't export AE statistic . We only have physical interface stats and for each physical interface on which ae this interface is a member. So we have two distinct paths :

  • /interfaces/interface/state/parent_ae_name = which gives us the ae interface on which is attached the physical interface
  • /interfaces/interface/state/counters/ = which gives us the traffic stats of physical interface

when telegraf exports to influx the collected data we don't have the parent_ae field/tag attached to the entries related to /interfaces/interface/state/counters/ even if we add the knob str_as_tags = true because the parent_ae_name field is not present on /interfaces/interface/state/counters/. So we could not convert it in tag.

Thus, it is difficult/impossible to simply aggregate the counters of several physical interfaces attached to a same AE

Is there an easy way to achieve that ? with jtimon ?

BR
David

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants