suggestions for atlas service
Hi Here are my few suggestions for Atlas service Suggestion1: It would be nice to have groups of Atlas probes which make measurement against them? A requirment may be to have public ip addresses assigned to the probes and you may suggest all the necessary firewall openings to make them reachable. If possible, it would also be nice to have an area in your portal to see only those probes. Suggestion2: It would be nice to have the possibility to set alarms or threshold associated to given probes, so to have the Atlas portal send warning email. Sugestion3: Send weekly or monthly reports by email about the stats collected by selected probes. cheers Edoardo
Hello, and one from me (speaking as a probe host and internet citizen): Have a "friend" button or list where I can give other individuals access to the measurements of my probe. best regards, Wolfgang -- Wolfgang Tremmel, WT5-RIPE
Hello, On 2011.05.05. 11:31, Wolfgang Tremmel wrote:
Hello,
and one from me (speaking as a probe host and internet citizen):
Have a "friend" button or list where I can give other individuals access to the measurements of my probe.
best regards, Wolfgang
Indeed, this (or something similar) has been asked by others too. Currently we only have a private/public probe distinction. On the longer run we cold just have the "friend" feature you mention, but we may go further and add ACLs for certain features like watching or configuring a probe. I think that adding a single "friend" to have the same control as the host is something we can add relatively quickly, especially if it solves most of the immediate needs. Regards, Robert
Hi, On 2011.05.05. 10:34, Edoardo Martelli wrote:
Hi
Here are my few suggestions for Atlas service
Suggestion1: It would be nice to have groups of Atlas probes which make measurement against them? A requirment may be to have public ip addresses assigned to the probes and you may suggest all the necessary firewall openings to make them reachable. If possible, it would also be nice to have an area in your portal to see only those probes.
It's possible to do this, however, hearing folks speaking at the mike at the measurements BoF, it may not be the most efficient solution. You probably want stable, high-bandwidth destinations instead (TTM boxes can be such).
Suggestion2: It would be nice to have the possibility to set alarms or threshold associated to given probes, so to have the Atlas portal send warning email.
Yes, this indeed sounds attractive. We already have plans for other types of notifications (like probes being down for some reason). The devil is in the details though: what are the thresholds for such a service, how easy and flexible is it to configure, how to filter out the noise so that you don't get spammed about every change, etc. But we'll surely investigate!
Sugestion3: Send weekly or monthly reports by email about the stats collected by selected probes.
Can yo explain what you'd like to see in such a report, what would be useful to see? Regards, Robert
cheers Edoardo
Hi all, some features I would like to see / have. 1. customized output I don't need all frames / boxes the system is reporting back after a query. So having the option to limit them and / or sort them in a different order would be helpful to me. 2. RIS dashboard function I like the RIS dashboard function a lot, and would like to see more of this stuff in stats, too. http://www.ris.ripe.net/mt/asdashboard.html?as=3333 Especially the transit provider list, would be cool. 3. An aggregated Looking-glass function from different locations. Apparently this was implemented since the last RIPE meeting and was therefore online before I have even written this email. Very cool, thanks for that:-) cheers, ck
Hi Christian, Many thanks for your input. I changed the subject line because I think you meant ripestat, not ripe atlas :) If anyone else has opinions on the below, we'd love to hear from you! Regards Mark Christian Kaufmann wrote:
Hi all,
some features I would like to see / have.
1. customized output I don't need all frames / boxes the system is reporting back after a query. So having the option to limit them and / or sort them in a different order would be helpful to me.
2. RIS dashboard function I like the RIS dashboard function a lot, and would like to see more of this stuff in stats, too. http://www.ris.ripe.net/mt/asdashboard.html?as=3333 Especially the transit provider list, would be cool.
3. An aggregated Looking-glass function from different locations. Apparently this was implemented since the last RIPE meeting and was therefore online before I have even written this email.
Very cool, thanks for that:-)
-- Mark Dranse RIPE NCC
Hi Christian,
Many thanks for your input. I changed the subject line because I think you meant ripestat, not ripe atlas :)
Hi Mark, On 19.05.2011, at 19:12, Mark Dranse <markd@ripe.net> wrote: this is corect:-) Thanks, ck
If anyone else has opinions on the below, we'd love to hear from you!
Regards
Mark
Christian Kaufmann wrote:
Hi all,
some features I would like to see / have.
1. customized output I don't need all frames / boxes the system is reporting back after a query. So having the option to limit them and / or sort them in a different order would be helpful to me.
2. RIS dashboard function I like the RIS dashboard function a lot, and would like to see more of this stuff in stats, too. http://www.ris.ripe.net/mt/asdashboard.html?as=3333 Especially the transit provider list, would be cool.
3. An aggregated Looking-glass function from different locations. Apparently this was implemented since the last RIPE meeting and was therefore online before I have even written this email.
Very cool, thanks for that:-)
-- Mark Dranse RIPE NCC
participants (5)
-
Christian Kaufmann -
Edoardo Martelli -
Mark Dranse -
Robert Kisteleki -
Wolfgang Tremmel