We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
List of NuGet packages and version that you are using (e.g. OpenTelemetry 0.4.0-beta.2):
OpenTelemetry 0.4.0-beta.2
Runtime version (e.g. net461, net48, netcoreapp2.1, netcoreapp3.1, etc. You can find this information from the *.csproj file):
net461
net48
netcoreapp2.1
netcoreapp3.1
*.csproj
Create a file "OTEL_DIAGNOSTICS.json" with content in folder "docs/trace/getting-started":
{ "LogDirectory": ".", "FileSize": 1024, "LogLevel": "Error" }
Run command in the same folder: dotnet run --configuration Release --framework net472 --project getting-started.csproj
dotnet run --configuration Release --framework net472 --project getting-started.csproj
A file would be generated with content:
Successfully opened file.2021-01-09T05:57:36.7394837Z:Activity started. OperationName = '{0}', Id = '{1}'.{Foo}{00-f02701bfe384804ea468f9f4770c6d2e-13c2dca1b5ebc549-01} 2021-01-09T05:57:36.7764812Z:Activity started. OperationName = '{0}', Id = '{1}'.{Bar}{00-f02701bfe384804ea468f9f4770c6d2e-7f5b345dbb1b624a-01} 2021-01-09T05:57:36.7774818Z:Activity started. OperationName = '{0}', Id = '{1}'.{Baz}{00-f02701bfe384804ea468f9f4770c6d2e-74abb7d3cce3f944-01} 2021-01-09T05:57:36.7954830Z:Activity stopped. OperationName = '{0}', Id = '{1}'.{Baz}{00-f02701bfe384804ea468f9f4770c6d2e-74abb7d3cce3f944-01} 2021-01-09T05:57:36.8824836Z:Activity stopped. OperationName = '{0}', Id = '{1}'.{Bar}{00-f02701bfe384804ea468f9f4770c6d2e-7f5b345dbb1b624a-01} 2021-01-09T05:57:36.8834843Z:Activity stopped. OperationName = '{0}', Id = '{1}'.{Foo}{00-f02701bfe384804ea468f9f4770c6d2e-13c2dca1b5ebc549-01}
There is also a separate issue that this file cannot be opened (even in read-only mode) by text editor when the program is running.
What is the expected behavior?
The issues don't happen for .NET Core: Run command dotnet run --configuration Release --framework netcoreapp3.1 --project getting-started.csproj:
dotnet run --configuration Release --framework netcoreapp3.1 --project getting-started.csproj
A file should be generated with content:
Successfully opened file.
Activity started/stopped events are Verbose level. They should be omitted by self diagnostics module when LogLevel is set to Error, according to EventListener.EnableEvents and EventLevel documentation.
Verbose
The file should be able to be opened, at least in read-only mode.
What did you expect to see?
See above. Running in .NET Frameworks should be the same as in result of .NET Core.
What is the actual behavior?
See above.
What did you see instead?
The text was updated successfully, but these errors were encountered:
@xiang17 Please confirm if this is already fixed and can be closed.
Sorry, something went wrong.
Yes it's already fixed.
No branches or pull requests
Bug Report
List of NuGet packages and
version that you are using (e.g.
OpenTelemetry 0.4.0-beta.2
):Runtime version (e.g.
net461
,net48
,netcoreapp2.1
,netcoreapp3.1
, etc.You can find this information from the
*.csproj
file):Symptom
Create a file "OTEL_DIAGNOSTICS.json" with content in folder "docs/trace/getting-started":
Run command in the same folder:
dotnet run --configuration Release --framework net472 --project getting-started.csproj
Bug#1
A file would be generated with content:
Bug#2
There is also a separate issue that this file cannot be opened (even in read-only mode) by text editor when the program is running.
What is the expected behavior?
The issues don't happen for .NET Core: Run command
dotnet run --configuration Release --framework netcoreapp3.1 --project getting-started.csproj
:A file should be generated with content:
Activity started/stopped events are
Verbose
level. They should be omitted by self diagnostics module when LogLevel is set to Error, according to EventListener.EnableEvents and EventLevel documentation.The file should be able to be opened, at least in read-only mode.
What did you expect to see?
See above. Running in .NET Frameworks should be the same as in result of .NET Core.
What is the actual behavior?
See above.
What did you see instead?
See above.
The text was updated successfully, but these errors were encountered: