Skip to content

Reference

Look up config keys, filter syntax, error codes, telemetry signals, and data shapes. Reference pages generated from source stay in sync with your running version.

SectionWhat’s in it
Data ModelEntry identifiers, operational attributes, change events
FiltersFleX, JSON, SCIM, LDAP filter syntax
ConfigAll configuration keys (HOCON + env vars)
TelemetryMetric names, attribute keys, span names
Error CodesError catalog with protocol mappings

Every entry supports four identifier formats. Use whichever your protocol needs.

FormatExampleWhen to use
GlobalIddXNlcjo5aXgDefault. URL-safe, fastest lookup.
UUID550e8400-e29b-41d4-a716-446655440000External system integration
DNcn=john,ou=users,dc=example,dc=comLDAP compatibility
UOID12345Legacy numeric references

The same query in each format:

FleX: cn = John
JSON: {"cn": "John"}
SCIM: cn eq "John"
LDAP: (cn=John)

Scribe auto-detects the format. See Filters for operators, combinators, and attribute groups.

VariablePurpose
SCRIBE_LDAP_URLSource LDAP server URL
SCRIBE_DATABASE_URLPostgreSQL connection string
SCRIBE_AUTH_ENABLEDEnable authentication (true/false)
SCRIBE_AUTH_ISSUEROAuth2/OIDC issuer URL

All SCRIBE_* variables map to config keys. See Configuration for the full mapping, or Config Reference for every key.

Reference entries support canonical deep links via /ref/*:

KindRouteExample
Config/ref/c/<key>/ref/c/database.max-pool-size
Metric/ref/m/<name>/ref/m/scribe.channel.requests.total
Attribute/ref/a/<key>/ref/a/scribe.query.signature
Error/ref/e/<code>/ref/e/DIRECTORY_BUSY
Shorthand/ref/<token>/ref/DIRECTORY_BUSY

Metric names work with both OTel (dotted) and Prometheus (underscore) notation.