You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This key is still in use but we highly recommend using the license key, which can be used for the same things and more.
when using SpanBatchSender.configurationBuilder or MetricBatchSender.configurationBuilder a special useLicenseKey parameter can be passed that indicates that the passed api key is either insights insert key or licence key.
technically this will result passing either "Api-Key" or "X-License-Key" respectively header in the request.
i will make MR for that
The text was updated successfully, but these errors were encountered:
* add a support for New Relic's licence key
- changes are compatible backwards
- extracted config parsing to the new file
- new `"licence-key"` can be passed
- added new tests
* remove apiKeyAndUseLicenseKey, because of tuple
* add license-key to the reference.conf
* Update reporters/kamon-newrelic/src/main/scala/kamon/newrelic/spans/SpanBatchSenderBuilder.scala
Co-authored-by: Mateusz Wójcik <[email protected]>
Co-authored-by: Mateusz Wójcik <[email protected]>
the NR documentation (chapter about keys) states that Insights insert key are deprecated / not recommended.
when using
SpanBatchSender.configurationBuilder
orMetricBatchSender.configurationBuilder
a specialuseLicenseKey
parameter can be passed that indicates that the passed api key is either insights insert key or licence key.technically this will result passing either
"Api-Key"
or"X-License-Key"
respectively header in the request.i will make MR for that
The text was updated successfully, but these errors were encountered: