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

Allow customers to see each other's graphs #336

Closed
htrosvik opened this issue Sep 14, 2017 · 14 comments
Closed

Allow customers to see each other's graphs #336

htrosvik opened this issue Sep 14, 2017 · 14 comments
Labels

Comments

@htrosvik
Copy link

Would be very useful if there was a way to allow customers to see each other's traffic graphs.

@barryo barryo added the Feature label Feb 1, 2018
@kylespencer
Copy link

I also think it would be useful to (optionally) allow customers to see each other's graphs.

In addition, it would be useful to be able to create separate read-only user accounts which can see per-network traffic statistics. My regulator, for example, would like to be able to see that data but I do not want them to have access to any other parts of IXP Manager.

@rfc1036
Copy link

rfc1036 commented Feb 1, 2018

This would be useful, since in Italy it has always been customary to show the port graphs to all other IX members and I would like to continue in the tradition for MINAP.
But this feature would also needs a blacklist, because a few big networks have strong policies against this and ask to opt-out.

@barryo
Copy link
Member

barryo commented Feb 1, 2018

In addition, it would be useful to be able to create separate read-only user accounts which can see
per-network traffic statistics. My regulator, for example, would like to be able to see that data but I
do not want them to have access to any other parts of IXP Manager.

On this - I have three problems:

  1. the actual usefulness of such a feature.
  2. the precedence and premise that a regulator should have/need such access.
  3. the complication of actually implementing.

If the regulator needs this information, it should be to satisfy some legal requirement. E.g. the incumbent must peer. This can be demonstrated with the peering matrix or even just a PDF print of the members graphs.

In any case, due to (3), this won't make the development list I'm afraid.

@steiostb
Copy link

On this - I have three problems:

the actual usefulness of such a feature.
the precedence and premise that a regulator should have/need such access.
the complication of actually implementing.

If the regulator needs this information, it should be to satisfy some legal requirement. E.g. the incumbent must peer. This can be demonstrated with the peering matrix or even just a PDF print of the members graphs.

In any case, due to (3), this won't make the development list I'm afraid.

Is your comment only for kylespencers request? Do you have any thought of htrosviks request? Is it possible and do you have any time schedule?

@barryo
Copy link
Member

barryo commented Feb 15, 2018

@steiostb - that related purely to @kylespencer's request for: In addition, it would be useful to be able to create separate read-only user accounts.

@yannrobin is currently working on migrating the statistics graphs from ZendFramework to Laravel and if it's feasible to add this as part of that, we'll do it quickly and release before end of March.

@steiostb
Copy link

@barryo - Any info on when this feature will be available?

@steiostb
Copy link

@barryo Do you have any news on this feature? This should have been implemented for some time ago? Our customers are really missing this feature.

@barryo
Copy link
Member

barryo commented May 15, 2018

Hi @steiostb - this will be in v4.8 which - depending on documentation and quality control - should be released by end of May.

90% of the coding work is finished and most of the documentation.

@barryo
Copy link
Member

barryo commented May 15, 2018

Documentation of this feature is ready here:

https://docs.ixpmanager.org/grapher/api/

Feedback and comments welcome.

@kylespencer
Copy link

kylespencer commented May 15, 2018 via email

@rfc1036
Copy link

rfc1036 commented May 15, 2018

I know that some networks are very sensitive about publishing their traffic levels even just to other IX members, so I would be able to use this (and I really want to!) only if it were possible to blacklist some customer's graphs to the "own_graphs_only" level.

@barryo
Copy link
Member

barryo commented May 15, 2018

@rfc1036 - that won't be possible in this implementation. That's a different degree of complication.

@steiostb
Copy link

@barryo - Thank you for your reply! We have an IX-meeting on May 28, and would be very grateful if this was available by then.

@barryo
Copy link
Member

barryo commented Jun 5, 2018

Implemented in v4.8.0 which we plan to push later this week.

@barryo barryo closed this as completed Jun 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants