Skip to content

v6 major release#2552

Open
aryamohanan wants to merge 32 commits into
mainfrom
v6-release
Open

v6 major release#2552
aryamohanan wants to merge 32 commits into
mainfrom
v6-release

Conversation

@aryamohanan
Copy link
Copy Markdown
Contributor

@aryamohanan aryamohanan commented May 15, 2026

BREAKING CHANGES:

  • The configuration precedence is updated. The new configuration precedence order is:

    environment variables > in-code configuration > agent configuration > default values

see: #2432

  • The environment variable INSTANA_DEV_MIN_DELAY_BEFORE_SENDING_SPANS is removed. Use INSTANA_TRACING_TRANSMISSION_DELAY instead.

public docs any updates: https://github.ibm.com/instana/docs/pull/19776/files

ref https://jsw.ibm.com/browse/INSTA-82558

Before release

After release

  • Public doc release
  • Prepare Release notes

@aryamohanan aryamohanan changed the title docs: updated major version to v6 v6 major release May 15, 2026
aryamohanan and others added 29 commits May 15, 2026 17:01
…nce (#2430)

- Created a utility file for shared configuration helpers.
- Moved and renamed normalizeSingleValue to resolveNumericConfig within the new utility module.
…v variable (#2431)

BREAKING CHANGE:
- The environment variable INSTANA_DEV_MIN_DELAY_BEFORE_SENDING_SPANS has been removed.
- Please use INSTANA_TRACING_TRANSMISSION_DELAY instead.
 Restructured the existing tests to improve logical grouping
- Normalization previously operated on a pre-filled in-code user config, making it unclear whether values were already present or resolved later(from env, in-code, or defaults).

- This change separated input from the
resulting config, making value resolution explicit and easier to follow.
BREAKING CHANGE: 
environment config now overrides in-code configuration.
Enforces consistent precedence:
env > in-code
Previously inconsistent behavior is now fixed. This may impact setups relying on the old precedence.
ref https://jsw.ibm.com/browse/INSTA-80965
ProcessControls was setting INSTANA_TRACING_DISABLE=false for all tests
where tracingEnabled=true (the default). According to the precedence rules
in disable.js, when INSTANA_TRACING_DISABLE is set to 'false', it takes
precedence over INSTANA_TRACING_DISABLE_INSTRUMENTATIONS and
INSTANA_TRACING_DISABLE_GROUPS, preventing granular disable configurations
from working in tests.

This caused logging integration tests to fail when trying to disable
specific instrumentations using INSTANA_TRACING_DISABLE_INSTRUMENTATIONS
or INSTANA_TRACING_DISABLE_GROUPS.

Changed ProcessControls to only set INSTANA_TRACING_DISABLE='true' when
tracingEnabled=false, and not set it at all when tracingEnabled=true,
allowing other disable environment variables to work correctly.
…olean

Fixed normalizeTracingEnabled to only use INSTANA_TRACING_DISABLE for the
tracing.enabled config when the env var value is 'true' or 'false'. When it
contains instrumentation/group names (e.g., 'logging'), it's now handled by
the separate disable normalizer
BREAKING CHANGE:
agent config now applies based on the precedence.
Enforces consistent precedence:
env > in-code > agent config > default
Previously inconsistent behavior is now fixed. This may impact setups relying on the old precedence.
#2506)

External config updates now deep-merge nested plain objects into the existing normalized config instead of replacing them at the top level.
@aryamohanan aryamohanan marked this pull request as ready for review May 15, 2026 11:31
@aryamohanan aryamohanan requested a review from a team as a code owner May 15, 2026 11:31
@aryamohanan aryamohanan added the v6 label May 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants