New Relic APM Instrumentation Language Collocations
Practise the standard verbs for instrumenting services with New Relic correctly.
0 / 5 completed
1 / 5
Fill in: 'We ___ the APM agent at the application entry point, rather than a partial install that misses whole transaction paths.'
We 'install an agent' — the standard, simple collocation for adding APM instrumentation. The other options are less idiomatic here.
2 / 5
Fill in: 'Skipping custom transaction naming can ___ a slow endpoint buried under a generic label nobody can actually identify.'
We say skipped naming will 'leave' a slow endpoint buried — the standard, natural collocation for the resulting obscurity. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ custom instrumentation around external calls explicitly, rather than a black-box span nobody can actually break down.'
We 'add instrumentation' — the standard, simple collocation for wrapping calls with custom spans. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every deployed instrumentation change against staging traces, rather than shipping a config nobody's actually verified.'
We 'verify a change' — the standard, simple collocation for confirming instrumentation before production. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ apdex scores per transaction closely, rather than treating one aggregate number as the actual whole picture.'
We 'monitor scores' — the standard, simple collocation for watching per-transaction performance. The other options aren't idiomatic here.