You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The main reason why I was looking for an Azure function visualizer was to better understand the sequence in which functions call or invoke each other. While the tool in its current state helps with that, there are still some important drawbacks I would like to address:
Logical ordering: Functions are currently sorted (alphabetically) by their inputs. If a function func1 is triggered by QueueB and writes to QueueA, while func2 is triggered by QueueA and writes to QueueC, func2 is still displayed above func1, even though the logical sequence of execution that could be deduced is the opposite.
Horizontal arrangements: If a logical sequence is to be detected (see above), why not display func2 on the right of func1. I would suggest using shared in- and outputs (in my case, queues) as central nodes, that are shared between functions. It would then look something like this:
The text was updated successfully, but these errors were encountered:
The main reason why I was looking for an Azure function visualizer was to better understand the sequence in which functions call or invoke each other. While the tool in its current state helps with that, there are still some important drawbacks I would like to address:
func1
is triggered byQueueB
and writes toQueueA
, whilefunc2
is triggered byQueueA
and writes toQueueC
,func2
is still displayed abovefunc1
, even though the logical sequence of execution that could be deduced is the opposite.func2
on the right offunc1
. I would suggest using shared in- and outputs (in my case, queues) as central nodes, that are shared between functions. It would then look something like this:The text was updated successfully, but these errors were encountered: