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

Not able to use ocprometheus with multiple targets #30

Open
aned opened this issue Nov 13, 2018 · 2 comments
Open

Not able to use ocprometheus with multiple targets #30

aned opened this issue Nov 13, 2018 · 2 comments

Comments

@aned
Copy link

aned commented Nov 13, 2018

It doesn't make much sense to run the bellow command for every Arista sw on my network:
./ocprometheus -addr 10.1.1.1:6042 -listenaddr :8080 -username blah -password blah -config sampleconfig.yml
./ocprometheus -addr 10.1.1.2:6042 -listenaddr :8080 -username blah -password blah -config sampleconfig.yml
...

-addr needs to support a list of targets in order to make this exporter worthwhile.

@wladh
Copy link

wladh commented Feb 22, 2019

Thanks for the report. It seems we lost this ability when we moved to gNMI client. We should rectify it.

@aned
Copy link
Author

aned commented Apr 6, 2019

It should be similar to prometheus's snmp_exporter, where we pass a target as a parameter, such as localhost:9116/snmp?module=vendor-specific-module&target=10.110.10.1
This way we'd run one ocprometheus process and scrape multiple arista targets.
It's much harder to do the opposite - run ocprometheus on every arista box or run one ocprometheus process per arista box on a server and than scrape localhost:listenaddr/metrics

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