You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs/reference/filebeat/filebeat-input-entity-analytics.md has a user-facing API endpoint inconsistency introduced in commit c76211f2ff09e2dfe4b8fec45996b0ed65821655.
Evidence:
Current docs (lines 968-970, blamed to c76211f2ff0):
x-pack/filebeat/input/entityanalytics/provider/okta/okta_test.go:164 also targets /api/v1/iam/roles/{roleId}/permissions
Why this is UX drift:
Nearby endpoint bullets in this same section list exact API paths being called (/api/v1/users, /api/v1/devices).
The new bullet switched to a broader path (/api/v1/iam/roles) while describing permissions enrichment, which is inconsistent with actual behavior and can mislead users configuring scopes/troubleshooting calls.
Suggested consolidation:
Update that bullet to [/api/v1/iam/roles/{roleId}/permissions](...) and keep the same endpoint-specific style as adjacent bullets.
(Optional wording polish) It also reads role permissions... for grammar clarity.
Note
🔒 Integrity filtering filtered 123 items
Integrity filtering activated and filtered the following items during workflow execution.
This happens when a tool call accesses a resource that does not meet the required integrity or secrecy level of the workflow.
#49658 (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
#49163 (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
#49099 (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
#39761 (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
#44780 (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
#39352 (search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
#49851 (search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
#49850 (search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
#49849 (search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
#49511 (search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
#49796 (search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
#49848 (search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
#49699 (search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
#49701 (search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
#49700 (search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
#49518 (search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)
docs/reference/filebeat/filebeat-input-entity-analytics.mdhas a user-facing API endpoint inconsistency introduced in commitc76211f2ff09e2dfe4b8fec45996b0ed65821655.Evidence:
c76211f2ff0):x-pack/filebeat/input/entityanalytics/provider/okta/internal/okta/okta.go:347const endpoint = "/api/v1/iam/roles/{roleId}/permissions"x-pack/filebeat/input/entityanalytics/provider/okta/okta_test.go:164also targets/api/v1/iam/roles/{roleId}/permissionsWhy this is UX drift:
/api/v1/users,/api/v1/devices)./api/v1/iam/roles) while describing permissions enrichment, which is inconsistent with actual behavior and can mislead users configuring scopes/troubleshooting calls.Suggested consolidation:
[/api/v1/iam/roles/{roleId}/permissions](...)and keep the same endpoint-specific style as adjacent bullets.It also reads role permissions...for grammar clarity.Note
🔒 Integrity filtering filtered 123 items
Integrity filtering activated and filtered the following items during workflow execution.
This happens when a tool call accesses a resource that does not meet the required integrity or secrecy level of the workflow.
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".)What is this? | From workflow: UX Design Patrol
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.