---
title: Getting Started with Datadog
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: Docs > Infrastructure > Datadog Resource Catalog
---

# gcp_blockchainnodeengine_blockchain_node{% #gcp_blockchainnodeengine_blockchain_node %}

## `ancestors`{% #ancestors %}

**Type**: `UNORDERED_LIST_STRING`

## `blockchain_type`{% #blockchain_type %}

**Type**: `STRING`**Provider name**: `blockchainType`**Description**: Immutable. The blockchain type of the node.**Possible values**:

- `BLOCKCHAIN_TYPE_UNSPECIFIED` - Blockchain type has not been specified, but should be.
- `ETHEREUM` - The blockchain type is Ethereum.

## `connection_info`{% #connection_info %}

**Type**: `STRUCT`**Provider name**: `connectionInfo`**Description**: Output only. The connection information used to interact with a blockchain node.

- `endpoint_info`**Type**: `STRUCT`**Provider name**: `endpointInfo`**Description**: Output only. The endpoint information through which to interact with a blockchain node.
  - `json_rpc_api_endpoint`**Type**: `STRING`**Provider name**: `jsonRpcApiEndpoint`**Description**: Output only. The assigned URL for the node JSON-RPC API endpoint.
  - `websockets_api_endpoint`**Type**: `STRING`**Provider name**: `websocketsApiEndpoint`**Description**: Output only. The assigned URL for the node WebSockets API endpoint.
- `service_attachment`**Type**: `STRING`**Provider name**: `serviceAttachment`**Description**: Output only. A service attachment that exposes a node, and has the following format: projects/{project}/regions/{region}/serviceAttachments/{service_attachment_name}

## `create_time`{% #create_time %}

**Type**: `TIMESTAMP`**Provider name**: `createTime`**Description**: Output only. The timestamp at which the blockchain node was first created.

## `ethereum_details`{% #ethereum_details %}

**Type**: `STRUCT`**Provider name**: `ethereumDetails`**Description**: Ethereum-specific blockchain node details.

- `additional_endpoints`**Type**: `STRUCT`**Provider name**: `additionalEndpoints`**Description**: Output only. Ethereum-specific endpoint information.
  - `beacon_api_endpoint`**Type**: `STRING`**Provider name**: `beaconApiEndpoint`**Description**: Output only. The assigned URL for the node's Beacon API endpoint.
  - `beacon_prometheus_metrics_api_endpoint`**Type**: `STRING`**Provider name**: `beaconPrometheusMetricsApiEndpoint`**Description**: Output only. The assigned URL for the node's Beacon Prometheus metrics endpoint. See [Prometheus Metrics](https://lighthouse-book.sigmaprime.io/advanced_metrics.html) for more details.
  - `execution_client_prometheus_metrics_api_endpoint`**Type**: `STRING`**Provider name**: `executionClientPrometheusMetricsApiEndpoint`**Description**: Output only. The assigned URL for the node's execution client's Prometheus metrics endpoint.
