Skip to content

🧩 Ensuring IO Appears in Global View (GV)

This document outlines the prerequisites and step-by-step process required for Infrastructure Observability (IO) integration to appear successfully in the Global View (GV). It covers account setup, property configurations, and validation steps for seamless visibility.

📌 Prerequisites

1. GV Account and OAuth Credentials

  • Requirement: Ensure the customer has an active Global View (GV) account and generated OAuth client credentials.

🔑 Steps to Generate Credentials:

  1. Log into the GV account.
  2. Navigate to Integrations → Virtana Platform API.
  3. Click Generate OAuth Client Credentials.
  4. Provide a name and optional description, then click Save.

🔧 IO-to-GV Integration Steps

2. Connectivity to Global view

  • Ensure the **IO appliance ** can connect to the Global view endpoint or cloud environment.

3. Install or Upgrade IO Cloud Sync

  • Upgrade: Validate the current IO Cloud Sync build version.
  • Fresh Install:
    • Download the latest IO Cloud Sync bundle from the UPD repository.
    • Example (v1.2.9): [Download IO Cloud Sync Bundle]

4. Enable CloudSync

🔔 Note: - Setting this property is essential while connecting to GV, so make sure to set it first in the UI service. - The property is also mentioned in the UI Service Properties section below.

vw.vp_base_url=<GLOBAL VIEW URL>  # e.g., https://gv.k8s.example.com/
  • Use the Client ID and Secret (from Step 1) in the IO appliance at:
https://<IO appliance>/#settings/connect-to-virtana-platform

✅ Ensure the connection is successful before proceeding.

5. Configure IO Properties to Integrate with GV

Note: - Restart IO Cloud Sync once properties are updated, as they are generally read at startup. - Ensure the vw.vp_base_url is correctly set to avoid connection failures. - By default flag properties are set to false, change them to true if needed.

🛠 IO Cloud Sync Integration Parameters (IO Cloud Sync service)

com.vi.integrations.vcs.platform.region=<region> #eg: USA
com.vi.integrations.vcs.platform.datacenter=<datacenter> # eg: Boston
com.vi.integrations.vcs.tls.trust_all_certs=true
com.vi.integrations.vcs.srclink_name=hostname  ## Just hostname from your IO URL not required https:// if not set some default name will be used like VI-Appliance

🖥 UI Service Properties

vw.vp_base_url=<GLOBAL VIEW URL>   ## e.g., https://gv.k8s.example.com/
com.vi.vp.tls.trust_all_certs=true
com.vi.ui.filters.exclusions.enable=true
com.vi.ui.enable.debug.options=true

✅ Validation Steps

6. IO Cloud Sync Service Activation

  • Confirm that the IO Cloud Sync is running.
  • This is essential for backend integration and sync with GV.

7. Active Data Metric Collection

  • At least one integration in IO must be collecting and discovering metrics.
  • Without data flow, GV won’t reflect IO.

8. Configured Alarms in IO

  • Alarms must be:
    • Properly configured in IO once the alarm is generated it should flow in the Global View.

🖥 Global View Verification

In the Global view UI:

  • Confirm the presence of the IO source link in the Infrastructure Observability drop down on GV i.e set through the property com.vi.integrations.vcs.srclink_name as mentioned above in the IO Cloud Sync properties section.
  • Check if dashboards, alerts, and governance pages load as expected.

🧮 Capacity Dashboard Check:

Navigate to:
Infrastructure Monitoring / Global View → Dashboard → On-Premise Storage Array Capacity Summary

Infrastructure Monitoring / Global View → Dashboard → On-Premise VM Compute Capacity Summary

✅ Ensure data is accurate and updated.

❓ Frequently Asked Questions (FAQ)

1. VCS Integration Parameters: com.vi.integrations.vcs.platform.region=<region or leave blank>. How do we know what “region” to use?

Answer →
Region is picked up based on the timestamp of the appliance, but you can override it using the following properties:

com.vi.integrations.vcs.platform.region=US
com.vi.integrations.vcs.platform.datacenter=New York

2. Enable CloudSync - "Confirm the connection succeeds." What do we do if it fails? What is the next step?

Answer →
If IO to VP connection is successful and IO Cloud Sync is enabled, then it should send data to CloudCapi/GV.
There is a retry mechanism already present in IO Cloud Sync.
If you still can’t see the data on GV (even when proper integrations are available), check the logs of the IO Cloud Sync service for failures or issues.

3. Is there a way to easily validate what version of VCS is installed without generating and downloading audit logs?

Answer →
VCS is a backend service, not a UI-visible integration, so it’s not listed in the UI.
To check the version, SSH into the IO appliance and run:

```bash rpm -qa | grep vcs