Hi,
I have setup a new Connections 7 environment (medium deployment) with Elasticsearch for Metrics.
Data capturing in Metrics is not working. In AppsCluster_server1, I see the following errors:
com.ibm.connections.metrics.elasticsearch.ElasticsearchClient httpRequest ElasticSearch returned - 400 : {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"Types cannot be provided in put mapping requests, unless the include_type_name parameter is set to true."}],"type":"illegal_argument_exception","reason":"Types cannot be provided in put mapping requests, unless the include_type_name parameter is set to true."},"status":400}
com.ibm.connections.metrics.elasticsearch.ElasticsearchClient httpRequest ElasticSearch returned - 400 : {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"The bulk request must be terminated by a newline [\\n]"}],"type":"illegal_argument_exception","reason":"The bulk request must be terminated by a newline [\\n]"},"status":400}
From Elasticsearch documentation, it looks like that the index is still using / created with something from Elasticsearch v6, which is no longer supported in v7: https://www.elastic.co/guide/en/elasticsearch/reference/7.x/removal-of-types.html
Connections Highway settings include two
c2.export.elasticsearch.baseurl: https://connections-elasticsearch.mycomp.com:9200
c2.export.elasticsearch.baseurl7: https://connections-elasticsearch.mycomp.com:9200
In this environment, Elasticsearch is configured to be accessible on port 9200, not 30098 as in documentation
In Connections itself, I used these wsadmin commands to configure Elasticsearch for Metrics:
> execfile('esSecurityAdmin.py')
> enableSslForMetrics('/opt/HCL/Elasticsearch/elasticsearch-metrics.p12', 'password', '/opt/HCL/Elasticsearch/chain-ca.pem', '9200')
> execfile('metricsEventCapture.py')
> switchMetricsToElasticSearch()Any similar experiences?
Greetings
Maik