Browse files and investigate logs
Use the client file browser and log explorer for targeted investigation. Both operate on an enrolled client and reflect its capabilities and your current permissions.
Browse files
Section titled “Browse files”- Open Clients, find the intended computer and select its file-browser action.
- Enter the Remote path or open a listed folder. Use Up to return to its parent.
- Filter the current directory by name. Open a file to inspect it, or choose Download.
- Use Upload or New folder when your access allows it. The delete-folder action applies to empty folders.
Directory listings show immediate entries, not a recursive scan or calculated folder sizes. Creation and modification times can be missing when a platform or older client does not report them.
The read, write and delete permissions are independent. Tooling additionally requires a matching operation policy and permitted path root.
Browse through the CLI
Section titled “Browse through the CLI”After connecting the CLI, substitute your discovered IDs and an approved path:
netratel files-v2 browse --tenant-id 7 --agent-id "$AGENT_ID" \ --path /var/log --page-size 50When the response includes nextCursor, repeat the command with that value as --cursor. Keep the identity, target, path and page size unchanged. A stale or expired cursor means start again without it.
File mutations have separate preview and confirmation commands. Use the operation’s --help for its exact plan-token and idempotency-key arguments.
Inspect logs
Section titled “Inspect logs”Open a client’s Logs action and select an available Source. Choose Log history to investigate a past event, or Live logs to follow new records.
Expand filters to search text, severity and category. Sources that support them also offer provider, event ID and UTC time filters. Apply a narrow time range around the event, then load older records if needed.
Check the displayed stream state and any dropped-record or resynchronisation message before concluding a history is complete. Clearing displayed records only clears the view. For MCP investigations, discover available log sources first and retain the returned cursor when paging.