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
When using service_graph, we usually find that the entry nodes are all virtual_node type (of course, this is expected), and their values are always user/peer values.
Is it possible for us to add a new feature that allows users to step in and configure its value?
Describe the solution you'd like
We always use the user-configured value first, if the user selects empty, we can fall back to the default value.
Can we organize it with the following structure? (Of course, this is just an example, not the final form):
service_graphs:
virtual_node:
defaultClientValue: foodefaultServerValue: bar
When using service_graph, we usually find that the entry nodes are all virtual_node type (of course, this is expected), and their values are always
user/peer
values.Is it possible for us to add a new feature that allows users to step in and configure its value?
Describe the solution you'd like
We always use the user-configured value first, if the user selects empty, we can fall back to the default value.
Can we organize it with the following structure? (Of course, this is just an example, not the final form):
Describe alternatives you've considered
None
Additional context
Related code:
tempo/modules/generator/processor/servicegraphs/servicegraphs.go
Lines 390 to 421 in c34cf3a
The text was updated successfully, but these errors were encountered: