5.8.5
Table Of Contents
- VMware vCenter Operations Manager Administration Guide
- Contents
- VMware vCenter Operations Manager Administration Guide
- Configuring and Managing vCenter Operations Manager
- Configuring Adapters
- Configuring Resources
- Configuring Attribute Packages
- Configuring Applications
- Configuring and Managing Users
- Configuring Alert Notifications
- Performing Basic System Administration Tasks
- View Performance Information
- View Status Information
- vCenter Operations Manager Service Names
- Start or Stop vCenter Operations Manager Services
- Viewing and Managing System Log Files
- Delete Old Data in the File System Database
- Run the Audit Report
- Modify Global Settings
- Modify Global Settings for Virtual Environments
- Create a Support Bundle
- Resolving Administrative System Alerts
- Analytics FSDB Overloaded
- Analytics Threshold Checking Overloaded
- Collector Is Down
- Controller Is Unable to Connect to MQ
- DataQueue Is Filling Up
- Describe Failed
- Failed to Connect to Replication MQ
- Failed to Repair Corrupted FSDB Files
- File Queue Is Full
- FSDB Files Corrupted for Resources
- FSDB Storage Drive Free Space Is Less Than 10%
- No DT Processors Connected
- One or More Resources Were Not Started
- Outbound Alert Send Failed
- Replication MQ Sender Is Blocked
- Backing Up and Recovering Data
- Backing Up and Recovering Data Components
- Backing Up and Recovering Processing Components
- Configuring the Repository Adapter
- Repository Adapter Requirements and Limitations
- Repository Adapter Configuration Steps
- Creating a Database User for the Repository Adapter
- Configure the Source Database Connection for the Repository Adapter
- Configure the Output Destination for the Repository Adapter
- Configuring the Source and Destination Columns for the Repository Adapter
- Configure Data Export Values for the Repository Adapter
- Customizing Repository Adapter Operation
- Start the Repository Adapter
- Using System Tools
- Using the Database Command Line Interface
- Index
The following supermetric configure command checks the super metric named SM1 for collection in the
super metric package named package1. It creates two thresholds and marks HT from level critical and DT
above and DT below as KPIs violations.
dbcli.sh supermetric configure "SM1" --packages "package1" --check true --ht true --
htcriticality critical --dtabove true --dtbelow true --thresholds "critical,>=,
90,2,3;immediate,=,70,3,3"
Export a Super Metric
You can use the dbcli supermetric export command to export a super metric from a
vCenter Operations Manager instance. When you export a super metric, vCenter Operations Manager
creates a super metric file in XML format.
The supermetric export command has the following syntax.
supermetric export "supermetric-name" [output-dir]
supermetric-name
Name of the super metric to export. If the named super metric does not exist,
the command does not export a super metric file. If multiple super metrics
exist that have the same name, the command exports only one of the super
metrics.
output-dir
Name of the directory where the command exports the super metric file. If
you do not provide an output directory name, the command exports the
super metric file to the current directory.
The following supermetric export command exports a super metric named SM1 to the SM1.xml file in the
supermetrics directory.
dbcli.sh supermetric export "SM1" supermetrics
Import a Super Metric
You can use the dbcli supermetric import command to import a super metric that you exported from
another instance of vCenter Operations Manager.
supermetric import "input-file" [--force] [--packages {all | "package-name[,package-name]..."}]
[--check {true | false} ] [--retry maxRetryMinutes] [--create]
input-file is the name of the a previously exported super metric file. If the super metric file does not exist, the
command fails.
The supermetric import command has certain options.
Table 13‑6. supermetric import Command Options
Option Description
--force
Use this option to import the super metric even if a super metric
that has the same name already exists on the target system.
NOTE This option can cause the command to create a duplicate
super metric on the target system.
--packages {all | "package-name[,package-
name]..."}
List of super metric packages to which to apply the import
operation. To apply the import operation to all super metric
packages, type all instead of individual super metric package
names.
--check {true | false}
Checks or unchecks the super metric for collection in the
specified packages.
Chapter 13 Using the Database Command Line Interface
VMware, Inc. 165