Preparing for BMC Helix logging

You can deploy

Some content is unavailable due to permissions.

Some content is unavailable due to permissions.

Fluentd needs the following privileges:

• Kubernetes cluster
  • PodSecurityPolicy - The installer creates the PodSecurityPolicy administrator with the host path enabled and the root runAsUser and runAsGroup settings as shown in the psp_fluentd.yamlfile.
  • ClusterRole and ClusterRoleBinding - The installer creates the ClusterRole and ClusterRoleBinding objects with the rules that are mentioned in the clusterole_rolebinding_fluentd.yaml file.

Perform the following tasks before deploying TrueSight Automation Console:

• In the tsac-deployment-manager-<release_version>/configs/deployment.config file, change the value of the BMC_HELIX_LOGGING parameter to yes as shown below:
  BMC_HELIX_LOGGING=yes

  Important

  If the value of the BMC_HELIX_LOGGING parameter is no, the TrueSight Automation Console supportability is limited, and the root cause analysis of an issue may not be possible.

• EFK collects logs from all namespaces in the cluster. If you are using separate namespaces for other applications in your cluster, the log file size increases. In the files shown in the following table, edit the default values of the ESLOG_MASTER_STORAGE_SIZE and ESLOG_DATA_STORAGE_SIZE parameters according to your deployment size:

  The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
  This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.For example, in the internal PSR, 180 GB of space was consumed in 24 hours for a single namespace. You can change these values based on the namespaces and applications in the cluster.

• Log retention is set to 90 days by default. You can configure the retention period. In the configs/default.config file, set the value in days for the ESLOG_RETINTION_PERIOD parameter.
  For example, to set the log retention for 30 days, set the ESLOG_RETINTION_PERIOD parameter as shown below:
  ESLOG_RETINTION_PERIOD=30