bluewave-labs
Feature Request: Change monitoring type and url
Is your feature request related to a problem? Please describe. Currently it is not possible to change the monitoring type and URL after a monitor is created.
Describe the solution you'd like The Configure menu is already there, it would be nice if it is possible to set a different URL, change the monitoring type and change from HTTPS to HTTP for example.
Describe alternatives you've considered Now the monitor has to be deleted and recreated, causing you to lose the history.
Additional context An internally used url could switch from HTTP to HTTPS. Right now you would need to create a new monitor even though you are monitoring the same service and would like to keep the history.
Hi @gorkem-bwl and @karenvicent,
I noticed this feature is assigned to @karenvicent, but I’m interested in contributing as well. If, for any reason, this issue becomes available or you need extra help, I’d be happy to work on it or assist with the implementation.
Please let me know if there’s an opportunity to help out.
Hi @gorkem-bwl and @karenvicent,
I noticed this feature is assigned to @karenvicent, but I’m interested in contributing as well. If, for any reason, this issue becomes available or you need extra help, I’d be happy to work on it or assist with the implementation.
Please let me know if there’s an opportunity to help out.
This is a small implementation so if @karenvicent hasn't started yet, you can go ahead and implement.
@Yasir-Rafique let me know if you still would like to work on this and I'll assign :)
I will start working on this soon and update you accordingly. Thanks!
I will start working on this soon and update you accordingly. Thanks!
Thanks. We are going to make a release soon - just fyi.
@Yasir-Rafique we want to make a release soon so let me know how it goes! :)
@gorkem-bwl I have just completed the requested feature for #2594 — enabling monitor URL and protocol (HTTP/HTTPS) updates directly from the UI, so users no longer have to delete/recreate monitors to keep their history.
Let me know if there’s anything you’d like me to revise, or if you spot any edge cases we should test further. Thanks for the feedback so far!
@gorkem-bwl I have just completed the requested feature for #2594 — enabling monitor URL and protocol (HTTP/HTTPS) updates directly from the UI, so users no longer have to delete/recreate monitors to keep their history.
Let me know if there’s anything you’d like me to revise, or if you spot any edge cases we should test further. Thanks for the feedback so far!
@Yasir-Rafique I cannot see a demo or video attached to the PR. Are all the checklists double checked ?
@FirefoxNL @Yasir-Rafique @gorkem-bwl
Allowing the protocol to be changed makes sense, but does it make sense to allow the changing of the target URL?
If you point the monitor for one day at www.google.com and then point it at www.yahoo.com for another day, it will appear that you have two days of monitoring for www.yahoo.com when in fact the first day of monitoring is for www.google.com. This change is up to the user of course, but I do find it misleading.
@gorkem-bwl I am really sorry. I was in a hurry and totally forgot to upload the video. I just did that. Please see the updated PR. Apologize!
@FirefoxNL @Yasir-Rafique @gorkem-bwl
Allowing the protocol to be changed makes sense, but does it make sense to allow the changing of the target URL?
If you point the monitor for one day at
www.google.comand then point it atwww.yahoo.comfor another day, it will appear that you have two days of monitoring forwww.yahoo.comwhen in fact the first day of monitoring is forwww.google.com. This change is up to the user of course, but I do find it misleading.
Yep - I am good with that. We can change the URL and protocol at the same time and user will know that the graph will show incoming data from 2 different URLs.
@FirefoxNL @Yasir-Rafique @gorkem-bwl
Allowing the protocol to be changed makes sense, but does it make sense to allow the changing of the target URL?
If you point the monitor for one day at
www.google.comand then point it atwww.yahoo.comfor another day, it will appear that you have two days of monitoring forwww.yahoo.comwhen in fact the first day of monitoring is forwww.google.com. This change is up to the user of course, but I do find it misleading.
Changing the monitoring URL does not have to be so drastic as changing from google to yahoo. Changing the URL is especially useful when a monitored API endpoint changes (domain.com/api/v1 to v2 for example) or you made a typo when creating the monitor. :)