Is your feature request related to a problem?
The codebase uses logger.error in places where the situation isn't an actual error — for example, when a resource is simply not found.
This creates log noise and makes it harder to identify genuine errors.
if not credentials:
logger.error(f"No credentials found for project {project_id}")
Describe the solution you'd like
Define clear guidelines for log levels:
- error: Unexpected exceptions, failures, or situations where the system cannot proceed
- warning: Recoverable conditions, user-caused validation errors
- info: Expected conditions that are worth noting
- No log: Entirely expected behavior (e.g., resource legitimately doesn't exist)
Action items:
- Review all logger.error usages across the codebase
- Downgrade to warning, info, or remove based on context
- Document logging conventions for future development
Is your feature request related to a problem?
The codebase uses logger.error in places where the situation isn't an actual error — for example, when a resource is simply not found.
This creates log noise and makes it harder to identify genuine errors.
Describe the solution you'd like
Define clear guidelines for log levels:
- error: Unexpected exceptions, failures, or situations where the system cannot proceed
- warning: Recoverable conditions, user-caused validation errors
- info: Expected conditions that are worth noting
- No log: Entirely expected behavior (e.g., resource legitimately doesn't exist)
Action items: