We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Description Hi team, After upgrading the app to 4.1.0-7.10.0 we are getting the following errors in system logs:
Feb 2 09:43:25 ip-172-31-36-201 performance-analyzer-agent-cli: 09:43:25.381 [pa-reader] ERROR com.amazon.opendistro.elasticsearch.performanceanalyzer.reader.ReaderMetricsProcessor - Error reading file '/usr/share/elasticsearch/data/batch_metrics_enabled.conf': java.nio.file.NoSuchFileException: /usr/share/elasticsearch/data/batch_metrics_enabled.conf
The module performance analyzer shouldn't be active. Steps to reproduce
We installed the app in AZL2 system with Elastic, Kibana and manager in the same node.
[root@ip-172-31-36-201 logs]# cat /etc/os-release NAME="Amazon Linux" VERSION="2" ID="amzn" ID_LIKE="centos rhel fedora" VERSION_ID="2" PRETTY_NAME="Amazon Linux 2" ANSI_COLOR="0;33" CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2" HOME_URL="https://amazonlinux.com/"
Screenshots If applicable, add screenshots to help explain your problem.
Regards, Víctor.
The text was updated successfully, but these errors were encountered:
This does not seem to be related to the app directly but to a configuration of the Open Distro module for Elasticsearch.
I found the next issue with the exposed error, it could be useful. opendistro-for-elasticsearch/performance-analyzer#229
Sorry, something went wrong.
No branches or pull requests
Description
Hi team,
After upgrading the app to 4.1.0-7.10.0 we are getting the following errors in system logs:
The module performance analyzer shouldn't be active.
Steps to reproduce
We installed the app in AZL2 system with Elastic, Kibana and manager in the same node.
Screenshots
If applicable, add screenshots to help explain your problem.
Regards,
Víctor.
The text was updated successfully, but these errors were encountered: