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
| name | Yes || Name used to register Log4j Appender |
91
-
| apiKey | Yes || API key for authenticating with New Relic's logging service |
92
-
| apiUrl | Yes || URL for New Relic's log ingestion API |
93
-
| logType | No | "muleLog" | Type of log being sent |
94
-
| applicationName | Yes || Name of the application generating the logs |
95
-
| batchSize | No | 5000 | Maximum number of log entries to batch together before sending to New Relic |
96
-
| maxMessageSize | No | 1048576 | Maximum size (in bytes) of the payload to be sent in a single HTTP request |
97
-
| flushInterval | No | 120000 | Interval (in milliseconds) at which the log entries are flushed to New Relic|
98
-
| customFields | No || Add extra context to your logs with custom fields, represented as comma-separated name-value pairs.|
99
-
| mergeCustomFields | No | false | (Default: false) All custom fields will be available as `custom.field1`, `custom.field2` else `field1` , `field2` will be available as the main attributes |
100
-
| maxRetries | No | 3 | Maximum number of retry attempts for sending logs. If logs cannot be sent successfully within the specified retries, they will be discarded. |
101
-
| timeout | No | 30000 | Connection timeout (in milliseconds) for HTTP requests to New Relic's logging service. Adjust based on network conditions and server response times. |
102
93
94
+
| Parameter | Required? | Default Value | Description |
-**Purpose**: Formats logs as JSON objects for structured logging.
127
+
-**Example**:
128
+
```xml
129
+
<JsonLayoutcompact="true"eventEol="true"/>
130
+
```
131
+
-**Use Case**: Suitable for integration with log management systems.
132
+
133
+
### Choosing Layout
134
+
135
+
-**PatternLayout**: For text-based logs.
136
+
-**JsonLayout**: For structured, machine-readable logs.
137
+
138
+
---
104
139
105
140
## Custom Fields [ v1.0.1 + ]
106
141
Custom fields provide a way to include additional custom data in your logs. They are represented as comma-separated name-value pairs. This feature allows you to add more context to your logs, making them more meaningful and easier to analyze.
107
142
108
143
## Configuring Custom Fields as Subfields of Custom Fields [v1.0.3+]
109
144
Starting from version 1.0.3, a new configuration parameter `mergeCustomFields` has been added. By default, all custom fields will be available as subfields under the `custom` field (e.g., `custom.field1`, `custom.field2`). If `mergeCustomFields` is set to `true`, custom fields will be available as main attributes (e.g., `field1`, `field2`).
110
145
111
-
146
+
## Configuring queueCapacity and connPoolSize [v1.0.6+]
147
+
Starting from version 1.0.6, the queueCapacity and connPoolSize parameters are exposed to allow for fine-tuning of the appender's performance, especially under high load conditions. These parameters help manage the flow of log data and the efficiency of network connections.
0 commit comments