There's probably a better way to do this, but just...
# devj
joshua_kelly
08/17/2023, 2:20 PMThere's probably a better way to do this, but just sharing this example of injecting
dd-trace Copy code
FROM medplum/medplum-server:latest
RUN npm install --save dd-trace
RUN echo "const tracer = require('dd-trace').init();\
const medplum = require(\"./packages/server/dist/index.js\");\
medplum.main(process.argv.length === 3 ? process.argv[2] : 'file:medplum.config.json').catch(console.log)" > entrypoint.js
ENTRYPOINT [ "node", "entrypoint.js" ]joshua_kelly
08/17/2023, 2:23 PMAlso tried using ESM loader:
Copy code
FROM medplum/medplum-server:latest
RUN npm install --save dd-trace
ENTRYPOINT [ "node", "--loader", "dd-trace/loader-hook.mjs", "packages/server/dist/index.js" ]require.mainr
reshma
08/17/2023, 3:37 PMHm, is there some reason the Datadog agent integration won't work? Is it due to the custom setup? https://www.medplum.com/docs/self-hosting/datadog
j
joshua_kelly
08/17/2023, 4:10 PMThe agent can be used for several features, including Logging and Tracing. Logging mostly works out of box on ECS if you are running a sidecar Agent container like this config.
Tracing, however, requires instrumentation at the level of the application -- requires adding the
dd-tracejoshua_kelly
08/17/2023, 4:11 PMI have a slight improvement over the above though, which is this:
Copy code
FROM medplum/medplum-server:latest
RUN npm install --save dd-trace
ENTRYPOINT [ "node", "--require", "dd-trace/init", "packages/server/dist/index.js" ]joshua_kelly
08/17/2023, 4:13 PMI thought about submitting an upstream PR here but it probably doesn't make sense to so tightly couple this telemetry to a specific vendor.
It would be best to instrument with OpenTelemetry in the server application -- the various vendors have SDKs that hook up to it (https://opentelemetry.io/docs/what-is-opentelemetry/)
r
reshma
08/17/2023, 4:24 PMAh got it - thanks for this context!
j
joshua_kelly
08/17/2023, 8:17 PMHere's an example of this working (test data)
164 Views