[JIRA] (JENKINS-49892) Evaluate options for collecting "method instrumentation" telemetry

[email protected] (JIRA) Thu, 15 Mar 2018 08:38:20 -0700

Title: Message Title

R. Tyler Croy assigned an issue to Carlos Sanchez

In the Gitter chat, Jesse Glick suggested implementing code changes and then taking advantage of the existing error telemetry tooling which will be implemented as part of JENKINS-49805.

If I'm understanding Jesse Glick's suggestion correctly, we would be making code changes on methods we would want to see call stacks from via some code

 
                                                                private static final Set<String> WARNINGS = new ConcurrentSet<>(); 
public static void warnAboutDeprecatedMethod() { 
  StackTraceElements[] stack = new Throwable().getStackTrace(); 
  String key = stack[2] + " →  " + stack[1];
  if (WARNINGS.add(key) { 
    LOGGER.warning("deprecated call to " + stack[1] + "\n\tat " + stack[2]); 
  }
}
  
                                                            

Which could then be called in "methods of interest", and use the error telemetry mechanism to transmit the call stack off the Jenkins instance.

Carlos Sanchez, since this saves us a boatload of work, I'm perfectly fine with it if you are

Jenkins /

JENKINS-49892

Change By:	R. Tyler Croy
Assignee:	R. Tyler Croy Carlos Sanchez

Add Comment

This message was sent by Atlassian JIRA

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-49892) Evaluate options for collecting "method instrumentation" telemetry

Reply via email to