Add support for additional metadata

Author: nyetwurk

Cargo.lock

@@ -2,7 +2,7 @@
 name = "solana-accountsdb-plugin-kafka"
 description = "Solana AccountsDb plugin for Kafka"
 authors = ["Blockdaemon"]
-version = "0.1.8+solana.3.0.0"
+version = "0.2.0+solana.3.0.0"
 edition = "2021"
 license = "Apache-2.0"
 repository = "https://github.com/Blockdaemon/solana-accountsdb-plugin-kafka"

Cargo.toml

@@ -122,3 +122,89 @@ The buffer size can be controlled using `librdkafka` config options, including:
 
 - `queue.buffering.max.messages`: Maximum number of messages allowed on the producer queue.
 - `queue.buffering.max.kbytes`: Maximum total message size sum allowed on the producer queue.
+
+## Enhanced Analytics Support
+
+The plugin now provides significantly richer analytics data for blockchain monitoring and analysis, enhancing all supported Solana transaction formats.
+
+### Transaction Types
+
+The plugin supports multiple Solana transaction formats:
+
+- **Legacy Transactions**: Traditional Solana message format
+- **V0 Transactions**: Versioned transactions with address lookup tables (LUTs)
+
+All transaction types are enhanced with comprehensive analytics metadata.
+
+### Enhanced Analytics Features
+
+All transactions provide additional analytics data that can be used for:
+
+#### Performance Monitoring
+- **Compute Units**: Actual compute units consumed by transactions
+- **Pricing Information**: Compute unit pricing from ComputeBudget instructions
+- **Cost Analysis**: Transaction fees and compute costs
+
+#### Error Analysis & Debugging
+- **Error Detection**: Reliable error status from transaction metadata
+- **Success Tracking**: Transaction success/failure status
+- **Error Details**: Structured error information without log parsing
+
+#### Address Intelligence
+- **Address Lookup Tables**: Support for V0 LUT transactions
+- **Loaded Address Details**: Index and writable status for loaded addresses
+- **Account Metadata**: Enhanced account information and versioning
+
+#### Slot & Network Analytics
+- **Confirmation Status**: Smart confirmation counting based on slot status
+- **Status Descriptions**: Human-readable slot status descriptions
+- **Progress Tracking**: Slot progression monitoring
+
+### Message Schema Enhancements
+
+The protobuf schema has been enhanced with analytics fields:
+
+#### UpdateAccountEvent
+- `data_version`: Account data version for change tracking
+- `is_startup`: Whether this is a startup account update
+- `account_age`: Approximate account age in slots
+
+#### SlotStatusEvent
+- `is_confirmed`: Whether slot is confirmed by supermajority
+- `confirmation_count`: Confirmation level (0-2 based on status)
+- `status_description`: Human-readable status description
+
+#### TransactionEvent
+- `compute_units_consumed`: Actual compute units used
+- `compute_units_price`: Compute unit pricing in micro-lamports
+- `total_cost`: Total transaction cost (fee + compute)
+- `instruction_count`: Number of instructions in transaction
+- `account_count`: Number of accounts involved
+- `execution_time_ns`: Execution time in nanoseconds
+- `is_successful`: Transaction success status
+- `execution_logs`: Detailed execution logs
+- `error_details`: Detailed error information
+- `confirmation_count`: Number of confirmations
+
+#### LoadedAddresses
+- `writable_info`: Detailed writable address information
+- `readonly_info`: Detailed readonly address information
+
+### Configuration for Analytics Features
+
+Analytics features are enabled by default and require no additional configuration. The plugin automatically:
+
+- Detects transaction format (Legacy or V0)
+- Extracts available metadata fields
+- Provides enhanced analytics where data is available
+- Maintains backwards compatibility with existing consumers
+
+### Use Cases
+
+Analytics enhancements enable new use cases:
+
+- **Performance Monitoring**: Track compute unit usage and costs
+- **Error Analysis**: Monitor transaction failures and success rates
+- **Network Analytics**: Analyze slot confirmation patterns
+- **Address Intelligence**: Monitor address lookup table usage
+- **Cost Optimization**: Analyze transaction pricing and efficiency

README.md

@@ -35,6 +35,11 @@ message UpdateAccountEvent {
 
   // First signature of the transaction caused this account modification
   optional bytes txn_signature = 9;
+
+  // Additional analytics fields
+  uint32 data_version = 10;                   // Account data version for change tracking
+  bool is_startup = 11;                       // Whether this is a startup account update
+  uint64 account_age = 12;                    // Account age in slots since creation
 }
 
 message SlotStatusEvent {
@@ -43,6 +48,11 @@ message SlotStatusEvent {
   uint64 parent = 2;
 
   SlotStatus status = 3;
+
+  // Additional analytics fields
+  bool is_confirmed = 4;                      // Whether slot is confirmed
+  uint32 confirmation_count = 5;              // Number of confirmations
+  string status_description = 6;              // Human-readable status description
 }
 
 enum SlotStatus {
@@ -81,6 +91,15 @@ message CompiledInstruction {
 message LoadedAddresses {
   repeated bytes writable = 1;
   repeated bytes readonly = 2;
+  repeated LoadedAddressInfo writable_info = 3;   // Detailed writable address information
+  repeated LoadedAddressInfo readonly_info = 4;   // Detailed readonly address information
+}
+
+// New message for detailed loaded address information
+message LoadedAddressInfo {
+  bytes address = 1;                           // Account address
+  uint32 index = 2;                            // Index in the loaded addresses list
+  bool is_writable = 3;                        // Whether account is writable
 }
 
 message MessageAddressTableLookup {
@@ -174,6 +193,10 @@ message TransactionStatusMeta {
   repeated TransactionTokenBalance pre_token_balances = 8;
   repeated TransactionTokenBalance post_token_balances = 9;
   repeated Reward rewards = 10;
+  uint32 compute_units_consumed = 11;        // Compute units used by transaction
+  uint64 compute_units_price = 12;           // Compute unit price in micro-lamports
+  repeated string error_logs = 13;           // Detailed error logs for debugging
+  bool is_successful = 14;                   // Transaction success status (inverse of is_status_err)
 }
 
 // based on solana_accountsdb_plugin_interface::accountsdb_plugin_interface::ReplicaTransactionInfo
@@ -184,6 +207,18 @@ message TransactionEvent {
   TransactionStatusMeta transaction_status_meta = 4;
   uint64 slot = 5;
   uint64 index = 6;
+
+  // Enhanced analytics fields
+  uint32 compute_units_consumed = 7;         // Compute units used by transaction
+  uint64 compute_units_price = 8;            // Compute unit price in micro-lamports
+  uint64 total_cost = 9;                     // Total transaction cost (fee + compute)
+  uint32 instruction_count = 10;             // Number of instructions in transaction
+  uint32 account_count = 11;                 // Number of accounts involved
+  uint64 execution_time_ns = 12;             // Execution time in nanoseconds
+  bool is_successful = 13;                   // Transaction success status
+  repeated string execution_logs = 14;        // Detailed execution logs
+  repeated string error_details = 15;         // Detailed error information
+  uint32 confirmation_count = 16;            // Number of confirmations
 }
 
 message MessageWrapper {