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

TraceTelemetry w/Severity set is no longer appearing in Insights #436

Closed
FBNitro opened this issue Oct 4, 2017 · 4 comments · Fixed by #437
Closed

TraceTelemetry w/Severity set is no longer appearing in Insights #436

FBNitro opened this issue Oct 4, 2017 · 4 comments · Fixed by #437
Assignees
Labels
Milestone

Comments

@FBNitro
Copy link

FBNitro commented Oct 4, 2017

I picked up Version 1.0.10 yesterday. After doing so, all my trace lines with severities set stopped writing to application insights.

ie:

TraceTelemetry traceTelemetry = new TraceTelemetry("hello", SeverityLevel.Information);
 OperationContext operation = traceTelemetry.getContext().getOperation();
 operation.setId("MyTransactionId");
 telemetry.trackTrace(traceTelemetry);

The above stopped tracing with 1.0.10

while if I do the same thing, but set the SeverityLevel to null, it works:

TraceTelemetry traceTelemetry = new TraceTelemetry("hello", null);
 OperationContext operation = traceTelemetry.getContext().getOperation();
 operation.setId("MyTransactionId");
 telemetry.trackTrace(traceTelemetry);

I rolled back to 1.0.9 because of this defect.

@dhaval24
Copy link
Contributor

dhaval24 commented Oct 4, 2017

Thanks for pointing this out. In our preliminary investigation it seems that there is an issue with the TraceTelemetry class and we believe this is a critical issue and would be fixed as soon as possible in the next release.

@dhaval24
Copy link
Contributor

dhaval24 commented Oct 4, 2017

@FBNitro there is a pull request coming in #437 which will fix this. If you would like to get this working before official release, as soon as it is merged in the master you can build the master locally and run the latest version. Thanks for reporting this issue.

@HeikoH
Copy link

HeikoH commented Nov 13, 2017

@dhaval24 Any chance a new release can be created that includes this fix? (or, when will 1.0.11 be released?)

@dhaval24
Copy link
Contributor

dhaval24 commented Nov 14, 2017

@HeikoH the next release is tentatively scheduled for the end of November. Also the changes for this fix are already in master so, if you wish you can locally build it to try for something quick.

@dhaval24 dhaval24 modified the milestones: 1.0.11, 2.0.0 Dec 27, 2017
@ghost ghost locked as resolved and limited conversation to collaborators Jul 21, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
3 participants