PuppyIP Resource Center
Cloud Operations 5 min Published 2026-11-18

Apigee Cloud EKM health monitoring: logs, alerts, and recovery checks

If your Apigee organization was created with Cloud EKM, you can find external key failures and set up alerts in Cloud Logging. Start by locating the affected organization and instance, then confirm recovery with an authorized operation that actually uses the key.

Apigee Cloud EKM Cloud Logging Log-based alerts

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

  • Google Cloud announced this feature on November 2, 2026, with a phased rollout. Check the actual environment for instance-level availability.
  • An error log identifies the affected organization and instance and deliberately omits the key name.
  • Apigee logs a persistent unreachable-key error about once an hour. After an alert closes automatically, confirm that a key-dependent operation works again.

Which Apigee organizations qualify?

This monitoring applies to managed Apigee, also known as Apigee X, when the organization was created with customer-managed encryption keys (CMEK) backed by Cloud EKM. Cloud EKM makes encryption operations depend on an external key manager. Apigee hybrid is outside this feature’s scope, and an existing organization created without EKM cannot enable it later.

Google Cloud listed the feature in its November 2, 2026 release notes. It said the rollout across Google Cloud zones could take four or more business days. Check how your organization was provisioned and inspect the current environment. The announcement date alone cannot confirm that a particular instance has received the update.

Where do you find the error logs?

In Google Cloud’s Logs Explorer, select a project where you can read the relevant Apigee logs. Enter the documented search text Apigee EKM key health issue detected in the query editor and run it. Start with a time range around the beginning of the incident and inspect the timestamps and states in the results.

Entries cover conditions such as denied access, a disabled key, disabled billing, or an unreachable key. Record the organization and instance and match them to your resource inventory. The log deliberately omits the key name. If you need to identify the key, use your team’s authorized configuration records.

How do you set up and interpret the alert?

Create a log-based alert policy in Cloud Logging and reuse the same query filter to match EKM failures. Route notifications to the team on call for that environment. Before saving, check the filter against existing sanitized logs, then review the notification channels, notification interval, and automatic closure settings.

While a key remains unreachable, Apigee writes an error roughly once an hour. Suppose the same instance shows the same error at 02:10 and 03:10. Correlate those entries with the original incident and check whether it is ongoing before opening a separate ticket. The logging interval does not guarantee how often your key is checked or when a notification arrives.

How do you confirm recovery after an alert closes?

When the key becomes reachable again, Apigee emits no separate recovery log or notification. Once matching errors stop, the log-based alert follows its automatic closure settings. The on-call record can track the last error, the alert closure, and the successful verification separately.

Ask the external key team to confirm reachability, then follow your change process to run an operation that actually requires the relevant key. Google gives deploying an API proxy as an example. Prefer a qualifying non-production environment and verify the operation uses the key you need to check. If only production can cover that key, arrange a check your team has authorized. A successful general health check is insufficient evidence for the encryption path.

When should you investigate the external key service?

Apigee logs show the connection or key-status issue it observed. For a network issue or a problem on the external key manager’s side, the responsible team should use its existing access to check configuration, connectivity, and service status.

In the handoff, include the time range, affected organization and instance, error status, and relevant recent changes. Mark recovery verified once the key-dependent operation succeeds. This preserves evidence and helps distinguish the effects on separate instances during a shared incident.

Sources

Frequently Asked Questions

Do empty EKM query results confirm that the key has stayed available?

Empty results alone cannot confirm availability. Check organization eligibility, project, read permissions, and time range first. When you need to establish current availability, use an approved operation that actually depends on the key.

What if several Apigee instances in the same project alert?

Group entries by organization, instance, and time, then check whether they point to a shared external dependency. Keep each instance’s verification result so a success on one instance doesn’t get recorded as project-wide recovery.