Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CAT Documentation #202

Closed
wants to merge 1 commit into from
Closed

CAT Documentation #202

wants to merge 1 commit into from

Conversation

rsteckler
Copy link

This documents the ability to enable or disable cross application tracing from the config file.

This documents the ability to enable or disable cross application tracing from the config file.
@rsteckler
Copy link
Author

A little context: After configuring new relic for my node app, I started seeing calls I was making to a third party service start failing. After a fair amount of debugging, I realized that new relic was adding the x-newrelic-id and x-newrelic-transcation headers to all outbound http requests. Those headers were making the third party API barf.
I looked through the docs, forum, and StackOverflow looking for a way to disable it and couldn't find anything. A quick pass through the source showed that the CAT code is checking this undocumented config file setting.

I believe it should be documented because there are cases where it breaks things.

@wraithan
Copy link
Contributor

Unfortunately we do not document the feature flags as they are meant to be temporary settings for our users who agree to beta for us to be able to turn on. They are considered private API, so we don't consider it a breaking change when we remove the ability to set them, which happens periodically as we sweep the code base to remove old feature flags.

We have an outstanding feature request to add the ability to toggle CAT headers. But by turning off that feature flag you are also turning off things like synthetics transactions and other things. It is no longer just CAT that is behind that as we've built on top of CAT. Honestly at this point that flag should have already been removed. Your best bet is to contact support and request this as we keep track of feature requests and it will let our PMs know this should be a priority.

@wraithan wraithan closed this Oct 19, 2015
bizob2828 added a commit to bizob2828/node-newrelic that referenced this pull request Apr 19, 2024
…/word-wrap-1.2.4

Bump word-wrap from 1.2.3 to 1.2.4
bizob2828 added a commit to bizob2828/node-newrelic that referenced this pull request Apr 23, 2024
…/word-wrap-1.2.4

Bump word-wrap from 1.2.3 to 1.2.4
bizob2828 pushed a commit to bizob2828/node-newrelic that referenced this pull request Jul 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants