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

Adds AutocompleteTags and corresponding REST api #2332

Merged
merged 2 commits into from
Dec 17, 2018

Conversation

codefromthecrypt
Copy link
Member

@codefromthecrypt codefromthecrypt commented Dec 17, 2018

This adds an optional storage interface AutocompleteTags to the
StorageComponent and corresponding endpoints to support the UI.

/api/v2/autocompleteKeys and /api/v2/autocompleteValues?key=http.host

Cache control is always set on the keys, and it is set conditionally on values when there are more than 3. The "more than 3" allows for a freshly booting system to not confuse users (we do the same thing on /api/v2/spans?serviceName=foo endpoint).

The server accepts an environment variable AUTOCOMPLETE_KEYS
which acts as a whitelist as storing values for every tag would be
expensive.

This adds an optional storage interface `AutocompleteTags` to the
`StorageComponent` and corresponding endpoints to support the UI.

/api/v2/autocompleteKeys and /api/v2/autocompleteKeys?key=http.host

The server accepts a parameter `zipkin.storage.autocompleteKeys`
which acts as a whitelist as storing values for every tag would be
expensive.
@codefromthecrypt
Copy link
Member Author

@tacigar @zeagord @shakuzen PTAL I suspect we can merge this on green

@zeagord
Copy link
Member

zeagord commented Dec 17, 2018

Sure. I think so too.

@codefromthecrypt codefromthecrypt merged commit 611e92a into master Dec 17, 2018
@codefromthecrypt codefromthecrypt deleted the autocomplete-tags branch December 17, 2018 07:16
abesto pushed a commit to abesto/zipkin that referenced this pull request Sep 10, 2019
* Adds AutocompleteTags and corresponding REST api

This adds an optional storage interface `AutocompleteTags` to the
`StorageComponent` and corresponding endpoints to support the UI.

/api/v2/autocompleteKeys and /api/v2/autocompleteKeys?key=http.host

The server accepts a parameter `zipkin.storage.autocompleteKeys`
which acts as a whitelist as storing values for every tag would be
expensive.

* Info when not implemented and backfill tests
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.

None yet

3 participants