- `api_enable_admin`**Type**: `BOOLEAN`**Provider name**: `apiEnableAdmin`**Description**: Immutable. Enables JSON-RPC access to functions in the `admin` namespace. Defaults to `false`.
- `api_enable_debug`**Type**: `BOOLEAN`**Provider name**: `apiEnableDebug`**Description**: Immutable. Enables JSON-RPC access to functions in the `debug` namespace. Defaults to `false`.
- `consensus_client`**Type**: `STRING`**Provider name**: `consensusClient`**Description**: Immutable. The consensus client.**Possible values**:
  - `CONSENSUS_CLIENT_UNSPECIFIED` - Consensus client has not been specified, but should be.
  - `LIGHTHOUSE` - Consensus client implementation written in Rust, maintained by Sigma Prime. See [Lighthouse - Sigma Prime](https://lighthouse.sigmaprime.io/) for details.
  - `ERIGON_EMBEDDED_CONSENSUS_LAYER` - Erigon's embedded consensus client embedded in the execution client. Note this option is not currently available when creating new blockchain nodes. See [Erigon on GitHub](https://github.com/ledgerwatch/erigon#embedded-consensus-layer) for details.
- `execution_client`**Type**: `STRING`**Provider name**: `executionClient`**Description**: Immutable. The execution client**Possible values**:
  - `EXECUTION_CLIENT_UNSPECIFIED` - Execution client has not been specified, but should be.
  - `GETH` - Official Go implementation of the Ethereum protocol. See [go-ethereum](https://geth.ethereum.org/) for details.
  - `ERIGON` - An implementation of Ethereum (execution client), on the efficiency frontier, written in Go. See [Erigon on GitHub](https://github.com/ledgerwatch/erigon) for details.
- `geth_details`**Type**: `STRUCT`**Provider name**: `gethDetails`**Description**: Details for the Geth execution client.
  - `garbage_collection_mode`**Type**: `STRING`**Provider name**: `garbageCollectionMode`**Description**: Immutable. Blockchain garbage collection mode.**Possible values**:
    - `GARBAGE_COLLECTION_MODE_UNSPECIFIED` - The garbage collection has not been specified.
    - `FULL` - Configures Geth's garbage collection so that older data not needed for a full node is deleted. This is the default mode when creating a full node.
    - `ARCHIVE` - Configures Geth's garbage collection so that old data is never deleted. This is the default mode when creating an archive node. This value can also be chosen when creating a full node in order to create a partial/recent archive node. See [Sync modes](https://geth.ethereum.org/docs/fundamentals/sync-modes) for more details.
- `network`**Type**: `STRING`**Provider name**: `network`**Description**: Immutable. The Ethereum environment being accessed.**Possible values**:
  - `NETWORK_UNSPECIFIED` - The network has not been specified, but should be.
  - `MAINNET` - The Ethereum Mainnet.
  - `TESTNET_GOERLI_PRATER` - Deprecated: The Ethereum Testnet based on Goerli protocol. Please use another test network.
  - `TESTNET_SEPOLIA` - The Ethereum Testnet based on Sepolia/Bepolia protocol. See [https://github.com/eth-clients/sepolia](https://github.com/eth-clients/sepolia).
  - `TESTNET_HOLESKY` - The Ethereum Testnet based on Holesky specification. See [https://github.com/eth-clients/holesky](https://github.com/eth-clients/holesky).
- `node_type`**Type**: `STRING`**Provider name**: `nodeType`**Description**: Immutable. The type of Ethereum node.**Possible values**:
  - `NODE_TYPE_UNSPECIFIED` - Node type has not been specified, but should be.
  - `LIGHT` - An Ethereum node that only downloads Ethereum block headers.
  - `FULL` - Keeps a complete copy of the blockchain data, and contributes to the network by receiving, validating, and forwarding transactions.
  - `ARCHIVE` - Holds the same data as full node as well as all of the blockchain's history state data dating back to the Genesis Block.
- `validator_config`**Type**: `STRUCT`**Provider name**: `validatorConfig`**Description**: Configuration for validator-related parameters on the beacon client, and for any GCP-managed validator client.
  - `beacon_fee_recipient`**Type**: `STRING`**Provider name**: `beaconFeeRecipient`**Description**: An Ethereum address which the beacon client will send fee rewards to if no recipient is configured in the validator client. See [https://lighthouse-book.sigmaprime.io/suggested-fee-recipient.html](https://lighthouse-book.sigmaprime.io/suggested-fee-recipient.html) or [https://docs.prylabs.network/docs/execution-node/fee-recipient](https://docs.prylabs.network/docs/execution-node/fee-recipient) for examples of how this is used. Note that while this is often described as "suggested", as we run the execution node we can trust the execution node, and therefore this is considered enforced.
  - `managed_validator_client`**Type**: `BOOLEAN`**Provider name**: `managedValidatorClient`**Description**: Immutable. When true, deploys a GCP-managed validator client alongside the beacon client.
  - `mev_relay_urls`**Type**: `UNORDERED_LIST_STRING`**Provider name**: `mevRelayUrls`**Description**: URLs for MEV-relay services to use for block building. When set, a GCP-managed MEV-boost service is configured on the beacon client.

## `labels`{% #labels %}

**Type**: `UNORDERED_LIST_STRING`

## `name`{% #name %}

**Type**: `STRING`**Provider name**: `name`**Description**: Output only. The fully qualified name of the blockchain node. e.g. `projects/my-project/locations/us-central1/blockchainNodes/my-node`.

## `organization_id`{% #organization_id %}

**Type**: `STRING`

## `parent`{% #parent %}

**Type**: `STRING`

## `private_service_connect_enabled`{% #private_service_connect_enabled %}

**Type**: `BOOLEAN`**Provider name**: `privateServiceConnectEnabled`**Description**: Optional. When true, the node is only accessible via Private Service Connect; no public endpoints are exposed. Otherwise, the node is only accessible via public endpoints. Warning: These nodes are deprecated, please use public endpoints instead.

## `project_id`{% #project_id %}

**Type**: `STRING`

## `project_number`{% #project_number %}

**Type**: `STRING`

## `region_id`{% #region_id %}

**Type**: `STRING`

## `resource_name`{% #resource_name %}

**Type**: `STRING`

## `state`{% #state %}

**Type**: `STRING`**Provider name**: `state`**Description**: Output only. A status representing the state of the node.**Possible values**:

- `STATE_UNSPECIFIED` - The state has not been specified.
- `CREATING` - The node has been requested and is in the process of being created.
- `DELETING` - The existing node is undergoing deletion, but is not yet finished.
- `RUNNING` - The node is running and ready for use.
- `ERROR` - The node is in an unexpected or errored state.
- `UPDATING` - The node is currently being updated.
- `REPAIRING` - The node is currently being repaired.
- `RECONCILING` - The node is currently being reconciled.
- `SYNCING` - The node is syncing, which is the process by which it obtains the latest block and current global state.

## `tags`{% #tags %}

**Type**: `UNORDERED_LIST_STRING`

## `update_time`{% #update_time %}

**Type**: `TIMESTAMP`**Provider name**: `updateTime`**Description**: Output only. The timestamp at which the blockchain node was last updated.

## `zone_id`{% #zone_id %}

**Type**: `STRING`