opensearch-project / opensearch-project/performance-analyzer
[BUG] On version 2.11.0, the plugin does not return metric values
Open
Nobody has claimed this yet.
bug
- Dominant language
- Java
- Stars
- 48
- Forks
- 78
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 5
Description
Hello! Performance analyzer is successfully enabled, but the response to the metrics request is empty.
opensearch version: 2.11.0
my configuration:
metrics-location = /dev/shm/performanceanalyzer/
metrics-deletion-interval = 1
cleanup-metrics-db-files = true
webservice-listener-port = 9600
rpc-port = 9650
metrics-db-file-prefix-path = /tmp/metricsdb_
https-enabled = true
certificate-file-path = /opt/opensearch/config/certs/edu-osm-21.pem
private-key-file-path = /opt/opensearch/config/certs/edu-osm-21-key.pem
trusted-cas-file-path = /opt/opensearch/config/certs/root-ca.pem
client-certificate-file-path = /opt/opensearch/config/certs/admin.pem
client-private-key-file-path = /opt/opensearch/config/certs/admin-key.pem
client-trusted-cas-file-path = /opt/opensearch/config/certs/root-ca.pem
webservice-bind-host = 0.0.0.0
plugin-stats-metadata = plugin-stats-metadata
agent-stats-metadata = agent-stats-metadata
and response from server
{
"6pU61DPLRMGZGjfSwyQ2Lw": {
"timestamp": 1720612630000,
"data": {
"fields": [
{
"name": "CPU_Utilization",
"type": "DOUBLE"
}
],
"records": []
}
}
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named in the report. Start by reproducing the metrics request with OpenSearch 2.11.0 and the supplied configuration, then trace why the response contains fields but no records; done means the request returns metric values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100