Skip to content

[PLINT-524] Sending data from vSAN using Resource Metadata #19070

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

Closed
wants to merge 14 commits into from

Conversation

rahulkaukuntla
Copy link
Contributor

@rahulkaukuntla rahulkaukuntla commented Nov 15, 2024

What does this PR do?

This PR enables sending vSAN cluster data using Resource Metadata, so that vSAN clusters can be viewed in the Resource Catalog. Changes to the backend had to be enabled in order for this new data to be written to the correct table, so that the Resource Catalog can pick it up correctly.

Motivation

Review checklist (to be filled by reviewers)

  • Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
  • Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
  • If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

Copy link

codecov bot commented Nov 15, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.10%. Comparing base (19e46a8) to head (1d07d6a).
Report is 1018 commits behind head on master.

Additional details and impacted files
Flag Coverage Δ
activemq ?
cassandra ?
hive ?
hivemq ?
hudi ?
ignite ?
jboss_wildfly ?
kafka ?
presto ?
solr ?
vsphere ∅ <100.00%> (∅)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@rahulkaukuntla rahulkaukuntla changed the title [PLINT-524] Sending data from vSAN to EvP intake [PLINT-524] Sending data from vSAN to REDAPL Dec 9, 2024
@rahulkaukuntla rahulkaukuntla marked this pull request as ready for review December 17, 2024 17:56
@rahulkaukuntla rahulkaukuntla requested a review from a team December 17, 2024 17:56
@rahulkaukuntla rahulkaukuntla requested a review from a team as a code owner December 17, 2024 17:56
@@ -439,9 +440,12 @@ def get_vsan_metrics(self, cluster_nested_elts, entity_ref_ids, id_to_tags, star
)
health_metrics.append(processed_health_metrics)

redapl_cluster_data = {'name': cluster_reference.name, 'vcenter_server': self.config.hostname}
vsan_perf_query_spec = []
for nested_id in nested_ids:
for entity_type in entity_ref_ids[id_to_tags[nested_id][0]]:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

... entity_ref_ids[id_to_tags[nested_id][0]]:

is this access completely safe?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I create all of these dictionaries: entity_ref_ids,id_to_tags,nested_id in this method. I define that every collected resource be included in id_to_tags by their id, and I define that their "0" value be the type of the resource. Basically, I just want to see, for each resource within a given cluster, what type of resource it is (either a host or the cluster itself, for now), and then depending on the type of the resource, choose the entities (list of metrics) that are appropriate to find for it.

@rahulkaukuntla rahulkaukuntla changed the title [PLINT-524] Sending data from vSAN to REDAPL [PLINT-524] Sending data from vSAN using Resource Metadata Dec 18, 2024
rtrieu
rtrieu previously approved these changes Dec 18, 2024
Copy link
Contributor

@rtrieu rtrieu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor feedback to comply with our style guide.

Co-authored-by: Rosa Trieu <107086888+rtrieu@users.noreply.github.com>
rtrieu
rtrieu previously approved these changes Dec 18, 2024
@rahulkaukuntla rahulkaukuntla marked this pull request as draft February 20, 2025 16:26
@NouemanKHAL NouemanKHAL removed their request for review June 25, 2025 09:07
@dd-devflow dd-devflow bot closed this Jul 17, 2025
@dd-devflow dd-devflow bot deleted the rahul/vsphere-to-evp branch July 17, 2025 00:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants