Add routing tree back to the UI

[mxinden]

We should bring back the routing tree introduced by @stuartnelson3 in the old UI in the new UI (See old UI).

This was mentioned by Jack here:

The visual editor/tester of the routing tree is missing...I assume that just hasn't made it back with all the code changes.

[stuartnelson3]

Would be nice to take this as an opportunity to re-implement the routing tree. It seemed fairly helpful in the general case (~90% of the users), but for larger routing trees it was fairly un-usable.

This would also be a great opportunity to experiment with a parser+autocomplete when typing in label matchers, since it's something we want in the prometheus ui re-write.

[fabxc]

I'd say add back the existing one first and then make it nicer in a subsequent effort.

…

On Mon, May 22, 2017 at 2:04 PM stuart nelson ***@***.***> wrote: Would be nice to take this as an opportunity to re-implement the routing tree. It seemed fairly helpful in the general case (~90% of the users), but for larger routing trees it was fairly un-usable. This would also be a great opportunity to experiment with a parser+autocomplete when typing in label matchers, since it's something we want in the prometheus ui re-write. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#813 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEuA8tnm4RKSbFBY44H57VN3hQg5mhgWks5r8Xm2gaJpZM4NiCHQ> .

[samifruit514]

Any updates on this? It would be really nice. Im spending a lot of time pushing alert config and copy/paste. Also it would be nice if the Config could be rendered on load time in the draw tool ( im talking about the {{ config }} rendered value in old code https://github.com/prometheus/alertmanager/blob/release-0.6/ui/app/partials/status.html#L23

[samifruit514]

Hey folks, I was looking at the alertmanager code (ui/app) folder and then read on elm lang. I am willing to try to do a PR. But there is something that I cannot figure out. New UI is on elm and it seems that the way to go would be to re-implement the routing tree in elm language. Just adding it back seems not possible since its using static assets and I don't see how we could just import the routing tree assets (routing tree js, d3.v3.min.js, etc...). elm does not allow <script> anymore... which is very understandable...

Any clue on how we could do this, without re-implementing this?

[roidelapluie]

We will move away from elm to react in the future. Le lun. 29 mai 2023, 15:13, Samuel Archambault ***@***.***> a écrit :

…

Hey folks, I was looking at the alertmanager code (ui/app) folder and then read on elm lang. I am willing to try to do a PR. But there is something that I cannot figure out. New UI is on elm and it seems that the way to go would be to re-implement the routing tree in elm language. Just adding it back seems not possible since its using static assets and I don't see how we could just import the routing tree assets (routing tree js, d3.v3.min.js, etc...). elm does not allow <script> anymore... which is very understandable... Any clue on how we could do this, without re-implementing this? — Reply to this email directly, view it on GitHub <#813 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACHHJR5YEVLLIDRZHVTPO3XISOGPANCNFSM4DMIEHIA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>