Centralized Log Collection – App Volumes 2.12

As you all aware that App Volumes 2.11 was released  earlier this month with exciting new set of capabilities and huge improvements that gives a great user experience. Also as per me App Volumes is the only solution optimized and certified on the VMware SDDC.

In this App Volumes seventh release VMware announced several new features as a part of tech preview.

  1. Asynchronous Mounting
  2. Read-Only Role in App Volumes Manager
  3. Centralized Log Collection

In my previous article we have seen on how to enable “Read-Only Role in App Volumes Manager”. This post will walk you through the instructions to setup”Centralized Log Collection” in App Volumes 2.12.

Centralized Log Collection :

Note : The Tech Preview features and capabilities are not supported for production deployment, rather they are available as a preview of potential upcoming innovations to test in a lab or UAT environment.

Here are the Features and Befits:

  1. Its Central repository for App Volumes Manager and App Volumes Agent logs.
  2. Enables centralized log collection.Centralized Log

 

Enable and Configure Log Collection :

In my test lab,i have created a files share on the Appvolumes manager server and set the appropriate permission level to the services account for configuring centralized log collection.

Here is the recommendation;

  • Remote file share path MUST end with a folder called “logs”
    •  Example: \\<myfileshare_IP>\AppVolumes\logs
  • Remote file share should use IP rather than FQDN.
  • Configure NTFS and share permissions for Log Fileshare User. “NTFS – Modify,Share – Change
  • Agent Time is in minutes, but recommend setting this for hours.
  • Example – 720 minutes = 12 hours.
  • SSL validation must occur for this setting to function.

Lets go ahead and configure,

  1.   Open a browser and navigate to http://<AVM FQDN>/log_filesshares/new1

2.   Enter all the required information  and Click on Create Log Share.

Log File Share Host name This is host and folder name for your Log Fileshare.
For example, //192.168.2.101/Appvol_Logs/logs (Ensure that your path ends with a logs folder)
Log Fileshare Username Username of the Log Fileshare
Log Fileshare Password Password of the Log Fileshare
Log Fileshare Domain Domain of the Log Fileshare
Log Fileshare Agent Time The agent will periodically push log files to the fileshare. This parameter will help in setting how much time delay is required. Time is denoted in minutes.

2

3.  Your Log File Share has been created now.

3

4.  To Display Current Configuration just try the below URL.

  • http://<AVM>/log_fileshares/active
  • Shows PW in clear text.

2016-12-25_12h45_36

5. Edit Existing Configuration

  • http://<AVM>/log_fileshares/edit

2016-12-25_17h28_07

6. View and Delete

  • http://<AVM>/log_fileshares

2016-12-25_12h44_58

  • AV Agents will automatically collect logs based on the Agent Time setting configured for the log fileshare.
  • AV Manager will automatically collect logs every 12 hours.
  • Manual log collection is an option, and doesn’t rely on the logfiles share configuration.

Running batch scripts on Agents and Managers:

In Windows, no setup is required. The bat script is shipped with the Agent and Manager images. To collect Agent logs, ensure https is enabled; otherwise, this feature will be turned off in the Agent.

Note: The bat script needs administration privileges to run.

The bat script can be run from C:\Program Files (x86)\CloudVolumes\DctLogCollector\support.bat.

Parameters for support.bat

Description

-destination

Destination of the log files on the machine

-fhhost

Location of the folder on hostname of the fileshare

For example, \\xx.xx.xx.xx\logs (Ensure that the folder named logs exists)

-fhuname

Username of the fileshare owner

-fhdomain

Domain under which the fileshare is located

-fhpwd

Password of the username for the fileshare owner

Example of running the script:

support.bat –fhhost \\192.168.2.101\appvol\logs -fh domain vsphereworld –fhuname svc-appvol -fhpwd XXXXX

For more information please refer the VMware KB : 2148180

Related Posts: