A VCF Operations tool that, given an object and a period, looks through related objects for possible evidence such as events, property changes and unusual metrics. Choosing TROUBLESHOOT on an alert opens it with that context.
Also called Observability Workbench.
Read more: Broadcom TechDocs
In the Ultra Transcenders books
Each book explains Troubleshooting Workbench in context, with comparison tables and the common traps.
Terms in this definition
- VCF Operations
VCF's console for running the fleet. It covers alerting, monitoring, capacity, reporting, log analysis and licensing alongside fleet management of identity, passwords, certificates and lifecycle.
- Chat message roles
Labels on chat messages: instructions go under system, the person's input under user, the model's previous answers under assistant, and results returned by a called tool under tool (or function).
- RELATED
Fetches a column value from the lookup table, that is the one side of a many-to-one relationship, for whichever row is being evaluated. It therefore needs to run inside an iterator or a calculated column, where row context exists.
- SEAT
Stats, events, alarms and tasks: the history stored in the vCenter database. Trends for SEAT, DB log and core space appear under Monitor > Database in the VAMI.
- property
In VCF Operations, an attribute describing how an object is configured, such as its vCPU count. Unlike a metric, it captures state rather than performance over time, and it can feed symptom definitions, views, dashboards and reports.
Related terms
- simple alert definition
Rather than building a full symptom-based alert in VCF Operations, you can start from one metric or property, such as those in Troubleshooting Workbench under Potential Evidence or Metrics, and make an alert definition straight away.