Developer Logs
Monitor API requests, MCP activity, and skill set executions across your workspace.
The Logs page gives admins a real-time view of every request hitting your workspace — API calls, MCP server traffic, and skill set executions — so you can debug integrations, spot errors, and keep an eye on usage.
Developer logs are available to admins and owners only.
Go to Settings → Developers → Logs.
Summary stats
Three cards at the top of the page give you a quick health check:
- Total Requests — Total number of requests in the current view
- Errors — How many requests failed, shown in red
- Success Rate — The percentage of successful requests, shown in green
Use these to spot issues at a glance before diving into the table below.
Filtering the log stream
You can combine any of the filters to zero in on exactly the requests you want.
Search
Type into the "Search logs by path..." box to filter by API endpoint.
Method
Filter by HTTP method:
- All Methods (default)
- GET, POST, PUT, DELETE
Status
Filter by HTTP response status. Common options include:
- 200 OK
- 201 Created
- 400 Bad Request
- 401 Unauthorized
- 403 Forbidden
- 404 Not Found
- 429 Rate Limited
- 500 Server Error
Source
Filter by where the request came from:
- API — Requests made with your API keys
- MCP — Calls from connected MCP servers
- Skillset — Executions from your skill sets
The logs table
Each row in the table represents a single request:
| Column | What it shows |
|---|---|
| Time | When the request happened |
| Method | HTTP method (colored for quick scanning) |
| Path | The API endpoint that was called |
| Status | HTTP status code (green for success, red for errors) |
| Duration | How long the request took, in milliseconds |
| IP | The IP address the request came from |
| Source | API, MCP, or Skillset |
Click the refresh icon to reload manually. The table also updates on its own in the background so you can watch activity as it happens.
Using logs to debug
- Start with errors. Filter by status codes in the 4xx and 5xx ranges to surface failed requests.
- Narrow by source. If a skill set isn't working, filter by Skillset to see exactly what's running and what's failing.
- Watch duration. A spike in duration usually points to something slow in a downstream system you're calling.
- Check the IP. Unexpected IPs on an API key are a red flag — rotate the key if anything looks off.
- Combine filters. For example, Source = API + Status = 401 quickly tells you if an integration is using the wrong key.
Related topics
- API Keys — Create and manage the keys showing up in these logs
- Skill Sets — Build the custom actions that show up under the "Skillset" source
- MCP Servers — Manage external tools Copilot uses