Setting up access between IO and Global View

The integration between IO and Global View enables you to synchronize infrastructure performance and utilization data with Global View, providing a unified platform for monitoring, analysis, and proactive management. This integration helps you to gain comprehensive visibility into both resource efficiency and cost trends across your hybrid environments, allowing you to quickly identify anomalies, optimize spending, and respond to alerts in context.

The ultimate goal is to enable IO data, including collected metrics and triggered alarms, to be successfully synchronized and displayed in the Global View Capacity and Alerts dashboards, providing a unified monitoring and analysis environment.

Prerequisites of IO and GV integration

Before starting the integration, ensure you meet the following requirements:

You must have administrator privileges in both Global View and IO.
Ensure that you have an active Global View (GV) account and have generated OAuth client credentials.

Generate OAuth credentials

You can generate OAuth client credentials by performing the following steps:

Log in to your Virtana account and click Settings ().
In the side menu, click Integrations and select Virtana Platform API.
Click Generate OAuth Client Credentials.
The New Credentials dialog box opens.

Enter a name, description for the credentials, and assign a user group.

You can select the user group, such as Administrators, Administrators only, to ensure secure and appropriate access control.

The impact of selecting Administrators or Administrators only as a user group is as follows:

Specification	Administrators	Administrators only
Effective Permission Scope	Inherits the full set of permissions granted to the standard Administrators role in Virtana Platform.	Restricted to the capabilities granted to the Administrators only group, which may be a more tightly scoped/security-hardened role.
IO Access Capabilities	IO can typically read all required inventory, configuration, performance metrics, utilization metrics, and alarms/cases.	IO access may be limited. If the group does not have full API access, IO may be missing read/write permissions for certain Global View resources.
Data Synchronization	Full data visibility and population of Global View Capacity and Alerts dashboards.	Partial data visibility is possible. Inventory, metrics, or alarms may be missing or incomplete in Global View dashboards.
Operational Impact	Recommended default choice for a reliable and fully functional IO and Global View integration.	Suitable only if the security model explicitly validates that the Administrators only group has equivalent or broader API access for all required IO operations.

Click Save.

If you need to remove credentials, perform the following steps:

Select and left-click on the credentials that you want to remove in the list.
The Edit Credentials window opens.
Select Revoke Credentials.
The Revoke Credentials window opens.
In the Revoke Credentials window, click Revoke.
Click Save.

Integrating IO with Global View at a Glance

This section outlines the process for integrating IO with Global View.

In Infrastructure Observability, click Settings, and then in Probes and Integrations, click Connect to Virtana Platform.
Depending on the status of your connection, do one of the following.
If no connection exists to a Virtana Platform organization:
1. Add the OAuth 2.0 client ID and client secret for the target organization in Virtana Platform.
2. Click Validate & Connect.
  A confirmation message informs you that the connection was successful.
If a connection already exists to a Virtana Platform organization:
1. Click Connect to a different organization.
2. Add the OAuth 2.0 client ID and client secret for the target organization in Virtana Platform.
3. Click Validate & Connect.
  A confirmation message informs you that the connection was successful.

To configure IO properties to integrate with Global View, perform the following steps:

In Settings, click Service Management under the Appliance Configuration.
Search for the IO Cloud Sync in the search bar.
Click the value under the properties column.
The IO Cloud Sync Properties window opens.

Review and update the properties in the Property Name field with the respective value.

IO Cloud Sync Integration Properties (IO Cloud Sync service):

Property	Default Behavior	Action
`com.vi.integrations.vcs.platform.region`	Defaults to country (derived from the appliance’s TimeZone).	Use to explicitly set the region, for example, `USA`.
`com.vi.integrations.vcs.platform.datacenter`	Defaults to city (derived from the appliance’s TimeZone). If the city cannot be determined, it falls back to the hostname.	Use to explicitly set the datacenter, for example, `Boston`.
`com.vi.integrations.vcs.tls.trust_all_certs`	Certificate validation is enabled by default.	When set to `true`, all SSL certificates from the GV endpoint are trusted. Disable validation, as it is recommended only for testing or seamless connectivity.
`com.vi.integrations.vcs.srclink_name`	If not set, the IP address is used in URLs sent to VP.	When specified, hostname is used instead. Require VCS restart.
`com.vi.integrations.vcs.iframe.cross.origin.allow.url`	Allows cross-origin URLs in iframes for VCS integration.	Set this property to `true` if you need to embed external content in iframes within Virtana Cloud.

Caution

Set all the above required property values before enabling IO Cloud Sync.

Select Auto Refresh IO Cloud Sync once properties are updated.
The page will get refreshed automatically every 30 seconds.
In the same way, search the UI service in the search bar under Service Management.

Ensure the vw.vp_base_url is correctly set to avoid connection failures and update the other relevant properties in the Property Name field with the respective value.

Setting this property is essential while connecting to Global View, so make sure to set it first in the UI service.

UI Service Properties:

