-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[BUG] ConfigurationException on creating OpenTelemetry SDK object when using AzureMonitorExporterBuilder #41859
Comments
@lmolkova could you please take a look? |
@greatvovan do you happen to have the full exception and the stack trace? Could you please share it? And please also enable OTel internal logging and share the logs. Thank you! @jeanbisutti @heyams or @trask should be able to investigate further. |
Yes, please share logs. @greatvovan |
@lmolkova I shared the full stack trace in the original message. |
I will try to repro it. |
@greatvovan I am not able to repro using based on the stack trace, it's to do with metadata service scheduler. it seemed that |
@heyams I cannot provide a repro app, because the essence of the bug is Databricks environment. In fact the both gists send telemetry just fine if wrapped by Regarding logs – as I cannot put a properties file next to a Scala notebook, I tried import java.util.logging.{Level => JulLevel}
import java.util.logging.{Logger => JulLogger}
JulLogger.getLogger("io.opentelemetry").setLevel(JulLevel.FINEST) But it did not produce any output. My guess is that JUL needs to be additionally configured to log to console? At this point I have nothing more to share as there is no any additional output anywhere. How else can I check/validate any ideas? |
When my PR is merged, I can give you a new exporter to try it out. I suspected that would resolve your issue. |
@greatvovan please try https://central.sonatype.com/artifact/com.azure/azure-monitor-opentelemetry-exporter v1.0.0-beta.29 and let us know the outcome. |
Hi @greatvovan. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue. |
This version seems broken, the code does not even compile complaining on missing See below (not putting it in a collapse section this time): import com.azure.monitor.opentelemetry.exporter.AzureMonitorExporterBuilder;
public class My
{
public static void main(String[] args) {
System.out.println("Hello");
}
} <project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.example</groupId>
<artifactId>otel-exporter</artifactId>
<version>1.0-SNAPSHOT</version>
<properties>
<maven.compiler.source>17</maven.compiler.source>
<maven.compiler.target>17</maven.compiler.target>
</properties>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.8.1</version>
<configuration>
<source>17</source>
<target>17</target>
</configuration>
</plugin>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>exec-maven-plugin</artifactId>
<version>3.0.0</version>
<configuration>
<mainClass>My</mainClass>
</configuration>
</plugin>
</plugins>
</build>
<dependencies>
<dependency>
<groupId>com.azure</groupId>
<artifactId>azure-monitor-opentelemetry-exporter</artifactId>
<version>1.0.0-beta.29</version>
</dependency>
</dependencies>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>io.opentelemetry.instrumentation</groupId>
<artifactId>opentelemetry-instrumentation-bom</artifactId>
<version>2.8.0</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
</project>
If I change 29 to 28, it compiles. Did you move this class to another package or something? |
Okay, it looks like you renamed it into I tried the original sample with
instead of
and the error does not reproduce. |
Describe the bug
When executing telemetry configuration code more than once in a Scala Databricks notebook / cluster, an "Unexpected configuration error" is thrown.
Exception or Stack Trace
ConfigurationException: Unexpected configuration error
To Reproduce
With auto configuration (gist 1) the code fails on
With manual configuration (gist 2), the code fails on
Code Snippet
See gists in repro steps.
Expected behavior
Detaching a notebook is expected to reset the state (equivalent to running a new notebook), however the cluster falls into a broken state and can be recovered only by a restart.
Screenshots
N/A
Setup (please complete the following information):
Additional context
Related bug: #41856.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report
The text was updated successfully, but these errors were encountered: