Closed jsmanrique closed 5 years ago
Thank you for reporting this issue! Which index(es) are you referring to?
A workaround is to refresh the index patterns in kibana, after that you will see the missing fields.
I guess the reason of not having cm_*
fields in the index patterns is due to the fact that they are custom fields, and thus they are not present by default.
Please @alpgarcia share your opinion, thanks
Thank you @valeriocos, that helped. Let's wait for @alpgarcia comments
This is probably out of the scope of Gelk. This happens when Mordred uploads standard index patterns from Sigils, so any custom field will either not be present or disappear from the index pattern (if you manually added them to the index pattern).
The only way to support this would be checking the projects.json
file after uploading standard index patterns and dynamically add custom fields to Kibana index pattern object. That means uploading an index pattern to the dashboard should trigger this check to make sure custom fields are always kept.
Custom fields could be modified in the index pattern by the user, so we couldn't simply overwrite the index pattern and then add them, but we will also need to keep those changes. So, should we consider custom an index pattern having custom fields? (and thus not updating that index pattern and the affected panels anymore)
I'm closing this issue here as Gelk can't handle this. Please open a similar one in sirmordred if needed.
I have a projects.json file that include some custom fields inside the
meta
field like:In the data discovery tab I see expected
cm_title
andcm_type
fields with the right data. Butcm_type
cannot be visualized, because it's not in the index pattern.cm_title
appears as field with typetext
.Would it be great adding any custom field in
meta
to the index pattern ascm_{custom field name}
with typetext
.