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

Cannot connect to metrics port 6000 for custom models wrapped with s2i. #1988

Closed
jlee3095 opened this issue Jun 22, 2020 · 1 comment
Closed
Labels
bug triage Needs to be triaged and prioritised accordingly

Comments

@jlee3095
Copy link

I am trying to write custom metrics so that I can expose them on prometheus and grafana following this guide (https://docs.seldon.io/projects/seldon-core/en/v0.3.0/examples/tmpl_model_with_metrics.html) to create a model with custom metrics.

I followed the instructions exactly to make a REST model. I wrapped the example(ModelWithMetrics.py) with s2i seldonio/seldon-core-s2i-python3:0.7 and deployed the model on seldon-core to k8s.

However, when looking at the prometheus targets page I get an error:
Get "http://[IP address]:6000/prometheus": dial tcp 10.0.2.85:6000: connect: connection refused

In addition, I tried deploying the exact same already-wrapped model with custom metrics found in the github repo (https://raw.githubusercontent.com/SeldonIO/seldon-core/master/examples/models/custom_metrics/model_rest.yaml) and the 6000 port did not have any connection issues.

Any help would be appreciated.

@jlee3095 jlee3095 added bug triage Needs to be triaged and prioritised accordingly labels Jun 22, 2020
@axsaucedo
Copy link
Contributor

@jlee3095 this functionality was only introduced from v1.1.0+, you would have to re-wrap your container with a python wrapper v1.1.0 for the prometheus metrics endpoint is available from the model wrapper containers. Versions prior to 1.1.0 exposed metrics only through the service orchestrator.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug triage Needs to be triaged and prioritised accordingly
Projects
None yet
Development

No branches or pull requests

2 participants