Before a suite can score your data, it needs something to look at. Adding objects brings datasets into a Monitoring Suite, whether they come from an uploaded file or a connected application, and kicks off the profiling that later powers your quality rules.
Overview
Every dataset you want monitored — a table, a file, a view — is added to a suite as an "object." You start from the suite's Objects tab and select Add Objects, or, if the suite is brand new, you'll see the same option presented as Add Objects to Monitor on an empty screen. From there you choose how the data should come in, review what was detected, and let the suite profile it before you assign any evaluation rules.
Choosing how you add objects
When you select Add Objects, you're asked to pick a method:
Upload File — add a source directly as a CSV or XLS file. Each file you upload becomes its own object. If you're not sure how your file should be structured, use the Get Template link to download a sample CSV first.
Connect to Application — pull tables straight from a system you've already connected. You'll step through selecting the application, then the connection, then the specific objects you want monitored.
Connect a Data Catalog — intended to import a schema from a template library. This option is visible but not yet available to use.
Pick whichever method matches where your data actually lives — there's no need to export application data to a file just to upload it.
Reviewing objects before you save
After you choose your files or source objects, you land on the Review & Edit Objects screen. This is your chance to check the field properties the suite detected — names and data types — before the object is added for monitoring, and you can edit any of them inline.
If an object has a problem, it's flagged with an error pill telling you how many fields have errors. Resolve those before saving; a mapping with unresolved errors can't be stored correctly, so it's worth fixing field types here rather than after the fact.
What happens after you add objects
Once you save, profiling starts automatically in the background. Profiling suggests evaluation rules and generates a profiling report for each object by analyzing the actual data — field statistics, value distributions, and duplicates. You don't have to wait for it: you can keep working in the suite while it runs.
A progress indicator tracks how many of your new objects have been profiled. When it finishes, a banner summarizes what profiling found, letting you know how many evaluation rule suggestions are ready across your objects so you can review and assign them.
Understanding the objects table
Back on the Objects tab, each monitored dataset appears as a row showing its name, how many evaluation rules are assigned to it (and a link to add more), its total record count, its number of fields, and when its last record was ingested, with a refresh control to re-check ingestion status. Click any row to open a details drawer with the full field-level profile and rule assignments for that object.
Notes
Connect a Data Catalog is shown in the method picker but isn't enabled yet — use Upload File or Connect to Application instead.
An object with unresolved field errors on the review screen can't be saved correctly, so fix flagged fields before moving on.
Adding objects doesn't start scanning by itself. Scans run the evaluation rules assigned to each object, so an object with no rules assigned won't contribute anything to a scan.
Profiling runs in the background, so you can continue adding or reviewing other objects while it completes.