You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/bug_report.yaml
+58-16Lines changed: 58 additions & 16 deletions
Original file line number
Diff line number
Diff line change
@@ -5,38 +5,61 @@ body:
5
5
- type: markdown
6
6
attributes:
7
7
value: |
8
-
Thanks for taking the time to fill out this bug report!
9
-
Please make sure to fill out the entire form below,
10
-
providing as much context as you can in order to help us
11
-
triage and track down your bug as quickly as possible.
8
+
> [!IMPORTANT]
9
+
> **Please read all parts of this form carefully.** By following the instructions carefully, you ensure that we
10
+
> can get started fixing your bug, instead of being stuck at trying to reproduce your issue. Please provide
11
+
> all requested information, even if you think it does not apply to your problem.
12
+
>
13
+
> **If you use a third-party package that re-distributes OpenTelemetry, open the bug ticket with that third party unless you can provide steps to reproduce this with pure OpenTelemetry.**
14
+
> Digging into third-party distributions of OpenTelemetry is not in scope for this project.
12
15
13
-
Before filing a bug, please be sure you have searched through
If your bug is related to an instrumentation or plugin in [opentelemetry-js-contrib](https://github.com/open-telemetry/opentelemetry-js-contrib)
18
-
please be sure to file it there.
16
+
Before filing a bug, please be sure you have searched through [existing open bugs](https://github.com/open-telemetry/opentelemetry-js/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3Abug)
17
+
to see if this bug has already been filed.
18
+
- type: markdown
19
+
attributes:
20
+
value: |
21
+
## Bug Reproduction
19
22
- type: textarea
20
23
attributes:
21
24
label: What happened?
22
-
description: Please provide as much detail as you reasonably can.
25
+
description: |
26
+
> [!IMPORTANT]
27
+
> **Please provide as much detail as you reasonably can.**
28
+
> We all know the complexities of developing with JavaScript/TypeScript. **Be specific** about your setup and **DO NOT** assume that the person handling your bug report knows how to use your specific combination of tooling. Always provide build instructions and config files.
23
29
value: |
24
30
## Steps to Reproduce
25
-
31
+
<!--
32
+
The most effective way to solve a bug is to provide a link to a reproducer repository. It is extremely difficult to exactly reproduce problems
33
+
and doing so can take multiple hours for us. You know your tooling and setup and we know OpenTelemetry JavaScript internals.
34
+
Let's help each other! :)
35
+
-->
26
36
## Expected Result
27
37
28
38
## Actual Result
29
39
30
40
## Additional Details
41
+
<!--
42
+
Anything you can think of that will help us reproduce and understand your problem:
43
+
- details about the behavior of the bug
44
+
- code to reproduce, if not provided via a repository above (including setting up any frameworks you may be using, we likely don't use the same tech-stack that you're using on the daily)
45
+
- which tooling you use and how you're using it
46
+
- config files for your tooling (typescript, bundlers, ...)
47
+
- how you run your code (example: `node -r otel.js ./index.js`).
48
+
- which module type you are you using (`module` or `commonjs`)
49
+
-->
50
+
31
51
32
52
validations:
33
53
required: true
34
54
- type: textarea
35
55
attributes:
36
56
label: OpenTelemetry Setup Code
37
-
description: Please provide the code you use to set up OpenTelemetry
57
+
description: |
58
+
Please provide the code you use to set up OpenTelemetry.
59
+
If you use `@opentelemetry/auto-instrumentations-node/register`, please state so here.
60
+
You may omit this step if you have provided a reproducer repository.
38
61
placeholder: | # This comes from our README.md
39
-
// tracing.js
62
+
// otel.js
40
63
41
64
'use strict'
42
65
@@ -75,13 +98,15 @@ body:
75
98
- type: textarea
76
99
attributes:
77
100
label: package.json
78
-
description: If possible, please provide your full package.json. If not, please provide at least your list of dependencies and their versions, especially OpenTelemetry versions.
101
+
description: |
102
+
Please provide your the full package.json needed to reproduce the issue.
103
+
You may omit this step if you provided a reproducer repository.
79
104
render: "JSON"
80
105
placeholder: |
81
106
{
82
107
"name": "my-app",
83
108
"scripts": {
84
-
"start": "node -r tracing.js app.js"
109
+
"start": "node -r otel.js app.js"
85
110
},
86
111
"dependencies": {
87
112
"@opentelemetry/api": "^1.3.0",
@@ -95,3 +120,20 @@ body:
95
120
description: |
96
121
Please copy and paste any relevant log output.
97
122
render: shell
123
+
- type: markdown
124
+
attributes:
125
+
value: |
126
+
## System Details
127
+
System Details help us when we cannot reproduce your problem with the information provided above. Sometimes bugs only surface on specific platforms and runtime versions.
128
+
- type: textarea
129
+
attributes:
130
+
label: Operating System and Version
131
+
placeholder: Ubuntu 24.04, Windows 11 Build 26100.2033, macOS 15.0.1
Copy file name to clipboardExpand all lines: CHANGELOG.md
+21-4Lines changed: 21 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,24 @@ For semantic convention package changes, see the [semconv CHANGELOG](packages/se
13
13
14
14
### :rocket: (Enhancement)
15
15
16
+
### :bug: (Bug Fix)
17
+
18
+
* fix(sdk-trace-base): do not load OTEL_ env vars on module load, but when needed [#5224](https://github.com/open-telemetry/opentelemetry-js/pull/5224)
19
+
20
+
### :books: (Refine Doc)
21
+
22
+
### :house: (Internal)
23
+
24
+
## 1.29.0
25
+
26
+
### :boom: Breaking Change
27
+
28
+
* feat(sdk-metrics): Add support for aggregation cardinality limit with a default limit of 2000. This limit can be customized via views [#5182](https://github.com/open-telemetry/opentelemetry-js/pull/5128)
29
+
30
+
## 1.28.0
31
+
32
+
### :rocket: (Enhancement)
33
+
16
34
* feat(sdk-metrics, sdk-trace): add `mergeResourceWithDefaults` flag, which allows opting-out of resources getting merged with the default resource [#4617](https://github.com/open-telemetry/opentelemetry-js/pull/4617)
17
35
* default: `true` (no change in behavior)
18
36
* note: `false` will become the default behavior in the next major version in order to comply with [specification requirements](https://github.com/open-telemetry/opentelemetry-specification/blob/f3511a5ccda376dfd1de76dfa086fc9b35b54757/specification/resource/sdk.md?plain=1#L31-L36)
@@ -22,10 +40,9 @@ For semantic convention package changes, see the [semconv CHANGELOG](packages/se
22
40
### :bug: (Bug Fix)
23
41
24
42
* fix(sdk-metrics): await exports in `PeriodicExportingMetricReader` when async resource attributes have not yet settled [#5119](https://github.com/open-telemetry/opentelemetry-js/pull/5119/)@pichlermarc
25
-
26
-
### :books: (Refine Doc)
27
-
28
-
### :house: (Internal)
43
+
* fix(sdk-trace): performance.now() may return the same value for consecutive calls [#5150](https://github.com/open-telemetry/opentelemetry-js/pull/5150)@dyladan
44
+
* fix(sdk-trace-base): pass BatchSpanProcessor#forceFlush() errors on visibilitychange/pagehide to globalErrorHandler [#5143](https://github.com/open-telemetry/opentelemetry-js/pull/5143)@pichlermarc
45
+
* fixes a bug where switching browser tabs with a failing exporter would cause an unhandled error
Remember to always work in a branch of your local copy, as you might otherwise have to contend with conflicts in main.
147
147
148
-
Please also see [GitHub workflow](https://github.com/open-telemetry/community/blob/master/CONTRIBUTING.md#github-workflow) section of general project contributing guide.
148
+
Please also see [GitHub workflow](https://github.com/open-telemetry/community/blob/main/guides/contributor/processes.md#github-workflow) section of general project contributing guide.
0 commit comments