Bring-Your-Own Log Aggregation Examples for IQ Server HA
Bring-Your-Own Log Aggregation Examples for IQ Server HA
The IQ Server HA Helm chart supports a log-aggregator-agnostic model. The following reference examples show how to collect IQ Server HA log files from the shared cluster log directory and forward them using an external log aggregation solution.
These examples are reference implementations. You may use a different log aggregation solution that suits your environment.
Available Examples
The IQ Server HA Helm chart provides the following examples:
| Example | Description |
|---|---|
| Fluent Bit | Collects IQ Server HA log files from the shared cluster log directory. |
| Datadog | Collects IQ Server HA log files from the shared cluster log directory and forwards them to Datadog. |
Refer to the IQ Server HA Helm chart examples directory for the current example configuration files.
Log File Location
By default, IQ Server HA log files are written under:
/sonatype-work/clm-cluster/log/
Log filenames include the pod name as a prefix, for example:
<pod-name>-clm-server.log
Log Files
Each pod running IQ Server generates the following log files:
| Log file | Description |
|---|---|
<pod-name>-clm-server.log |
Application log |
<pod-name>-request.log |
Request log |
<pod-name>-audit.log |
Audit log |
<pod-name>-policy-violation.log |
Policy violation log |
<pod-name>-stderr.log |
Stderr log |
Example Architecture
In the reference examples, IQ Server pods write log files to the shared cluster log directory. A customer-managed log aggregation component reads those files and forwards them to the configured output.
The Fluent Bit and Datadog examples use the same general pattern:
- IQ Server pods write logs to
/sonatype-work/clm-cluster/log/. - Fluent Bit reads the IQ Server HA log files from that location.
- Fluent Bit processes the log files.
- Fluent Bit forwards the logs to the configured output.
Extending to Other Log Aggregation Solutions
You can use another log aggregation solution instead of the provided Fluent Bit or Datadog examples.
When adapting the examples for another solution:
- Collect logs from
/sonatype-work/clm-cluster/log/. - Use the pod-prefixed log filenames generated by IQ Server HA.
- Configure your log aggregation solution to process the IQ Server HA log files required by your environment.
- Validate the configuration in your environment before relying on it for log collection.
Upgrade Considerations
Customers upgrading to v200 or later must remove any fluentd.* or cloudwatch.* Helm chart overrides previously used with bundled Fluentd configurations.
If iq_server.config includes custom log file paths, update those paths to write under /sonatype-work/clm-cluster/log/.