Set up Google Cloud Logging to send structured logs from your agents to Google Cloud for centralized log management. Before starting, complete the quickstart guide to have an agent running on Idun Agent Platform.Documentation Index
Fetch the complete documentation index at: https://docs.idunplatform.com/llms.txt
Use this file to discover all available pages before exploring further.
Set up GCP Logging observability
Prepare your Google Cloud project
- Create a Google Cloud project if you do not have one
- Enable the Cloud Logging API in your project
- Verify that the environment where your agent runs has credentials with permission to write logs (the
Logs Writerrole)
Create an observability configuration
- On the Idun Agent Platform main page, navigate to Observability
- Click Add configuration
- Select GCP Logging
- Enter a Configuration Name (for example, “GCP Logging Prod”)
- Fill in the required details:
- Project ID: Your Google Cloud Project ID
- Log Name: Identifier for the log stream (for example,
idun-agent-logs) - Resource Type: (Optional) For example,
globalorgce_instance - Severity: Minimum level to record (for example,
INFO,WARNING,ERROR) - Transport: Delivery method (default
BackgroundThread)
- Click Create configuration
Attach GCP Logging to your agent
- Navigate to the agent you want to add logging to
- Click Edit Agent
- Click Next to reach the observability configuration step
- Select GCP Logging as the observability provider
- Select the configuration you created
- Click Next
- Click Save changes to finalize
View log data
Once your agent is running with observability enabled:- Interact with your agent
- Open the Google Cloud Console
- Navigate to Logging > Logs Explorer
Best practices
- Use structured logging: The agent platform sends structured logs, which are easier to query in GCP
- Set appropriate severity: Filter out debug noise in production by setting severity to
INFOorWARNING
Troubleshooting
Logs not showing up?
- Check permissions: Verify the
Logs Writerrole is assigned to the agent’s service account - Check log name: Confirm you are filtering by the correct log name in Logs Explorer