Skip to main content
Solved

Chronicle API Migration Legacy Endpoints

  • Sep 22, 2026 6:06 PM UTC
  • 1 reply
  • 115 views

donkos
Forum|alt.badge.img+10

There’s a variety of endpoints listed in the Chronicle API documentation that still have “legacy” in the name. ​@SoarAndy in a post about five months mentioned that this just reflects the API call not being the Google structure yet. However, I am concerned that these endpoints are only usable using the v1alpha version, which Google documentation warns is not suitable for production as it could be changed unpredictably. With the migration deadline so close, I am concerned about being forced to switch existing use cases to use these unstable endpoints while knowing I have no choice.

 

Does the use of the v1alpha with these legacy endpoints truly mean that they are unstable and not fit for production?

Best answer by sukeerth

The v1alpha legacy name endpoints in Chronicle API are operationally stable and supported & safe for production workloads.

A few key points on what to expect:

  1. Operational reliability and API structure: These legacy name endpoints are not experimental features—they run on the exact same production infrastructure and Cloud IAM controls as v1, and power the Google SecOps UI today. They have legacy name because their payloads mirror the older API structure. We will not abruptly shut down a v1alpha endpoint without giving an appropriate 1 year notice per Google Cloud Deprecation.
  2. Why migrating to v1alpha makes sense: Most endpoints are already in v1 or v1beta—always use those first. If they are not available, you can use v1alpha.
View original

1 reply

sukeerth
Staff
Forum|alt.badge.img+2
  • Staff
  • Answer
  • Sep 24, 2026 8:13 PM UTC

The v1alpha legacy name endpoints in Chronicle API are operationally stable and supported & safe for production workloads.

A few key points on what to expect:

  1. Operational reliability and API structure: These legacy name endpoints are not experimental features—they run on the exact same production infrastructure and Cloud IAM controls as v1, and power the Google SecOps UI today. They have legacy name because their payloads mirror the older API structure. We will not abruptly shut down a v1alpha endpoint without giving an appropriate 1 year notice per Google Cloud Deprecation.
  2. Why migrating to v1alpha makes sense: Most endpoints are already in v1 or v1beta—always use those first. If they are not available, you can use v1alpha.