Home
VOV Subsystem Reference Guide
VOV Metrics
The Altair Accelerator allows users to collect arbitrary metrics, where a metric is defined as a "named time series" of values, where each value is either a floating point number or a string.
Using vovselect
You can also query the metrics using vovselect.

Welcome
What's New
View new features for VOV Subsystem 2025.1.0.
Overview
Discover the workspace, licensing and installation, and training.
VOV Subsystem Tutorials
Discover VOV Subsystem functionality with interactive tutorials.
VOV Subsystem Administrator Guide
This manual provides information about managing a VOV project, including starting the server and connecting computing resources such as computers and licenses.
VOV Subsystem Reference Guide
- Command Line Interface
- Fields, Selection Rules and Formatting Strings
- VOV Metrics
  The Altair Accelerator allows users to collect arbitrary metrics, where a metric is defined as a "named time series" of values, where each value is either a floating point number or a string.
  - Metrics Storage
    The metrics are primarily stored in the vovserver memory. You can choose how much RAM is to be used for the metrics using the parameter metrics.maxmem, which is a value in MB.
  - Metrics Naming
    The name of a metric determines the name of the file used to store the metric. Therefore, the name of a metric may include any character that is acceptable in a file name.
  - Built-in Server Metrics
  - VOV Metrics Command Line Interface
    The simplest way to manage metrics is with the utility vovmetric.
  - Using vovselect
    You can also query the metrics using vovselect.
  - Vtk Interface
    The low-level interface for metrics is with the vtk_metric family of procedures.
  - Plotting
    The vovconsole has some ability to plot metrics using the VovPlotMetrics procedure.
- Miscellaneous
- VOV Security Infrastructure
- REST Application Programming Interface
  Altair Accelerator supports a RESTful API that enables a developer to submit, monitor, and control batch jobs as well as query the batch scheduler queues, jobs, and hosts in useful ways.
- All About Tcl
- VTK Procedures
EDA Tool Integration Guide
This document is a collection of techniques that have proven to be useful when applying FlowTracer in Electronic Design Automation.

View All Altair Accelerator Help

Using vovselect

You can also query the metrics using vovselect.

% vovselect id,name from metrics
...this returns id and name of  all metrics
% vovselect id,name from metrics where name~/ram/
id      name
000113670       scheduler/ram/available
000113671       scheduler/ram/capacity
000113672       scheduler/ram/inuse

If you want to access a property of a wave (reminder: a property is computed from the metric name, which may consist of components of the form PROPERTY=VALUE), use the field 'PROP.<propertyName>' as in this example:

% vovselect id,name,prop.user from metrics where prop.site==US
000150881       site=US/user=john/res=abc/m     john
000150882       site=IN/user=john/res=abc/m     john

Run vovselect fieldname,fieldtype from <object> to see the list of fields for that object. Multiple fields may be requested by separating them with a comma. Some fields represent a data collection that can be broken down using a format of FIELD.X, such as:

KEY.<KEYNAME>       (metric objects)
PARAM.<PARAMNAME>   (server object)
PROP.<PROPNAME>     (all objects)
RESOURCES.<RESNAME> (tasker objects)

To find the fields that are accessible for metrics, you can use this command:

Usage: 'vovselect fieldname from
                metrics'

AGE
AGEPP
FAMILY
FIRSTTS
ID
IDINT
KEY
LASTACCESS
LASTDATA
LASTLABEL
LASTTS
LASTUPDATE
MEMORY
NAME
POINTS
PROP
PROPDUMP
PROPERTIES
ROWCOUNT
TAIL
UNITS