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

Seldon dashboard with hundreds of REST requests #29

Open
beeva-enriqueotero opened this issue Nov 7, 2016 · 5 comments
Open

Seldon dashboard with hundreds of REST requests #29

beeva-enriqueotero opened this issue Nov 7, 2016 · 5 comments

Comments

@beeva-enriqueotero
Copy link

Seldon grafana dashboard shows every API request for a client. With Recommendation REST API each user generates a different entry in charts. So after hundreds of users the chart legend is huge and the web interface hangs up.

Regards, and thank you
Enrique

@ukclivecox
Copy link
Contributor

Hi,

The dashboard for recommendations should aggregate by request type as shown in http://docs.seldon.io/img/grafana.png
Do you have the version of Seldon you are running and perhaps some example or screenshot to help us debug this further?

@beeva-enriqueotero
Copy link
Author

beeva-enriqueotero commented Nov 8, 2016

Hi,

The dashboard for recommendations aggregates by request type based on url. The problem with REST
API is that /users/1/recommendations and /users/10/recommendations, for instance, generate different request types.

I tested this behaviour with Seldon Server 1.3.11

@ukclivecox
Copy link
Contributor

Yes, this will need a fix to the kafka-streams job that aggregates the stats and sends them to influxdb.
We will need to add to it knowledge of the REST endpoint URL structures so the user can be removed from the request.
An alternative would be to change the influxdb (via grafana) SELECT statements if possible, but I'm not sure of the flexibility of the influxdb query langauge to accomplish this.

@beeva-enriqueotero
Copy link
Author

I don't know much about influxdb. But I don't find in its documentation any string function. So it doesn't seem easy to be done only by changing SELECT queries.

@seldondev
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale

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

3 participants