Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add archive traces UI configuration #171

Merged

Conversation

pavolloffay
Copy link
Member

Signed-off-by: Pavol Loffay [email protected]

Resolves: jaegertracing/jaeger-ui#7

@ghost ghost assigned pavolloffay Nov 15, 2018
@ghost ghost added the review label Nov 15, 2018
Copy link
Contributor

@objectiser objectiser left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - although at some point might be good if format changed to be consistent with dependencies, e.g. {"archive":{"menuEnabled":true}}

@pavolloffay
Copy link
Member Author

you can raise it in the UI repo

@pavolloffay pavolloffay merged commit 3c6bd6c into jaegertracing:master Nov 15, 2018
@ghost ghost removed the review label Nov 15, 2018
@pavolloffay
Copy link
Member Author

Thinking about this, Not sure if there are more conf props for the archive. I think dependencies is an object because there are two properties.

@@ -340,6 +341,8 @@ An example configuration file:

`dependencies.menuEnabled` enables (`true`) or disables (`false`) the dependencies menu button. Default: `true`.

`archiveEnabled` enables (`true`) or disables (`false`) the archive traces button. Default: `false`. It requires a configuration of an archive storage in Query service.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might be useful to explain what "archiving" means", given this confusion: jaegertracing/jaeger#818 (comment)

@pavolloffay
Copy link
Member Author

pavolloffay commented Nov 16, 2018 via email

@tiffon
Copy link
Member

tiffon commented Nov 28, 2018

@pavolloffay You're right, the archiveEnabled is a top-level property because it's a single isolated value.

I commented with trade-offs to both approaches in the UI ticket: jaegertracing/jaeger-ui#277 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants