Runtime logs
Use the runtime logs to help diagnose problems with theapigee-runtime pods. Each runtime pod contains a message processor, which is responsible for processing API proxy traffic, executing policies, routing requests, and more.
Using runtime logs
Logs are a good way to troubleshoot problems with your installation. SeeLogging for details.
Use the logs command
You can view runtime system logs using thekubectl logs command. For example:
kubectl logs -f -n apigee apigee-runtime-apigee-gcp-prod1-test-blue-hd77q
Contract version information
The following table briefly describes log entries related to loading the contract from the management plane:
| Log Entry | Meaning |
hybrid-runtime Apigee-Timer-9 INFO RUNTIME-SYNC-SERVICE - RuntimeSyncServiceImpl.updateToVersion() : Switched to newer version 750 from version null | The MP changed to a newer version of the configuration contract. |
hybrid-runtime Apigee-Timer-6 INFO RUNTIME-SYNC-SERVICE - RuntimeSyncServiceImpl.loadLatestVersionIfAvailable() : Found a newer version 750 | The MP loaded the latest contract configuration version fromversion.properties. |
hybrid-runtime Apigee-Timer-6 INFO RUNTIME-SYNC-SERVICE - RuntimeSyncServiceImpl.updateToVersion() : Attempting to update to a newer version 750 | The MP is updating to a newer version of the configuration contract. |
hybrid-runtime Apigee-Timer-6 INFO RUNTIME-SYNC-SERVICE - RuntimeSyncServiceImpl.updateToVersion() : Switched to newer version 751 from version 750 | The MP loaded the latest contract configuration version fromversion.properties. |
Deployment errors
The following runtime errors relate to proxy deployments:
| Log Entry | Meaning |
hybrid-runtime org:hybrid env:prod Apigee-Main-6 ERROR i.a.h.e.i.HermesEngineImpl - HermesEngineImpl.handleHermesException() : Keyspace cache_hybrid_hybrid does not exist | Keyspacecache_orgname_hybrid is not provisioned in Cassandra. |
hybrid-runtime org:hybrid Apigee-Timer-9 ERROR c.a.s.e.k.HybridEncryptionKeyServiceImpl - HybridEncryptionKeyServiceImpl.getEncryptionKey() : Encryption key does not exist for organization hybrid and type KmsKey | Keyspacekms_orgname_hybrid is not provisioned in Cassandra. |
Message processor deployment error logs
Look for the following deployment error entries in the message processor logs:
| Log entry | Description |
|---|---|
hybrid-runtime org:hybrid env:prod Apigee-Main-6 ERROR i.a.h.e.i.HermesEngineImpl - HermesEngineImpl.handleHermesException() : Keyspace cache_hybrid_hybrid does not exist | Keyspacecache_orgname_hybrid is not provisioned in Cassandra. |
hybrid-runtime org:hybrid Apigee-Timer-9 ERROR c.a.s.e.k.HybridEncryptionKeyServiceImpl - HybridEncryptionKeyS erviceImpl.getEncryptionKey() : Encryption key does not exist for organization hybrid and type KmsKey | Keyspacekms_orgname_hybrid is not provisioned in Cassandra. |
Message processor error codes
Error codes for the message processor start withruntime.sync.error-name. For example:
| Log Entry | Meaning |
runtime.sync.ContractLoadFailedMessage: Error loading spec file | Reason: The error could be caused by an invalid schema, corrupted contract specification file, or invalid contract. Any of these issues could prevent the message processor from loading the spec file. Remedy: Make sure either the contract specification file is available, the file system is not corrupted, or the schema/contract is valid. |
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2026-02-18 UTC.