Extend tables

An extend table is a small key-to-record lookup table kept in MoleSignal. A pipeline transform looks a key up in it to enrich events with reference data: map a service to the team that owns it, an account ID to a plan tier, or a region code to a region name, without calling an external store on the hot path.

The table list

Open Extend tables. The head counts the tables and their records. Each table shows its lookup key and fields, the number of records, where it is used, the last update, and its state, Healthy or Empty. Filter by state and by usage (In use or Unused), and search by name.

Create a table

Select New extend table. The wizard has two steps.

Define schema

Enter the Table name and a Description. Choose the Lookup key, the field that identifies a record, such as customer_id, service, or region_code. Add Value fields with a Field name, a Type (String, Number, Boolean, or Object), whether it is Required, and a description. Leave the value fields empty to store flexible JSON records instead. A table holds up to 100 value fields; field names use letters, digits, ., -, and _.

Add or import data

Choose Start empty to add records later, or Paste JSON to load them now: a JSON array of records that each carry the lookup key, or an object that maps each key to its record.

Select Create extend table.

Records

Open a table. The Data records tab lists the records; search them by lookup key or by a field value.

Action	Effect
Add record	Enter the lookup key and the field values, in Form mode or JSON mode. A key that already exists is overwritten after a warning.
Edit record	Changes the values of a record.
View JSON	Shows the whole record, including fields that the table does not list as columns.
Delete record	Deletes the record. It cannot be undone.
Import data	Writes many records at once from a JSON file (an array or a key-to-record map), a CSV file whose first row holds the field names, or pasted JSON or CSV. The data must contain the lookup-key column. The summary says how many records will be imported and how many overwrite existing keys.

Schema, usage, and settings

Tab	Content
Schema	The lookup key and the value fields. Edit fields adds fields and changes descriptions and Required. While the table has records, existing fields cannot be renamed, retyped, or removed; an empty table allows all changes. The table name and the lookup key never change.
Usage	The pipelines and saved queries that reference the table. Check it before changing or deleting the table.
Settings	Table information, and Delete extend table under Danger zone, which deletes the table and all its records and can break the pipelines that reference it.

Look up a key in a pipeline

Inside a VRL transform, call lookup(table, key) and read a field off the returned record:

# enrich each event with the service's owning team
.team = lookup("service_meta", .service).team

Lookups run in memory and add no query or storage cost to a pipeline run. The table loads on startup and stays current as records are added, changed, or deleted. Extend tables belong to the workspace and every pipeline of it can use them.

Extend table API

# upsert a record keyed by "checkout"
curl -X PUT http://localhost:5080/api/v1/extend_tables/service_meta/rows/checkout \
  -H "authorization: Bearer $MS_JWT" \
  -H 'content-type: application/json' \
  -d '{"team":"payments","tier":"gold"}'

Action	Endpoint
List tables	`GET /api/v1/extend_tables`
List the records of a table	`GET /api/v1/extend_tables/{table}`
Upsert a record	`PUT /api/v1/extend_tables/{table}/rows/{key}`
Delete a record	`DELETE /api/v1/extend_tables/{table}/rows/{key}`

Permissions

functions.read lists tables and their usage. Creating a table requires functions.create, changing records and fields requires functions.edit, and deleting a table requires functions.delete.

Pipelines

Build the transform chain that calls the extend tables.

Get started

Data

Observe

Query and correlate

Reliability

AI ops

Collaboration

Admin

Deploy & operate

Best practices

Resources

The table list

Create a table

Records

Schema, usage, and settings

Look up a key in a pipeline

Extend table API

Permissions

Pipelines

​The table list

​Create a table

​Records

​Schema, usage, and settings

​Look up a key in a pipeline

​Extend table API

​Permissions

Pipelines

The table list

Create a table

Records

Schema, usage, and settings

Look up a key in a pipeline

Extend table API

Permissions