Skip to content

Commit

Permalink
chore: Add AWS Bedrock feature flag (#1913)
Browse files Browse the repository at this point in the history
  • Loading branch information
jsumners-nr committed Dec 14, 2023
1 parent ee81429 commit 91019b0
Show file tree
Hide file tree
Showing 3 changed files with 10 additions and 2 deletions.
6 changes: 6 additions & 0 deletions documentation/feature-flags.md
Expand Up @@ -38,3 +38,9 @@ Any prerelease flags can be enabled or disabled in your agent config by adding a
* Configuration: `{ feature_flag: { legacy_context_manager: true|false }}`
* Environment Variable: `NEW_RELIC_FEATURE_FLAG_LEGACY_CONTEXT_MANAGER`
* Description: The legacy context manager was replaced by AsyncLocalContextManager for async context propagation. If your application is not recording certain spans or creating orphaned data, you may want to enable this older context manager. Enabling this feature flag may increase the agent's use of memory and CPU.

#### aws_bedrock_instrumentation
* Enabled by default: `false`
* Configuration: `{ feature_flag: { aws_bedrock_instrumentation: true|false }}`
* Environment Variable: `NEW_RELIC_FEATURE_FLAG_AWS_BEDROCK_INSTRUMENTATION`
* Description: Enables instrumentation of AWS Bedrock in `aws-sdk@3`.
3 changes: 2 additions & 1 deletion lib/feature_flags.js
Expand Up @@ -12,7 +12,8 @@ exports.prerelease = {
reverse_naming_rules: false,
undici_async_tracking: true,
unresolved_promise_cleanup: true,
legacy_context_manager: false
legacy_context_manager: false,
aws_bedrock_instrumentation: false
}

// flags that are no longer used for released features
Expand Down
3 changes: 2 additions & 1 deletion test/unit/feature_flag.test.js
Expand Up @@ -34,7 +34,8 @@ const used = [
'certificate_bundle',
'unresolved_promise_cleanup',
'undici_instrumentation',
'undici_async_tracking'
'undici_async_tracking',
'aws_bedrock_instrumentation'
]

tap.test('feature flags', (t) => {
Expand Down

0 comments on commit 91019b0

Please sign in to comment.