Jobs created under Automation Central which contain property-based filters ( Custom Tag ) are not working in Aria Operations

Products

• VMware Aria Suite

Issue/Introduction

When a Job is created under Automation Central using property-based filters ( I'e Virtual Machine Custom Attributes / Custom Tag ) would get saved as metrics.


For Example:

• When creating a schedule job, set the filter criteria using the Custom Tag ( Properties -> Summary | Custom Tag - > Value ) and Save the Job

• Right after the save, job gets created. But the filter criteria parameters are immediately changed from 'Properties' to 'Metrics' ( Metrics -> Summary | Custom Tag - > Value )
  
  

Environment

VMware Aria Operations (formerly known as vRealize Operations) 8.16.X

VMware Aria Operations (formerly known as vRealize Operations) 8.17.X

Cause

This issue occurs when a job created in Automation Central using property-based filter ( Custom Tag ) are saved incorrectly in the database.

Resolution

This is a known issue with VMware Aria Operations (formerly known as vRealize Operations).There is currently no resolution.

To work around the issue, use vSphere Tags instead of custom attributes at vCenter Virtual Machine to unblock them.