Skip to content
New issue

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

[FEATURE] Cluster config API should provide meaningful status instead of a bitmap encoded numeric value #322

Closed
kkhatua opened this issue Nov 1, 2022 · 0 comments · Fixed by #342
Assignees
Labels
enhancement New feature or request good first issue Good for newcomers v3.0.0

Comments

@kkhatua
Copy link
Member

kkhatua commented Nov 1, 2022

Is your feature request related to a problem?
When checking cluster state of Performance Analyzer, the responses are bit-encoded numeric values, which don't provide much meaningful insight.

GET localhost:9200/_plugins/_performanceanalyzer/cluster/config
{"batchMetricsRetentionPeriodMinutes": 7, "currentPerformanceAnalyzerClusterState": 19, "shardsPerCollection": 0}

The value of 19 translates to 0b1011, which in turn provides the following being enabled:

  1. PerformanceAnalyzer : Enabled (LSB)
  2. RCA Engine : Enabled
  3. Logging : Disabled
  4. BatchMetrics : Enabled
  5. ThreadContentionMonitoring : Disabled (MSB)

What solution would you like?
The response should be meaningful like:

GET localhost:9200/_plugins/_performanceanalyzer/cluster/config
{
	"batchMetricsRetentionPeriodMinutes": 7,
	"currentPerformanceAnalyzerClusterState": {
		"PerformanceAnalyzer": "enabled",
		"Rca": "enabled",
		"Logging": "enabled",
		"BatchMetrics": "enabled",
		"ThreadContentionMonitoring": "enabled"
	},
	"shardsPerCollection": 0
}

What alternatives have you considered?
None

Do you have any additional context?
None

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers v3.0.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants