Configure the Application
Consistent naming across systems
Configure Data Privacy & Exclusions
Filtering sensitive values
Validate the Configuration
Checking telemetry after changes
Advanced Configuration
Tuning monitoring behavior
@germainapm/nodejs-monitoring package is already installed and initialized.
Configure the Node.js Data Source
Enable and configure the Node.js data source that GermainUX will monitor. Depending on the environment, the data source can identify information such as:- File path
- Host
- URI
- Application endpoint
- Monitored runtime

Configure the Application
Configure the Node.js application in GermainUX so collected telemetry is associated with the correct application. Use consistent application naming across:- Production
- Staging
- Development
- Application components
- Services

Configure Monitoring Frequency
Some Node.js monitoring components execute periodically. The default frequency is 60 seconds. Configure it using:Configure Asynchronous Correlation
By default, GermainUX correlates incoming HTTP requests with asynchronous outgoing HTTP requests. This supports tracing such as:Incoming HTTP RequestNode.js ProcessingOutgoing HTTP RequestDownstream Service
Disable asynchronous correlation when required:
Configure Data Distribution
GermainUX periodically sends collected telemetry to the GermainUX Server. Configure the maximum interval between transmissions using:- Sending or discarding telemetry
- Compression
- Maximum datapoints retained in memory
- Maximum flush interval
Configure Incoming HTTP Monitoring
Incoming HTTP monitoring is enabled by default. Control it using:Configure Outgoing HTTP Monitoring
Outgoing HTTP monitoring is enabled by default. Control it using:Configure Unhandled Exception Monitoring
Unhandled exception monitoring is enabled by default. Configuration supports:- Enable / disable monitoring
- Whether the Node.js process exits after an error
- Application callback when an error occurs
exitOnError carefully because changing it can affect normal Node.js error-handling behavior.
Configure Node.js Warning Monitoring
Node.js warning monitoring is enabled by default. Warnings generated by the Node.js process can be collected and analyzed by GermainUX. Control this capability using:- KPIs
- Dashboards
- Reports
- Alerts
- Trend analysis
Configure Unhandled Promise Rejection Monitoring
Unhandled Promise rejection monitoring is enabled by default. Control it using:Configure Multiple Promise Resolve / Rejection Monitoring
GermainUX also monitors when a Promise is resolved or rejected multiple times. This monitoring is enabled by default. Disable it using:Configure Event Loop Latency Monitoring
Event-loop latency monitoring is enabled by default. Disable it using:Configure Startup Monitoring
GermainUX automatically monitors Node.js startup duration. By default, startup duration is measured between the Node.js process startup and GermainUX initialization. Disable automatic startup monitoring using:Configure Exit Monitoring
Node.js process-exit monitoring is enabled by default. Disable it using:Configure Custom Transaction Monitoring
Use custom transactions to monitor important business or application operations. Start a transaction:ProcessOrderCustomerLookupGenerateInvoicePaymentRequestSubmitClaim
Configure Node.js Process Monitoring
By default, GermainUX monitors the Node.js process for:- CPU
- Memory usage
- Heap size
- Heap usage
Configure OS Resource Monitoring
GermainUX monitors CPU and memory usage of the server hosting the Node.js application. Disable it using:Configure Disk Monitoring
GermainUX monitors disk usage of the server hosting the Node.js application. Disable it using:Configure Default Context
Default context can be added to collected datapoints. Supported default dimensions include:- User
- System
- Application
- Application component
- Process
Configure GermainUX Logging
Logging is enabled atinfo level and above by default.
Configure logging using:
errorwarninfoverbosedebug
Configure Data Privacy & Exclusions
By default, captured telemetry is sent to GermainUX. Use field exclusions when data must be protected for security or privacy reasons. GermainUX supports: MaskReplace characters while optionally preserving length and whitespace. Anonymize
Hash the original value so it can still be correlated without retaining the original value. Exclude
Remove the captured value. Example:
- Session identifiers
- Request bodies
- Authentication information
- Tokens
- User information
- Personal information
- Application-specific confidential data
Configure KPIs
GermainUX provides preconfigured Node.js KPIs and supports custom KPIs. Examples include:- NodeJS Unhandled Promise Rejections
- NodeJS Warning
- HTTP response time
- Transaction duration
- Event-loop latency
- CPU usage
Show all 9
Show all 9
- Memory usage
- Heap usage
- Application exits

