> ## Documentation Index > Fetch the complete documentation index at: https://docs.kinetica.com/llms.txt > Use this file to discover all available pages before exploring further. # create_table_monitor

create\_table\_monitor

create\_table\_monitor(
table\_name: string,
options?: Record\<string, string>,
callback?: GPUdbCallback,
): Promise\<CreateTableMonitorResponse>
Creates a monitor that watches for a single table modification event type (insert, update, or delete) on a particular table (identified by table\_name) and forwards event notifications to subscribers via ZMQ. After this call completes, subscribe to the returned topic\_id on the ZMQ table monitor port (default 9002). Each time an operation of the given type on the table completes, a multipart message is published for that topic; the first part contains only the topic ID, and each subsequent part contains one binary-encoded Avro object that corresponds to the event and can be decoded using type\_schema. The monitor will continue to run (regardless of whether or not there are any subscribers) until deactivated with clear\_table\_monitor.

For more information on table monitors, see Table Monitors.
Parameters
- table\_name: string
  
  Name of the table to monitor, in \[schema\_name.]table\_name format, using standard name resolution rules.
- Optionaloptions: Record\<string, string>
  
  Optional parameters.
- Optionalcallback: GPUdbCallback
  
  Optional callback function
Returns Promise\<CreateTableMonitorResponse>

Promise\ - Promise resolving to the response
- Defined in src/GPUdb.ts:6846

create\_table\_monitor\_request

create\_table\_monitor\_request(
request: CreateTableMonitorRequest,
callback?: GPUdbCallback,
): Promise\<CreateTableMonitorResponse>
Creates a monitor that watches for a single table modification event type (insert, update, or delete) on a particular table (identified by table\_name) and forwards event notifications to subscribers via ZMQ. After this call completes, subscribe to the returned topic\_id on the ZMQ table monitor port (default 9002). Each time an operation of the given type on the table completes, a multipart message is published for that topic; the first part contains only the topic ID, and each subsequent part contains one binary-encoded Avro object that corresponds to the event and can be decoded using type\_schema. The monitor will continue to run (regardless of whether or not there are any subscribers) until deactivated with clear\_table\_monitor.

For more information on table monitors, see Table Monitors.
Parameters
- request: CreateTableMonitorRequest
  
  Request object containing the parameters for the operation
- Optionalcallback: GPUdbCallback
  
  Optional callback function
Returns Promise\<CreateTableMonitorResponse>

Promise\ - Promise resolving to the response
- Defined in src/GPUdb.ts:6811

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.