This monorepo consolidates the following packages / applications:
| Component | Version(s) |
|---|---|
| The Connector docker images | see ghcr.io |
| The Connector helm charts | see ghcr.io and |
| TypeScript Connector SDK | |
| TypeScript Connector Types |
The documentation for this project is available at https://enmeshed.eu/integrate.
To get started developing in this repository, see the developer's guide.
The Connector exports logs, traces and metrics through OpenTelemetry. Configure the SDK with standard OTEL_* environment variables:
OTEL_EXPORTER_OTLP_ENDPOINT=http://otel-collector:4318
OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf
OTEL_SERVICE_NAME=enmeshed.connector
NMSHD_OTEL_LOG_LEVEL=INFOThe service name defaults to enmeshed.connector. Existing log appenders remain active, and application logs accepted by the configured log4js category levels are exported directly through the OpenTelemetry Logs SDK. NMSHD_OTEL_LOG_LEVEL controls the minimum level exported through OpenTelemetry and defaults to INFO; accepted values are ALL, TRACE, DEBUG, INFO, WARN, ERROR, FATAL and OFF. This setting does not affect other log appenders. Exporters, endpoints, protocols, authentication headers, sampling and resource attributes can be configured with their standard OpenTelemetry environment variables.
Only the instrumentations used by the Connector are included: amqplib, express, grpc, host-metrics, http, mongodb, redis, runtime-node and undici. OTEL_NODE_ENABLED_INSTRUMENTATIONS and OTEL_NODE_DISABLED_INSTRUMENTATIONS can select a subset of this list. Set OTEL_SDK_DISABLED=true to disable telemetry entirely.
Please file any bugs or feature requests by creating an issue.
Share your feedback with the enmeshed team by contributing to the discussions.
Contribution to this project is highly appreciated. Head over to our contribution guide to learn more.