docs/en/administration/management/monitoring/metric_details/i-p.md
:::note
Metrics for materialized views and shared-data clusters are detailed in the corresponding sections:
For more information on how to build a monitoring service for your StarRocks cluster, see Monitor and Alert.
:::
iceberg_compaction_duration_ms_totalcompaction_type (manual or auto)iceberg_compaction_input_files_totalcompaction_type (manual or auto)iceberg_compaction_output_files_totalcompaction_type (manual or auto)iceberg_compaction_removed_delete_files_totalcompaction_type (manual or auto)iceberg_compaction_totalcompaction_type (manual or auto)rewrite_data_files) tasks.iceberg_delete_bytesdelete_type (position or metadata)DELETE tasks. For metadata delete, this represents the size of deleted data files. For position delete, this represents the size of position delete files created.iceberg_delete_duration_ms_totaldelete_type (position or metadata)DELETE tasks in milliseconds. The duration of each task is added after it ends. delete_type distinguishes between two delete methods.iceberg_delete_rowsdelete_type (position or metadata)DELETE tasks. For metadata delete, this represents the number of rows in deleted data files. For position delete, this represents the number of position deletes created.iceberg_delete_totalstatus (success or failed)reason (none, timeout, oom, access_denied, unknown)delete_type (position or metadata)DELETE tasks that target Iceberg tables. The metric is incremented by 1 after each task ends, regardless of success or failure. delete_type distinguishes between two delete methods: position (generates position delete files) and metadata (metadata-level delete).iceberg_metadata_table_query_totalmetadata_table (refs, history, metadata_log_entries, snapshots, manifests, files, partitions, or properties)metadata_table label that identifies the metadata table being accessed.iceberg_time_travel_query_totaltime_travel_type (branch, tag, snapshot, or timestamp) for the categorized series.snapshot means FOR VERSION AS OF <snapshot_id>, branch and tag mean FOR VERSION AS OF <reference_name>, and timestamp means FOR TIMESTAMP AS OF ....iceberg_write_byteswrite_type (insert, overwrite, or ctas)INSERT, INSERT OVERWRITE, CTAS). This represents the total size of data files written to the Iceberg table. write_type distinguishes between the operation types.iceberg_write_duration_ms_totalwrite_type (insert, overwrite, or ctas)INSERT, INSERT OVERWRITE, CTAS) in milliseconds. The duration of each task is added after it ends. write_type distinguishes between the operation types.iceberg_write_fileswrite_type (insert, overwrite, or ctas)INSERT, INSERT OVERWRITE, CTAS). This represents the count of data files written to the Iceberg table. write_type distinguishes between the operation types.iceberg_write_rowswrite_type (insert, overwrite, or ctas)INSERT, INSERT OVERWRITE, CTAS). This represents the number of rows written to the Iceberg table. write_type distinguishes between the operation types.iceberg_write_totalstatus (success or failed)reason (none, timeout, oom, access_denied, unknown)write_type (insert, overwrite, or ctas)INSERT, INSERT OVERWRITE, or CTAS tasks that target Iceberg tables. The metric is incremented by 1 after each task ends, regardless of success or failure. write_type distinguishes between the operation types.int128_column_pool_bytesint16_column_pool_bytesint32_column_pool_bytesint64_column_pool_bytesint8_column_pool_bytesjemalloc_active_bytesjemalloc_allocated_bytesjemalloc_mapped_bytesjemalloc_metadata_bytesjemalloc_metadata_thpjemalloc_resident_bytesjemalloc_retained_bytesjit_cache_mem_bytesload_bytesload_channel_countload_mem_bytesload_rowsload_rpc_threadpool_sizelocal_column_pool_bytes (Deprecated)max_disk_io_util_percentmax_network_receive_bytes_ratemax_network_send_bytes_ratememory_pool_bytes_totalmemtable_flush_duration_usmemtable_flush_queue_countmemtable_flush_totalmerge_commit_append_pipemerge_commit_fail_totalmerge_commit_pendingmerge_commit_pending_bytesmerge_commit_pending_totalmerge_commit_register_pipe_totalmerge_commit_requestmerge_commit_request_bytesmerge_commit_request_totalmerge_commit_send_rpc_totalmerge_commit_success_totalmerge_commit_unregister_pipe_totalLatency metrics expose percentile series such as merge_commit_request_latency_99 and merge_commit_request_latency_90, reported in microseconds. The end-to-end latency obeys:
merge_commit_request = merge_commit_pending + merge_commit_wait_plan + merge_commit_append_pipe + merge_commit_wait_finish
Note: Before v3.4.11, v3.5.12, and v4.0.4, these latency metrics were reported in nanoseconds.
merge_commit_wait_finishmerge_commit_wait_planmeta_request_durationmeta_request_totalmetadata_mem_bytes (Deprecated)network_receive_bytesnetwork_receive_packetsnetwork_send_bytesnetwork_send_packetsordinal_index_mem_bytespage_cache_capacitypage_cache_hit_countpage_cache_insert_countpage_cache_insert_evict_countpage_cache_lookup_countpage_cache_release_evict_countpip_query_ctx_cntpipe_driver_execution_timepipe_driver_queue_lenpipe_driver_schedule_countpipe_poller_block_queue_lenpipe_prepare_pool_queue_lenpipe_scan_executor_queuingpk_index_compaction_queue_countpk_index_sst_read_error_totalpk_index_sst_write_error_totalplan_fragment_countprocess_fd_num_limit_hardprocess_fd_num_limit_softulimit command.process_fd_num_usedprocess_mem_bytesprocess_thread_numpublish_version_queue_countpush_request_duration_uspush_request_write_bytespush_request_write_bytes_per_secondpush_request_write_rowspush_requests_total