Integers in custom fields will be rendered as string about cf-nodejs-logging-support HOT 2 CLOSED

In our Logstash/Kibana solution all custom fields are deliberately converted to Strings. This decision was made to ensure proper operation on name conflicts: In Elasticsearch each field has a fixed type. This type is either determined by a mapping or created on the fly from the first document. Documents with mismatching types cannot be ingested. As we have no control over the field names we decided to treat all custom fields as string type (keyword).

The use-case for custom fields as you suggest points to metrics and/or monitoring. This is currently unsupported. We are evaluating different strategies to provide better support of such use-cases.

from cf-nodejs-logging-support.

Ok, thanks for your answer. We will look into alternative approaches.

from cf-nodejs-logging-support.