Container Attributes

Totals

1 Quality Score: This represents the overall health of the data based on various checks. A higher score indicates better data quality and fewer issues detected.

2 Sampling: Displays the percentage of data sampled during profiling. A 100% sampling rate means the entire dataset was analyzed for the quality report.

3 Completeness: The average completeness of the profiled fields, where a field's completeness is the share of sampled records in which it has a value. A lower percentage means one or more fields are frequently empty.

4 Records: Shows the total number of records in the container as measured by the latest profile, not the sampled subset.

5 Fields Profiled: This shows the number of fields or attributes within the dataset that have undergone data profiling, which helps identify potential data issues in specific columns.

6 Active Checks: Represents the number of ongoing checks applied to the dataset. These checks monitor data quality, consistency, and correctness.

7 Active Anomalies: The number of anomalies that are still active on this container. Anomalies come from scan operations, so the card stays empty until the container has been scanned. Anomalies that have been acknowledged or archived are not counted here. The card label follows the count, so it reads Active Anomaly when there is only one.

Observability

1 Data Volume Over Time

This chart plots the container's record count at each measurement, so you can see how the data grows or shrinks over time and spot a sudden jump or drop that deserves a closer look. It measures rows, not stored size.

2 Anomalies Over Time

This chart helps users track any unusual data patterns or issues within the container. It shows a visual representation of when anomalies occurred over a specific time period, making it easy to spot unusual activity. This allows users to quickly identify when something might have gone wrong and take action to fix it, ensuring the data stays accurate and reliable.

Timeline

The Timeline section displays a detailed, chronological log of all configuration changes. It provides complete visibility into what was modified, who made the update, and when the action occurred. Click Show more at the bottom of the list to load older changes.

Ownership changes on a computed asset are recorded here alongside the other configuration changes. The entry names the previous and new owner, so a transfer is auditable in the same timeline as edits to the definition, the description, or the tags.

Reviewing a Change

Short values are shown inline on the entry, reading from <previous value> to <new value>. A long change collapses behind a View changes control instead, so it never floods the Timeline: this happens when the two values together run past roughly 170 characters, or when either one contains a line break. The control reports the before and after lengths (for example, 32 → 166 chars) and expands into a panel with the From and To values. Any field can collapse this way, a rewritten description as much as a tag list. On a computed container, the query and clause fields are the exception: they always collapse behind the control, however short the change is. When one save changes several properties at once, they are grouped into a single entry rather than split into separate rows.

SQL changes get a richer view. For the Query of a Computed Table, the Select Clause, Where Clause, or Group By Clause of a Computed File or a two-source Computed Join, and the Query of a Computed Join built in SQL mode, View changes opens the two versions side by side, aligned line for line and sharing a single scrollbar, with the changed lines highlighted and a copy button on each side. See Computed Table Query Diff, Computed File Query Diff, or Computed Join Query Diff.

The dialog is titled after the field that changed, so a Computed File's filter opens as Where Clause Changes even though the edit form labels that input Filter Clause.

Commenting on the Timeline

You can discuss changes directly on the Timeline, which is what keeps the reason for a change next to the change itself:

• Comment on the container. Use the comment box above the Timeline, with the placeholder "Leave a comment (use @ to mention users)". The comment takes its own place in the Timeline, in chronological order.
• Comment on a specific change. Click the Comment control below a change entry. The comment stays attached to that entry, and once an entry has comments they collapse into a pill showing the author avatars, the comment count, and when the last comment was posted.
• Reply to a comment. Click the Reply control below a comment. Threads are one level deep, so you reply to a comment, not to a reply.
• Mention a teammate. Type @ and pick a user from the list. They receive an in-app Mention notification that opens this page, expands the thread, and highlights the comment, even when it sits further back in the Timeline.

Comment authors can edit and delete their own comments from the options menu on the comment; users with the Admin role can delete anyone's comment, and nobody can edit someone else's. Deleting a comment that already has replies leaves a placeholder reading This comment was deleted so the replies stay visible.