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

ocprometheus doesn't work on Arista running 4.21.5F #41

Open
aned opened this issue Jun 13, 2019 · 8 comments
Open

ocprometheus doesn't work on Arista running 4.21.5F #41

aned opened this issue Jun 13, 2019 · 8 comments

Comments

@aned
Copy link

aned commented Jun 13, 2019

I'm getting this directly from gnmi cli:

./gnmi -addr 10.10.1.1:6042 -username admin -password blah get "/Sysdb/connectivityMonitor/status"

/Sysdb/connectivityMonitor/status/hostStatus/device-1/defaultStats/latency:
0.07800000160932541
/Sysdb/connectivityMonitor/status/hostStatus/device-1/defaultStats/jitter:
0.012000000104308128
/Sysdb/connectivityMonitor/status/hostStatus/device-1/defaultStats/packetLoss:
0

In ocprometheus I have this configured:

subscriptions:
        - /Sysdb/connectivityMonitor/status

metrics:
        - name: PacketLossArista
          path: /Sysdb/connectivityMonitor/status/hostStatus/(?P<dst_target>.+)/defaultStats/packetLoss
          help: Packet loss on Arista

        - name: LatencyArista
          path: /Sysdb/connectivityMonitor/status/hostStatus/(?P<dst_target>.+)/defaultStats/latency
          help: Latency on Arista

        - name: JitterArista
          path: /Sysdb/connectivityMonitor/status/hostStatus/(?P<dst_target>.+)/defaultStats/jitter
          help: Jitter on Arista

It worked fine on previous EOS version.

@aaronbee
Copy link
Member

The issue is likely due to a change in TerminAttr in EOS-4.21.5F that removes use of deprecated fields of the gNMI protobufs. ocprometheus was updated to support both the deprecated and newer fields here: 22b2444

@aned
Copy link
Author

aned commented Jun 13, 2019

Running the latest master, the same issue (no metrics being exported).

@aned
Copy link
Author

aned commented Jul 16, 2019

Ping?
Or the entire thing is no longer supported?

@aaronbee
Copy link
Member

@aned I suggest you get in contact with Arista Support.

@aned
Copy link
Author

aned commented Jul 16, 2019

Cut arista case# 158111 @aaronbee

@aned
Copy link
Author

aned commented Jul 17, 2019

@aaronbee Arista TAC provided an extension ocprometheus-1.6.swix. Installed it on arista switch, /usr/bin/ocprometheus worked as expected, got my metrics. Copied over the binary to my server and it's working as well.
So it's definitely some issue with the current code on github.

@aaronbee
Copy link
Member

Thanks for the update. What version of TerminAttr you are running on the device? You can tell with the Cli command:

bash /usr/bin/TerminAttr -version

(This is assuming you are running TerminAttr from its default location. If not, replace /usr/bin/TerminAttr with the path used under daemon TerminAttr.)

@aned
Copy link
Author

aned commented Jul 17, 2019

Running TerminAttr from the default location:

v1.5.2 go1.10.3

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

No branches or pull requests

2 participants