apm-server-1 | {"log.level":"error","@timestamp":"2023-06-13T12:37:45.116Z","log.logger":"beater","log.origin":{"file.name":"beater/waitready.go","file.line":62},"message":"precondition 'apm integration installed' failed: error querying Elasticsearch for integration index templates: unexpected HTTP status: 404 Not Found ({\"error\":{\"root_cause\":[{\"type\":\"resource_not_found_exception\",\"reason\":\"index template matching [metrics-apm.service_summary.60m] not found\"}],\"type\":\"resource_not_found_exception\",\"reason\":\"index template matching [metrics-apm.service_summary.60m] not found\"},\"status\":404}): to remediate, please install the apm integration: https://ela.st/apm-integration-quickstart","service.name":"apm-server","ecs.version":"1.6.0"}
Yes APM and fleet require xpack.security, and it’s not working yet. We are getting closer to make it work thanks to parallel experimental work we did on supporting ECK.
None just yet! @coutoPL is working on finalizing the changes that make ROR work with ECK, and the situation is highly improved compared to the total unusability of apps like APM. But more work is required to make all the necessary bits work (even in APM alone). That will be done right after.
However, we are in a much better position.We are now able to:
start ROR with xpack.security enabled
mock xpack security requests from ES plugin
Need to get through a boring trial and error until things start working. Unless we discover something ultra weird in the process, it should be possible.