[atlas] [Request] System tags for DNS resolution
- Previous message (by thread): [atlas] [Request] System tags for DNS resolution
- Next message (by thread): [atlas] edst 193.0.0.228 in traceroute results
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Vesna Manojlovic
BECHA at ripe.net
Thu Nov 12 11:58:08 CET 2015
Hi Stephane, all, On 11-nov.-15 17:36, Stephane Bortzmeyer wrote: > [Is there a better way to record enhancement requests for Atlas? Atlas > has no public issue tracker, if I'm correct?] You are correct, to some extent -- there is a manual processing involved in the middle ;-) It's good that you ask for features on the list, where people can comment on your feature request & add their own use cases (just like Vaibhav just did); then I collect them, we discuss them internally & prioritize them, and they end up on the roadmap: https://atlas.ripe.net/docs/roadmap/ (notice the new URL & new formatting - we are in the process of migrating the roadmap from the old URL to the new one...) > [Is the maintainer of the probe automatically notified when there is > such an issue?] There is something similar already on the roadmap: "Provide additional information to the probe owner about the probe: After analysis of measurements, results will be added to a comments page for the specified probe. This helps the hosts to identify issues and fix them." I will add your additional request to this one. Keep them coming :) Regards, Vesna and thanks for tagging it with [Request] -- good practice :)
- Previous message (by thread): [atlas] [Request] System tags for DNS resolution
- Next message (by thread): [atlas] edst 193.0.0.228 in traceroute results
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]