-
Notifications
You must be signed in to change notification settings - Fork 103
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
Gauge mapping errors #10
Comments
One solution might be to have a Gauge-mapping for each data type. |
do you have an example I could use for a failing test here? |
I stumbled upon this bug while tryingon elasticsearch-metrics-reporter in a http://www.dropwizard.io installation. Seems to be quite common for gauges with different value types. Tried to create a failing test here, sometimes there's an exception on the output, but I failed to reproduce it consistently and assert on it since the exception happens inside elasticsearch. Anyway, when the problem is that elasticsearch automatically creates a mapping for the first value, which is a double:
When lateron a gauge comes along with a string value, the following exception is thrown in elasticsearch:
and the gauge is lost :( |
Stagemonitor seems to use an approach where the value is mapped to a given type: https://www.elastic.co/blog/elasticsearch-as-a-time-series-data-store (value, value_string, value_boolean) |
I created a PR for this: #49 |
When the dynamic mapping has created the mapping for a gauge of type
T
, other gauges of other types fails with mapping errors.The text was updated successfully, but these errors were encountered: