-
Notifications
You must be signed in to change notification settings - Fork 527
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
Allow setting numbers as tags #828
Comments
Do you mean something similar as This wouldn't be a big issue from a technical point of view (except for the one open issue that we also have with marks #708). |
Yes, similar to marks, but mark values should always be a timestamp in ms, right? Shouldn't we map it to a date then? For this, we should pre-define a mapping so that we don't have the issue mentioned in #708. Double would be the most flexible datatype for this I guess. |
Are you considering nested objects with |
Just flat key value pairs with double values |
@felixbarny is this related to Open Tracing? |
OpenTracing allows to set string, boolean and number tags. Converting the numbers to strings does not really break the contract, but it means the users can't create graphs based on the number tags. Example: the user could add a tag to a checkout cart span which represents the total value of the cart. If we don't support number tags, the user can't create a Kibana visualization with graphs the revenue. |
@felixbarny and I discussed offline and while OT prescribes both:
it doesn't prescribe how the values should be stored or how users should be able to query them. I understand this would be useful, but in order to avoid holding up OT support, let's consider this to be unrelated to OT. |
Side-note: If it's easy to do while we're changing this anyway, I would like to propose that we also support boolean values. |
Is it on working? |
We are investigating options to implement this, but it hasn't been implemented yet. |
Is there any roadmap about it? Or any other alternative solutions? And can I help anythings about it? :) |
@felixbarny I suggest to use a Possible solution in ES:
Insert example doc
Fetching mapping with
|
Store numbers as scaled_floats, scaling_factor 1000000 fixes elastic#828.
Store numbers as scaled_floats, scaling_factor 1000000 fixes elastic#828.
@toughrogrammer there is WIP PR #1712 which you can follow. |
* Allow numbers and boolean values for tags. Store numbers as scaled_floats, scaling_factor 1000000 * Update tags in metricset to behave the same way as transaction.tags fixes #828.
* Allow numbers and boolean values for tags. Store numbers as scaled_floats, scaling_factor 1000000 * Update tags in metricset to behave the same way as transaction.tags fixes elastic#828.
Having the ability to set custom number values which are indexed in Elasticsearch allows to create aggregated graphs based on transactions.
For example, you could track the number of search results for a search transaction, along with the search query to get a list of the top searches without results.
The text was updated successfully, but these errors were encountered: