# OpenTelemetry custom logs Copy as Markdown[Open in ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fdocs-docusaurus.kinsta.page%2Fdeveloper-portal%2Fapis%2Fdata-ingestion%2Fopentelemetry-custom-logs.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[Open in Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fdocs-docusaurus.kinsta.page%2Fdeveloper-portal%2Fapis%2Fdata-ingestion%2Fopentelemetry-custom-logs.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.) Send your **custom logs** to Coralogix using our OpenTelemetry-compatible endpoint. ## Overview[​](#overview "Direct link to Overview") Custom logs can be delivered directly to the Coralogix OpenTelemetry-compatible ingress.:443 endpoint using any gRPC client, plain HTTP requests (OTLP/HTTP with JSON or binary protobuf payloads), or [OpenTelemetry SDKs](https://opentelemetry.io/docs/concepts/sdk-configuration/). The examples below guide you using gRPCurl, cURL (OTLP/HTTP with JSON), and the OpenTelemetry Java SDK. ## Prerequisites[​](#prerequisites "Direct link to Prerequisites") [Git](https://git-scm.com/) and [gRPCurl](https://github.com/fullstorydev/grpcurl) installed. ## Data model[​](#data-model "Direct link to Data model") The custom logs API implementation is based on the OpenTelemetry [logging specification](https://github.com/open-telemetry/opentelemetry-proto/blob/main/opentelemetry/proto/logs/v1/logs.proto). This ensures that our logging implementation adheres to industry best practices and can seamlessly integrate with other components and tools in the OpenTelemetry ecosystem. ### Example log[​](#example-log "Direct link to Example log") ``` { "resource_logs": [ { "resource": { "attributes": [ { "key": "cx.application.name", "value": { "string_value": "my-test-application" } }, { "key": "cx.subsystem.name", "value": { "string_value": "my-test-subsystem" } } ] }, "scope_logs": [ { "scope": { "name": "test" }, "log_records": [ { "time_unix_nano": "1665989944490035000", "severity_number": "SEVERITY_NUMBER_WARN", "severity_text": "WARN", "body": { "string_value": "Test log message" } } ] } ] } ] } ``` ## 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. * For the `` field, select the ingress.:443 endpoint that corresponds to your Coralogix [domain](https://docs-docusaurus.kinsta.page/user-guides/account-management/account-settings/coralogix-domain/.md) using the domain selector at the top of the page. * For the `` field, input your Coralogix [Send-Your-Data API key](https://docs-docusaurus.kinsta.page/user-guides/account-management/api-keys/send-your-data-api-key/.md). Assuming the example in the data model is saved as `logs.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 logs to Coralogix grpcurl -v -d @ \ -rpc-header 'Authorization: Bearer ' \ -proto opentelemetry-proto/opentelemetry/proto/collector/logs/v1/logs_service.proto \ -import-path opentelemetry-proto \ ingress.eu2.coralogix.com:443 \ opentelemetry.proto.collector.logs.v1.LogsService/Export \ < logs.json ``` Note Set the `time_unix_nano` field in the `logs.json` file to a timestamp that is within the last 24 hours. ## Sending data with cURL (OTLP/HTTP)[​](#sending-data-with-curl-otlphttp "Direct link to Sending data with cURL (OTLP/HTTP)") The same endpoint also accepts [OTLP/HTTP](https://opentelemetry.io/docs/specs/otlp/#otlphttp) requests on the `/v1/logs` path, with the payload encoded either as JSON (`Content-Type: application/json`) or as binary protobuf (`Content-Type: application/x-protobuf`). The JSON payload follows the [OTLP/JSON mapping](https://github.com/open-telemetry/opentelemetry-proto/blob/main/docs/specification.md#json-protobuf-encoding), which differs from the gRPCurl example above: * Keys are lowerCamelCase (`timeUnixNano`); original snake\_case proto field names are not valid and are ignored. * Enum fields are integers (for example, `severityNumber: 13` instead of `"SEVERITY_NUMBER_WARN"`). * 64-bit integers are decimal strings. Save the following example as `logs-http.json`: ``` { "resourceLogs": [ { "resource": { "attributes": [ { "key": "cx.application.name", "value": { "stringValue": "my-test-application" } }, { "key": "cx.subsystem.name", "value": { "stringValue": "my-test-subsystem" } } ] }, "scopeLogs": [ { "scope": { "name": "test" }, "logRecords": [ { "timeUnixNano": "1665989944490035000", "severityNumber": 13, "severityText": "WARN", "body": { "stringValue": "Test log message" } } ] } ] } ] } ``` Then send it to Coralogix: ``` curl -v "https://ingress.eu2.coralogix.com:443/v1/logs" \ -H 'Content-Type: application/json' \ -H 'Authorization: Bearer ' \ --data-binary @logs-http.json ``` Note Set the `timeUnixNano` field 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 logs to Coralogix. Others [SDKs](https://opentelemetry.io/docs/concepts/sdk-configuration/) may also be used. **STEP 1**. Add to your maven pom.xml the following libraries: ``` io.opentelemetry opentelemetry-sdk-logs io.opentelemetry opentelemetry-exporter-otlp-logs ``` **STEP 2**. Use the following code snippet to create and report a span: ``` SdkLoggerProvider loggerProvider = SdkLoggerProvider.builder() .addLogRecordProcessor(BatchLogRecordProcessor.builder( OtlpGrpcLogRecordExporter.builder() .setEndpoint("ingress.eu2.coralogix.com:443") .addHeader("Authorization", "Bearer ") .build() ).build()) .setResource(Resource.create(Attributes.of( AttributeKey.stringKey("cx.application.name"), "my-test-application", AttributeKey.stringKey("cx.subsystem.name"), "my-test-subsystem"))) .build(); Logger logger = loggerProvider.loggerBuilder("test").build(); logger.logRecordBuilder() .setSeverity(Severity.WARN) .setSeverityText("WARN") .setBody("Test log message") .emit(); loggerProvider.forceFlush(); ``` ## Limits & quotas[​](#limits--quotas "Direct link to Limits & quotas") Coralogix places a **hard limit of 10MB** of data to our OpenTelemetry [endpoints](https://docs-docusaurus.kinsta.page/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://docs-docusaurus.kinsta.page/integrations/coralogix-endpoints/.md) |