impress-2020/src/server/lib/beeline-graphql.js
Matchu dc785b063e remove detailed gql from honeycomb traces
This wasn't actually super helpful to read anyway, and I think it was causing us to hit rate limits.

We can maybe add back a limited version to like, add path context of _where_ a span happened in the GQL tree, but like, I feel like that's typically been pretty intuitive so far.
2020-09-19 21:34:35 -07:00

22 lines
442 B
JavaScript

const beeline = require("honeycomb-beeline");
const beelinePlugin = {
requestDidStart() {
const trace = beeline.startTrace();
return {
didResolveOperation({ operationName }) {
beeline.addContext({
name: operationName,
operation_name: operationName,
});
},
willSendResponse() {
beeline.finishTrace(trace);
},
};
},
};
module.exports = {
beelinePlugin,
};