We've reorganized our documentation navigation structure to align directly with your operational workflows. See the release notes and the walkthrough video for more information.

GetCollector parity mapping

Supported in:

Google secops SIEM

This guide details the request and response mapping specifications and property parity analysis for migrating from the legacy Backstory Ingestion Collector API (GetCollector) to the modern Chronicle API (GetCollector).

Protocol and mapping overview

Feature	Legacy API (`GetCollector`)	Modern Chronicle API (`GetCollector`)
HTTP method	`GET`	`GET`
Permissions	Partner token or legacy API keys	`chronicle.googleapis.com/collectors.get`

Request payload field-by-field parity

The modern Chronicle API GetCollectorRequest targets resources using Google Cloud resource name paths.

Legacy field (`GetCollectorRequest`)	Modern field (`GetCollectorRequest`)	Field type	Parity and migration notes
`name`	`name` (in HTTP path)	`string`	Google Cloud scoping context: Scopes the connection target using the standard resource path in the HTTP URL path. Pattern: `projects/{project}/locations/{location}/instances/{instance}/forwarders/{forwarder_id}/collectors/{collector_id}`.

Response payload field-by-field parity

Both APIs return the requested Collector representation.

Legacy field (`Collector` message)	Modern field (`Collector` message)	Field type	Parity and migration notes
`name`	`name`	`string`	Parity mapped: Contains the standard canonical resource path: `projects/{project}/locations/{location}/instances/{instance}/forwarders/{forwarder_id}/collectors/{collector_id}`.
`display_name`	`display_name`	`string`	Rename to `displayName` in JSON responses.
`config`	`config`	`CollectorConfig`	Contains equivalent log source and network settings.
`state`	`state`	`enum`	Maps directly to `State` enum (values: `ACTIVE`, `SUSPENDED`).
`type`	`type`	`enum`	Maps directly to `Type` enum (values: `FILE`, `KAFKA`, `PCAP`, `SPLUNK`, `WEBPROXY`, `SYSLOG`).
`override_timezone`	`override_timezone`	`bool`	Rename to `overrideTimezone` in JSON responses.
`time_zone`	`time_zone`	`string`	Rename to `timeZone` in JSON responses.

Key differences

Google Cloud project scoping integration:
- Scoped natively under parent project instance folder bindings.
Resource path renaming:
- Legacy path formats forwarders/<forwarder_id>/collectors/<collector_id> are migrated to standard Google Cloud path parameters projects/{project}/locations/{location}/instances/{instance}/forwarders/{forwarder_id}/collectors/{collector_id}.