Property	Default Behavior	Action
`vw.vp_base_url`	IO does not know where to send data for Global View integration.	Set this to the URL of your Global View instance, for example, `https://gv.k8s.example.com`.
`com.vi.vp.tls.trust_all_certs`	(IO) validates SSL certificates when connecting to Global View.	Set to `true` to allow (IO) to trust all SSL certificates.
`com.vi.ui.filters.exclusions.enable`	The UI filter exclusions are not enabled by default.	Set to `true` to enable filter exclusions in the IO user interface.
`com.vi.ui.enable.debug.options`	Debug options are hidden in the (IO) user interface.	Set to `true` to display debug options in the IO UI for troubleshooting or development.

Single Sign-On (SSO) Setup
SSO setup properties and configuration options required to enable and manage Single Sign-On (SSO) in Virtana Platform. These properties are typically set during SSO integration with providers such as Okta, Azure AD, or any SAML 2.0-compliant identity provider.
Configure an application in the SSO provider:
A SAML 2.0 provider can be, for example, OKTA. In provider one needs to add an application, and provide:
- SSO URL, for example, https://vi.okta.com/api/sec/saml/login.
- Audience URL, for example, https://[FODT]/.
- The application username should be set as the email ID.
To log in with the SSO-generated IdP, see the section Log in with SSO.
On successful login, the SSO provider will redirect the page back to the Virtana Platform SAML login link. With this, Virtana Platform will validate SSO details, and upon successful validation user will be taken to the appropriate landing page.

For more details, refer to this Virtana Platform process.

Verifying if IO Data Appears in Global View

This section outlines the verification steps to ensure a seamless connection has been established between IO and Global View.

Activate IO Cloud Sync. Ensure the IO Cloud Sync service is running by navigating to Service Management in Settings, and verify that the IO Cloud Sync service is running.
Data metrics should be successfully collected and discovered by at least one integration in IO without any issues. Navigate to the Service Management in Settings section of IO to verify that the key data collection services are running. This ensures that IO captures essential data for monitoring.
Configure Alarms in IO if you do not have any existing alarms.
To create a property-based alarm rule, perform the following steps:
1. Navigate to the Cases and Alarms and click Rules.
2. On the Rules page, click New and select Property from the dropdown.
3. Provide a unique name and a brief description for your new alarm rule.
4. Select the Entity Type and (optional) apply filters.
5. In the Add Property Criteria field, configure the alarm parameters and select the severity for the alarm.
  Click to add multiple properties.
6. Select the Actions and save the Rule.
  The rule will appear in the rules list with the template set to property. Cases are generated as per the rule criteria.
Once an alarm is triggered in IO according to configured rules, it will appear as an alert in the Global View Alerts dashboard.
Check the Capacity Dashboard
1. Navigate to the On-Premises Storage Array Cost And Capacity Summary/On-Premises Compute Cost And Capacity in the Dashboard section of the Global View.
2. Verify if the data is displayed accurately.

Note

The datacenter set in the parameters will display as the site property on the array capacity pages in Global View. See On-Premises Storage Array Cost and Capacity Summary.

Getting Help

Perform the following tasks if the data is not syncing:
- Check appliance health: In Global View, click IO in the top menu to view the IO appliance that is having syncing issues.
- Validate OAuth credentials: Confirm that you have entered the correct OAuth 2.0 client ID and client secret for your Virtana Platform organization in the IO appliance settings.
- Verify vw.vp_base_url: Make sure the vw.vp_base_url property is set correctly in the UI Service properties. An incorrect URL will prevent data synchronization.
- Refresh the service: If the service is stopped, enable the Auto Refresh in the service management interface.
- Check data collection: Ensure that IO is successfully collecting data metrics from at least one integration. If data collection fails, synchronization to Global View will not occur.
- Review logs: Examine IO and Global View logs for error messages related to data transfer or authentication. To view these logs, navigate to Service Management in Settings of IO and click Download All Logs.
Perform the following tasks if the UI Service is not running:
- Service status: Navigate to Service Management in Settings of IO and check if the UI Service is running/stopped under the Status column.
- Refresh the service: If the service is stopped, enable the Auto Refresh in the service management interface.
- Check configuration: Verify that all required properties, such as vw.vp_base_url, are set before enabling the UI Service.
- Review system resources: Ensure the IO appliance has sufficient resources to run the UI Service.
- Consult logs: Check the service logs for any startup errors or configuration issues.
Perform the following tasks if unable to log in to Global View/IO:
- Credentials: Double-check your username and password. If you are using SSO, ensure your SSO credentials are correct.
- Account status: Verify that your account is active and has the necessary permissions in both IO and Global View.
- Network connectivity: Ensure your network connection is stable and that there are no firewall or proxy restrictions blocking access to the Virtana Platform.
- Password reset: If you have forgotten your password, use the password reset option or contact your administrator.
Perform the following tasks if SSO is not working:
- SSO provider configuration: Confirm that the SSO application is correctly configured in your identity provider with the correct SSO URL and Audience URL.
- Certificate validity: Ensure the certificate is valid and not expired.
- Attribute mapping: Verify that the required attributes, such as name, groups, are being sent by the IdP and are correctly mapped in Virtana Platform.
- SSO URL: Make sure you are accessing the correct SSO login URL as configured in your provider.
- Logs and error messages: Review any error messages displayed during login and consult the authentication logs in both Virtana Platform and your SSO provider for more details.
- Contact support: If the issue persists, contact your IT administrator or Virtana support at support@virtana.com for assistance.

In this section: