Agent classification enrichment - #1822
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
documentation | 80a9a80 | Commit Preview URL Branch Preview URL |
Jun 10 2026, 09:55 AM |
Style & writing reviewThis PR is well-written and compliant with the style guide and One minor, optional item:
Using Nothing else material to flag. |
| <Tabs groupId="deployment" queryString> | ||
| <TabItem value="console" label="Console" default> | ||
|
|
||
| Configure the parameters in the Console enrichment editor. Keep the Console defaults for the `database` and `uri` fields. For example: |
There was a problem hiding this comment.
This pending console support.
|
|
||
| | Field | Type | Description | | ||
| | --- | --- | --- | | ||
| | `uri` | string | Base URI where the file is hosted. Supports `http:`, `s3:`, and `gs:` schemes. Must not end with a trailing slash. | |
There was a problem hiding this comment.
abfs also.
| "database": "<use default value from Console>" | ||
| }, | ||
| "classification": { | ||
| "MyInternalBot": {"operator": "Acme Corp", "purpose": "Monitoring"} |
There was a problem hiding this comment.
| "MyInternalBot": {"operator": "Acme Corp", "purpose": "Monitoring"} | |
| "SomeBot": {"operator": "Acme Corp", "purpose": "Monitoring"} |
That's a detail but IMO MyInternalBot could let people think that it is possible to add our own bot somewhere, whereas it is not possible as the value comes from YAUAA.
Nick (stanch)
added
the
do not merge
3 participants
What changed?
Why?
Reviewer guidance
AI reviews
Claude will automatically review this PR against the docs style guide.
If you have questions or want it to look again at something specific, tag
@claudein a comment.