Logging for HA
Logging for HA
Starting in v200, the IQ Server HA Helm chart no longer bundles Fluentd for log aggregation. Customers are responsible for providing and managing their own log aggregation solution for HA deployments.
IQ Server pods continue to generate local log files that can be collected by an external log aggregation solution. By default, log files are written under /sonatype-work/clm-cluster/log/.
Refer to the IQ Server Helm Chart (under the section "Logging") for details on configuring log file locations and integrating external log aggregation solutions.
Log filenames include the pod name as a prefix, for example, <pod-name>-clm-server.log. 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 |
External Log Aggregation
Customers can integrate IQ Server HA deployments with external log aggregation solutions such as Fluent Bit, Datadog, CloudWatch, or Loki.
Log aggregation is optional and does not affect core IQ Server functionality.
The IQ Server HA Helm chart provides Fluent Bit and Datadog reference examples for collecting IQ Server HA log files from the shared cluster log directory. These examples are reference implementations. You may use a different log aggregation solution that suits your environment.
For reference examples using Fluent Bit and Datadog, see Bring-Your-Own Log Aggregation Examples for IQ Server HA.
Note
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/.
Refer to Configuring Logging for more details.