TVS Manager enables single click log generation and bundling versus what would normally be tens of clicks on a variety of screens.

After TVS Manager is installed, an action, Collect Logs, will be available on all adapter instances of TVS Management Packs.

To collect logs:

  1. Select the correct adapter instance from Inventory (or Inventory Explorer).
  2. Click the gear on the left side of the toolbar
  3. Click Collect Logs
  4. A pop-up window will request additional parameters; these parameters are: 
    • Collections: The number of collections to wait to complete (default: 10)
    • Timeout: The length of time (in minutes) to wait for the specified number of collections to complete (default: 60 minutes)
    • Restart?: Whether to restart the adapter instance before collecting logs (default: true)

After submitting the action, it will show up under History > Recent Tasks on the vROps Administration tab.

Status messages will be shown after selecting the action in the recent tasks list.

When the the task completes check for the status message Bundle ID:. This will tell you which Support Bundle was generated by the task.You can download the bundle from Administration > Support > Support Bundles

Possible Error Messages:

  • Unable to run collectLogs Action. collectLogs is already running on Collector ID 1
    • This means that Collect Logs is already running on the given collector node. Wait until the other action is finished.
  • Unable to find result for action collectLogs
    • This means that the result was removed before it was retrieved. If this error happens, Contact Support.
    • The likely cause is a TVS Manager Adapter instance being restarted by a user and a collect logs thread was not properly cleaned up.
  • Extended Log file long_run_$SOLUTIONID_$RESOURCEID.log was not created.
    • The log file wasn't created (reason unknown). Contact Support.
    • Likely causes are: no write permissions on File/folder, or lack of disk space.
  • Unabled to locate file at path $LOG4J_PROPERTIES_FILE_LOCATION
    • The known path for is incorrect on the customer's system. Contact Support.
  • Only one adapter instance per action is supported for the Collect Logs action.
    • User attempted to collect logs for more than one adapter instance. Select only one adapter instance to run an action against.
  • No adapter instance given to the Collect Logs action.
    • The user should not encounter this error (this parameter is given by vROps). Contact Support.
  • Missing required fields for log collection: any of {timeout, collections, resourceId, adapterKindKey, collectorId, restartAdapterInstance}
    • The user should not encounter this error (The parameter validation is done by vrops before given to the adapter instance action). Contact Support.
  • Cannot collect log files for an adapter on a different collector. TVS Collector ID: 1; $adapterKind Collector ID: 2
    • The user should not encounter this error, The adapter instance to run the action on is selected by vROps and should always be the one on the same collector. Contact Support.
  • Collecting logs for $adapterKind is not supported.
    • The user should not encounter this error, if they do, TVS Manager has a bug and should be reported.
  • log file LOG_FILE does not exist on collector 1
    • The user should not encounter this error. If they do, that means that vrops did not create a log file for the adapter instance they're trying to collect from.