How newrelic/newrelic-azure-functions works
New Relic Azure Functions collects logs from Azure Event Hubs and Blob Storage, normalizes and enriches them, then compresses and forwards them to New Relic Logs. The principal runtime path is registered source handler → shared processing in LogForwarder/index.js → New Relic. The README also documents ARM templates for automating deployment, represented as a separate capability. The source excerpt shows the shared processing and send path; the individual template behavior is not sampled, so no deployment-flow links are inferred.
Main entry points: index.js Shared Handler
Components 14
Log Forwarders
- Event Hub Handler
LogForwarder/index.js - Blob Handler
LogForwarder/index.js
Log Processing
- Shared Handler
LogForwarder/index.js - Parse and Transform
LogForwarder/index.js - Add Metadata
LogForwarder/index.js - Add Timestamps
LogForwarder/index.js - Compress and Send
LogForwarder/index.js
Deployment Templates
- Blob ARM Template
armTemplates/azuredeploy-blobforwarder.json - Event Hub ARM Template
armTemplates/azuredeploy-eventhubforwarder.json - Activity Log Bicep
bicep/activityLogConfiguration.bicep - Event Hub Bicep
bicep/azuredeploy-eventhubforwarder.bicep
Other components
- Azure Event Hubs
- Azure Blob Storage
- New Relic Logs API
Connections 9
- Azure Event Hubs → Event Hub Handler: provides logs
README.md - Event Hub Handler → Shared Handler: invokes
LogForwarder/index.js - Azure Blob Storage → Blob Handler: provides logs
README.md - Blob Handler → Shared Handler: invokes
LogForwarder/index.js - Shared Handler → Parse and Transform: transforms
LogForwarder/index.js - Shared Handler → Add Metadata: adds metadata
LogForwarder/index.js - Shared Handler → Add Timestamps: adds timestamps
LogForwarder/index.js - Shared Handler → Compress and Send: sends payload
LogForwarder/index.js - Compress and Send → New Relic Logs API: posts logs
LogForwarder/index.js