newrelic-telemetry-sdk-java
newrelic-telemetry-sdk-java copied to clipboard
Java library for sending telemetry data to New Relic
```groovy implementation ("com.newrelic.telemetry:telemetry-http-okhttp:0.16.0") implementation ("com.newrelic.telemetry:telemetry-core:0.16.0") ``` When we include the above dependencies in `build.gradle`, I get the following error. ``` error: module io.ballerina.observe.extension.newrelic reads package com.newrelic.telemetry from both telemetry.core and...
I am wring a code where I am sending data to new relic endpoint using TelemetryClient. But in case where batch to be scheduled cannot be allocated, the scheduler just...
This PR adds a configuration to enable batching in the Telemetry SDK. **What is batching?** The Java Telemetry SDK sends Metric and Event data to New Relic by using the...
Response codes 400, 403, 404, 405 and 411 are not handled separately by the BatchDataSender. Instead a common DiscardBatchException is thrown to handle these response codes. https://github.com/newrelic/newrelic-telemetry-sdk-java/blob/60fb68d4793da37b55d47b342c62f9c7f962ed13/telemetry-core/src/main/java/com/newrelic/telemetry/transport/BatchDataSender.java#L167 Also, is there...
User can provide Dispatcher(ExecutorService) to OkHttpClient, but TelemetryClient forcibly creates another one with `Executors.newSingleThreadScheduledExecutor` in constructor. (Migrate to Jira)
The backend API supports sending multiple batches in one payload. We should support that in the SDK. (Migrate to Jira)
## Description Update the Http Client. We're currently using OkHttp and need to update to use Apache HttpClient instead.
According to new relic docs, a 413 http status code is send when `The payload was too big. Payloads must be under 1MB (10^6 bytes).` Currently, BatchDataSender throws a RetryWithSplitException...