Problem Statement
In some rare cases we aren't ready to use sentry yet but would like to start a trace. Updating end date is enough right now, can still construct whatever length we want though it would be nice to be able to set the start/end to the actual times something happened.
Specifically, this is in regards to overriding the duration value of an event. In particular, overriding the duration value for a custom Performance Span.
Solution Brainstorm
It seems like the change here should be fairly easy. Just change the access modifier to public from private like it is set for updateEndDate.
Here are the relevant lines in the SDK that I found that would need to be looked at/changed:
|
public boolean updateEndDate(final @NotNull SentryDate date) { |
|
private void updateStartDate(@NotNull SentryDate date) { |
┆Issue is synchronized with this Jira Improvement by Unito
Problem Statement
In some rare cases we aren't ready to use sentry yet but would like to start a trace. Updating end date is enough right now, can still construct whatever length we want though it would be nice to be able to set the start/end to the actual times something happened.
Specifically, this is in regards to overriding the duration value of an event. In particular, overriding the duration value for a custom Performance Span.
Solution Brainstorm
It seems like the change here should be fairly easy. Just change the access modifier to public from private like it is set for updateEndDate.
Here are the relevant lines in the SDK that I found that would need to be looked at/changed:
sentry-java/sentry/src/main/java/io/sentry/Span.java
Line 393 in 9762f09
sentry-java/sentry/src/main/java/io/sentry/Span.java
Line 420 in 9762f09
┆Issue is synchronized with this Jira Improvement by Unito