feat(transports/newrelic): add New Relic Log API transport#89
Merged
Conversation
Wraps transports/http with New Relic-specific defaults: - Zone-aware intake URL (US, EU) - Api-Key / X-License-Key header auth - NDJSON encoder yielding timestamp, message, loglevel, optional hostname - AllowInsecureURL flag for non-https URL override (matches datadog pattern) 20 tests covering encoder shape, level mapping, config validation, and goroutine leak detection. See https://docs.newrelic.com/docs/logs/log-api/introduction-log-api/
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
New
transports/newrelictransport shipping log entries to the New Relic Log API as NDJSON.Wraps
transports/httpwith New Relic-specific defaults:ZoneUS,ZoneEU)Api-Keyheader fromConfig.APIKeyX-License-Keyheader fromConfig.LicenseKeytimestamp,message,loglevel, optionalhostnameAllowInsecureURLopt-in for on-prem forwardersFollows the exact pattern established by
transports/datadog.What Changed
New module:
go.loglayer.dev/transports/newrelic/v2Config:APIKey(required),LicenseKey(optional),Zone(IntakeZone),URLoverride,Hostname,AllowInsecureURL,HTTPoverridesloglevel, notlevel;timestampin RFC3339 with milliseconds)debug; Fatal and Panic map tocriticalConfig.String()redacts both keys; both taggedjson:"-"/transports/newrelic, sidebar entry, transport-list catalog update, whats-new entry