-
Notifications
You must be signed in to change notification settings - Fork 0
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
solution for a collector #1
Comments
|
The latter seems the way to go for Azure Opentelemetry. Will try inside my Azure DevOps project. Well, there I'll opt for Azure Insights because it is more mature |
You can send opentelemetry traces to grafana cloud tempo saas without an agent or a collector: see my dotnet and python code also there. .NET services.AddOpenTelemetryTracing((builder) =>
builder
//https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/docs/trace/customizing-the-sdk/README.md
.AddSource("AzureTracer")
.SetResourceBuilder(ResourceBuilder.CreateDefault()
.AddService("API.TestBed"))
// Instrument HttpClient calls and pass on context
// .AddHttpClientInstrumentation() // catching azure live diagnostic
.AddAspNetCoreInstrumentation()
.AddSqlClientInstrumentation(
options => options.SetDbStatementForText = true)
.AddConsoleExporter()
.AddOtlpExporter(o =>
{
o.Endpoint = new Uri("https://tempo-eu-west-0.grafana.net"); //"http://otel-collector:4317");
string token = "my encoded token";
o.Headers = $"Authorization=Basic {token}";
o.ExportProcessorType = ExportProcessorType.Simple;
}));
} PythonNotice that for python it is necessary to upgrade to version 1.12 of opentelemetry sdk!
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We can't send straight to grafana, apparently, but we need an agent or a collector. That must be running on his own, hence the runtime implementation "to-do".
The text was updated successfully, but these errors were encountered: