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
Requirement - what kind of business use case are you trying to solve?
The UI is not documented anywhere. (Aside from the configuration options.)
Problem - what in Jaeger blocks you from solving the requirement?
Currently, the UI code is the only place that will inform users how the UI works, aside from the UI configurtaion.
For instance, if a user wanted to understand the search in the trace detail page, checking the code or PR is the only way they would learn it's case-insensitive and prefacing a term with a hyphen, e.g. -stacktrace, will exclude keys containing the term from the tags or log fields checked.
Proposal - what do you suggest to solve the problem or improve the existing situation?
Create a top-level section in the docs for the UI. The reason I suggest a top-level section is because it doesn't seem to fit within the existing sections.
Any open questions to address
Mainly if this is a good idea or not.
cc @aljesusg who is preparing docs for a new feature.
The text was updated successfully, but these errors were encountered:
Requirement - what kind of business use case are you trying to solve?
The UI is not documented anywhere. (Aside from the configuration options.)
Problem - what in Jaeger blocks you from solving the requirement?
Currently, the UI code is the only place that will inform users how the UI works, aside from the UI configurtaion.
For instance, if a user wanted to understand the search in the trace detail page, checking the code or PR is the only way they would learn it's case-insensitive and prefacing a term with a hyphen, e.g.
-stacktrace
, will exclude keys containing the term from the tags or log fields checked.Proposal - what do you suggest to solve the problem or improve the existing situation?
Create a top-level section in the docs for the UI. The reason I suggest a top-level section is because it doesn't seem to fit within the existing sections.
Any open questions to address
Mainly if this is a good idea or not.
cc @aljesusg who is preparing docs for a new feature.
The text was updated successfully, but these errors were encountered: