Merged
Conversation
…nterval) Addresses member feedback about unexpected automated traffic to agent endpoints. Adds proper User-Agent identification, an outbound request log visible to agent owners, and controls to pause or adjust check frequency. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…lient@4.22.0 Now that @adcp/client supports userAgent in PropertyCrawlerConfig and TestOptions (adcp-client#427), pass AAO-Discovery and AAO-ComplianceCheck User-Agent strings through the remaining two outbound paths. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Rename "Pause monitoring" to "Pause automated checks" - Disable and dim interval dropdown when paused - Show inline warning when paused: "Compliance status will not update" - Use design tokens for select padding/border-radius - Add User-Agent column to request log table (shows short name, full UA on hover) - Increase default request log from 20 to 50 rows Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The pause toggle was only gating the compliance heartbeat (getAgentsDueForCheck). The property crawler and capability probe ran against all agents regardless. Now both filter out paused agents. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Reject non-integer interval_hours (e.g. 6.7, Infinity) - Log warning when getPausedAgentUrls query fails - escapeHtml on data.total in request log panel Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Migration 376 was taken on main by admin_accounts_perf_indexes. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
bokelley
force-pushed
the
bokelley/optional-agent-fields
branch
from
e6df627 to
98646ef
Compare
Previous lock file was missing platform-specific transitive deps (e.g. @emnapi/core for sharp on Linux) that npm ci requires on CI. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
User-Agentheaders (e.g.AAO-HealthCheck/1.0,AAO-Discovery/1.0,AAO-ComplianceCheck/1.0) to all automated outbound requests to agent endpointsagent_outbound_requeststable) so agent owners can see what AAO is hitting their endpoints withPrompted by member feedback (Jeff Mahoney / Equativ) about unexpected high-volume automated traffic to their agent endpoint.
Follow-up needed:
PropertyCrawlerandcomply()in@adcp/clientdon't acceptuserAgentconfig yet — separate PR against adcp-client.Test plan
PUT /api/registry/agents/{url}/monitoring/pausePUT /api/registry/agents/{url}/monitoring/interval🤖 Generated with Claude Code