Skip to content

Deploy Virtana Service Observability

Deploying Virtana Service Observability is a collaborative process between your IT department and Virtana Professional Services personnel. The following sections outline the process and include links to the resources that will help you get up and running as quickly and efficiently as possible. Deployment starts immediately after we sign a contract together.

1. Exchange information

Virtana Professional Services requests user and infrastructure information and files a Virtana Support ticket to record and track the information, including:

  • Support accounts — Virtana Support personnel create an account in our support system for your technical lead, and your technical lead creates accounts for additional team members as required.

  • Training system accounts — The names and email addresses of the initial group of users to train. Once the users are added to the Virtana University, the self-directed Virtana Service Observability Operator class can be started immediately.

  • Initial Virtana Service Observability users — The full names and email addresses of the initial (administrative) Virtana Service Observability users. Virtana Operations creates accounts for these users with the native identity management feature of Virtana Service Observability.

    If you plan to integrate your own identity management service, you can skip this.

  • List of initial devices — A list of the devices and applications that have the biggest impact on your business.

    This is the first step of an iterative, ongoing process.

  • Infrastructure names — Names for your Virtana Service Observability tenant, Collection Zones, and collectors.

    Please take time to consider these names; once chosen, they cannot be changed.

2. Create infrastructure

Virtana Operations creates your Virtana Service Observability tenant, Collection Zones, and collectors using the names you provide.

3. Prepare devices

With our help, you begin the process of preparing devices for use in a Collection Zone. This process ensures that the devices to monitor can, for example, send SNMP data or are otherwise configured for the access required to gather model and metric data.

Keep in mind, you don't need a collector to send data! Use one or more streaming data clients to begin sending data to Virtana Service Observability immediately.

4. Conduct kickoff meeting

Whenever possible, we gather at your facility to hold the project kickoff meeting. Virtana personnel attend either in person or through teleconference.

5. Install collector appliances

With our help, you create virtual machines with a Virtana Service Observability Collector virtual appliance package.

6. Integrate identity service

With our help, you can integrate your own identity management service such as Active Directory or LDAP, if desired. This is an alternative to the native identity management features of Virtana Service Observability and is not required.

7. Broaden the scope

This part of the deployment process involves more devices and people in your organization:

  • Load and configure devices — With our help, you add devices to Virtana Service Observability to begin modeling and monitoring them. This process continues throughout deployment and beyond.

  • Attend training — Your team attends instructor-led, online training sessions, along with your Virtana deployment consultant.

  • Optional: Begin custom ZenPack development — Unique devices or integrations may require custom ZenPacks, which Virtana Professional Services can develop at your request.

  • Optional: Begin integrating CMDB or Incident Management — If your environment includes these products, the process of integrating with Virtana Service Observability would begin.

8. Transition to Virtana Support

When the initial device load is complete and the system is working as designed, Virtana deployment consultants bow out and hand off to Virtana Support.