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
Logs sent to NR via this lambda are not related to any specific APM. Is there a way for this lambda to set the appropriate entity.guid, entity.guids, and entity.name fields in the log JSON so that logs may be related/tied to a specific APM? (I believe these fields would accomplish that linking?)
(I understand using an infrastructure agent typically accomplishes this, though we have reasons for shipping logs separately)
The text was updated successfully, but these errors were encountered:
The New Relic PHP Agent team has just released https://github.com/newrelic/newrelic-php-agent/releases/tag/v10.13.0.2 which does allow us to decorate logs being forwarded by an external solution (e.g. from cloudwatch using this lambda) with the correct entity.* attributes which will link logs to the correct APM.
This NR_TAGS env var seems it would also accomplish this linking, but would require one lambda running per application, e.g. as a sidecar container running along side the application container
Hello,
Logs sent to NR via this lambda are not related to any specific APM. Is there a way for this lambda to set the appropriate
entity.guid
,entity.guids
, andentity.name
fields in the log JSON so that logs may be related/tied to a specific APM? (I believe these fields would accomplish that linking?)(I understand using an infrastructure agent typically accomplishes this, though we have reasons for shipping logs separately)
The text was updated successfully, but these errors were encountered: