graphql 2022-05-22 | Slack Archive

Fork me on GitHub

dviramontes17:05:10

Hello all, i’m not super familiar with pedestal and lacinia, does anyone have an example of how they’ve disabled tracing in production ? https://lacinia-pedestal.readthedocs.io/en/latest/tracing.html

thumbnail13:05:38

it’s disabled by default

dviramontes00:05:10

it does not appear to be disabled by default https://github.com/walmartlabs/lacinia-pedestal/blob/master/src/com/walmartlabs/lacinia/pedestal2.clj#L233

thumbnail06:05:16

The docs of that interceptor mention the following: https://github.com/walmartlabs/lacinia-pedestal/blob/1db186bc35404093a533c66b550b4891271b9401/src/com/walmartlabs/lacinia/pedestal2.clj#L183-L184 Which (in pedestal2) is controlled by a header: https://github.com/walmartlabs/lacinia-pedestal/blob/1db186bc35404093a533c66b550b4891271b9401/src/com/walmartlabs/lacinia/pedestal2.clj#L201 In pedestal1 you were required to manually adjust the context (the https://lacinia.readthedocs.io/en/latest/tracing.html#resolver-tracing). I suppose you should remove the enable-tracing-interceptor-interceptor from the chain.