Hi @mtojek,
After refresh the index, It is not working Marcin.
There is a showing a some info..
4 fields are defined as several types (string, integer, etc) across the indices that match this pattern. You may still be able to use these conflict fields in parts of Kibana, but they will be unavailable for functions that require Kibana to know their type. Correcting this issue will require reindexing your data.
Thank you for your inputs. As this is not a fresh installation, we are using elasticsearch since two years. But, recently installed AWS RDS metricset. Please let me know if you need logs from application.
As you may see, there is a field conflict with some existing ones. If this is the first time you're using metricbeat, the quickest way to fix would be deleting metricbeat-* index. Otherwise you will need a new index for AWS data.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.