# OpenTelemetry custom traces Copy as Markdown[Open in ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fintegrations%2Fdata-ingestion%2Fopentelemetry-custom-traces.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[Open in Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fintegrations%2Fdata-ingestion%2Fopentelemetry-custom-traces.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.) Send your **custom traces** to Coralogix using our OpenTelemetry-compatible endpoint. ## Overview[​](#overview "Direct link to Overview") Custom [traces](https://coralogix.com/docs/docs/user-guides/data_exploration/spans/.md) can be delivered directly to the Coralogix OpenTelemetry-compatible ingress.:443 endpoint using any gRPC client or [OpenTelemetry SDKs](https://opentelemetry.io/docs/concepts/sdk-configuration/). The examples below guide you using gRPCurl and OpenTelemetry **Java** SDK. This is an alternative to using the [OpenTelemetry Collector](https://coralogix.com/docs/docs/opentelemetry/getting-started/.md). ## Prerequisites[​](#prerequisites "Direct link to Prerequisites") If you are sending us your data using gRPCurl, you are required to have [Git](https://git-scm.com/) and [gRPCurl](https://github.com/fullstorydev/grpcurl) installed. ## Data model[​](#data-model "Direct link to Data model") The custom metric API implementation is based on the OpenTelemetry [tracing specification](https://github.com/open-telemetry/opentelemetry-proto/blob/main/opentelemetry/proto/trace/v1/trace.proto). This ensures that our tracing implementation adheres to industry best practices and can seamlessly integrate with other components and tools in the OpenTelemetry ecosystem. ### Example tracing span[​](#example-tracing-span "Direct link to Example tracing span") ``` { "resource_spans": [ { "resource": { "attributes": [ { "key": "cx.application.name", "value": { "string_value": "my-test-application" } }, { "key": "cx.subsystem.name", "value": { "string_value": "my-test-subsystem" } }, { "key": "service.name", "value": { "string_value": "my-test-service" } } ] }, "scope_spans": [ { "scope": { "name": "test" }, "spans": [ { "trace_id": "d0XALf50O6rdjlMxreTJsA==", "span_id": "YolJ2eFjJCs=", "name": "test-span", "kind": "SPAN_KIND_INTERNAL", "start_time_unix_nano": "1665753217736722000", "end_time_unix_nano": "1665753217737156416", "status": {} } ] } ] } ] } ``` ## Sending data with gRPCurl[​](#sending-data-with-grpcurl "Direct link to Sending data with gRPCurl") gRPC is a modern way of calling APIs on top of HTTP/2. Similar to cURL, [gRPCurl](https://github.com/fullstorydev/grpcurl) is a command-line tool used to communicate with gRPC services. Coralogix supports OTLP/gRPC and OTLP/HTTP (binary protobuf or JSON payloads) for its custom traces endpoint. Assuming the example in the data model is saved as `traces.json`, use the following command to send your data to Coralogix: ``` # Clone OpenTelemetry protobuf definitions git clone https://github.com/open-telemetry/opentelemetry-proto.git # Send traces to Coralogix grpcurl -v -d @ \ -rpc-header 'Authorization: Bearer ' \ -proto opentelemetry-proto/opentelemetry/proto/collector/trace/v1/trace_service.proto \ -import-path opentelemetry-proto \ ingress.eu2.coralogix.com:443 \ opentelemetry.proto.collector.trace.v1.TraceService/Export \ < traces.json ``` **Notes**: * For ``, select the ingress.:443 endpoint that corresponds to your Coralogix [domain](https://coralogix.com/docs/docs/user-guides/account-management/account-settings/coralogix-domain/.md) using the domain selector at the top of the page. * For the ``, input your Coralogix [Send-Your-Data API key](https://coralogix.com/docs/docs/user-guides/account-management/api-keys/send-your-data-api-key/.md). * Set the `start_time_unix_nano` and the `end_time_unix_nano` in the `traces.json` to a timestamp that is within the last 24 hours. ## Sending data using the OpenTelemetry Java SDK[​](#sending-data-using-the-opentelemetry-java-sdk "Direct link to Sending data using the OpenTelemetry Java SDK") The example below guides you using OpenTelemetry Java SDK to send your custom traces to Coralogix. Others [SDKs](https://opentelemetry.io/docs/concepts/sdk-configuration/) may also be used. **STEP 1**. Add the following libraries to your maven pom.xml: ``` io.opentelemetry opentelemetry-sdk-trace io.opentelemetry opentelemetry-exporter-otlp ``` **STEP 2**. Use this code snippet to create and report a span: ``` SdkTracerProvider traceProvider = SdkTracerProvider.builder() .addSpanProcessor(BatchSpanProcessor.builder( OtlpGrpcSpanExporter.builder() .setEndpoint("https://ingress.eu2.coralogix.com:443") .addHeader("Authorization", "Bearer ") .build() ).build()) .setResource(Resource.create(Attributes.of( ResourceAttributes.SERVICE_NAME, "my-test-service", AttributeKey.stringKey("cx.application.name"), "my-test-application", AttributeKey.stringKey("cx.subsystem.name"), "my-test-subsystem" ))) .build(); Tracer tracer = traceProvider.tracerBuilder("test").build(); Span span = tracer.spanBuilder("test-span") .setSpanKind(SpanKind.INTERNAL) .startSpan(); span.end(); traceProvider.forceFlush(); ``` ## Limits & quotas[​](#limits--quotas "Direct link to Limits & quotas") Coralogix places a **hard limit of 10MB** of data to our OpenTelemetry [endpoints](https://coralogix.com/docs/docs/integrations/coralogix-endpoints/.md), with a **recommendation of 2MB**. Limits apply to single requests, regardless of timespan. ## Additional resources[​](#additional-resources "Direct link to Additional resources") | | | | ------------- | ------------------------------------------------------------------------------------------- | | Documentation | [Coralogix Endpoints](https://coralogix.com/docs/docs/integrations/coralogix-endpoints/.md) | | External | [GitHub](https://github.com/coralogix/custom-traces-examples/tree/master/java) |