Configure SLAs
Define SLAs for Node.js KPIs requiring threshold-based monitoring. For example: HTTP Response Time > Threshold Event Loop Latency > Threshold Unhandled Promise Rejections > 0 CPU Usage > Threshold Transaction Duration > Threshold SLAs should reflect expected application behavior rather than using the same thresholds for every Node.js service.
Configure Categorization
Configure categorization rules to group Node.js telemetry into meaningful operational categories. Categorization can be used for:- Errors
- Warnings
- Transactions
- Application components
- Services
- Failure types
Configure Correlation
In addition to built-in asynchronous HTTP correlation, configure GermainUX correlation where Node.js telemetry should be associated with other monitored technologies. Examples:BrowserNode.jsAPI
MarkoJSNode.jsMySQL
Node.jsMuleSoftDownstream Service
Correlation allows teams to move across application layers during troubleshooting.
Configure Analytics Data Privacy
In addition to the Node.js collector-side exclusion rules, configure GermainUX privacy controls where collected telemetry needs additional handling within analytics. Privacy policies should remain consistent across Node.js and any correlated frontend, API, or database monitoring.Configure Alerts
Create alerts for Node.js conditions requiring operational attention. Examples include:- Unhandled exception
- Unhandled Promise rejection
- Node.js warning
- Unexpected process exit
- Slow HTTP request
- Slow transaction
- High event-loop latency
- CPU or memory threshold exceeded
- Conditions
- Thresholds
- Time windows
- Recipients
- Escalation behavior

Configure Automation
Node.js conditions can trigger GermainUX automation. For example:Node.js ConditionKPISLAAlert / Action
Automation can include:
- Notifications
- Reports
- Scripts
- HTTP actions
- Incident workflows
- Other configured operational actions
- Remediation actions where appropriate
Configure Dashboards
Use an existing Node.js dashboard or create a custom dashboard. Dashboards can present:- Application health
- Errors and warnings
- HTTP performance
- Transaction performance
- Event-loop latency
- Promise-related problems
Show all 11
Show all 11
- CPU and memory
- Heap utilization
- OS resources
- Disk utilization
- SLA status
Configure Automated Reports
Enable an existing report or create a Node.js-specific automated report. Reports can summarize:- Availability
- Errors
- Application performance
- Transaction performance
- Resource utilization
- SLA violations
- Trends over time
Validate the Configuration
After changing Node.js configuration, execute representative application activity and verify:- Application and data source association
- Incoming HTTP monitoring
- Outgoing HTTP monitoring
- Async correlation
- Unhandled exceptions
- Node.js warnings
Show all 21
Show all 21
- Promise rejections
- Event-loop latency
- Startup and exit events
- Custom transactions
- Process CPU and memory
- Heap telemetry
- OS resources
- Disk usage
- Privacy and exclusion rules
- KPIs
- SLA evaluation
- Categorization
- Correlation
- Alerts and automation
- Dashboards and reports
Advanced Configuration
GermainAPMConfiguration exposes additional controls for Node.js monitoring.
The main configuration areas include:
servicesUrlmonitoringloggingdatapointsdefaultsexclusions
- Monitoring frequency
- Asynchronous correlation
- Unhandled exceptions
- Incoming HTTP
- Outgoing HTTP
- Startup
Show all 14
Show all 14
- Process resources
- OS resources
- Disk
- Node.js warnings
- Unhandled Promise rejections
- Event-loop latency
- Process exit
- Multiple Promise resolutions
Get More Information
Magento environments can vary significantly depending on storefront customization, extensions, integrations, infrastructure, and security requirements. The GermainUX team can help configure the appropriate monitoring scope, privacy controls, analytics, alerts, and automation for your Magento environment. Please contact us for any help.Get Help
Contact GermainUX Support
The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.
Can't find what you need?
Search all GermainUX docs with Ctrl + K, or use the feedback buttons at the bottom of this page to tell us what is missing.
The content of this document is proprietary to GERMAIN SOFTWARE.

