Collecting logs for BMC Helix Log Analytics
Data is collected in BMC Helix Log Analytics with the help of connectors and integrations. In integrations, you define the hosts from which you want to collect logs, fiitering details, and the log expressions present in your logs. Before collecting logs, identify your monitoring requirements—the applications and files from which you want to collect logs. To collect logs, connectors require parsing formats based on which logs are parsed while collection such as Apache, Apache error, and so on. For more information, see Downloading-and-installing-connectors.
Use integrations and connectors to collect logs for analysis. Integration capabilities and connector management is provided in BMC Helix Developer Tools. Use the different connector types to collect application logs from various sources. For more information, see Downloading-and-installing-connectors.
The connector requires parsing formats based on which logs are parsed while collection such as Apache, Apache error, and so on. You can also define which log messages you want to include or exclude by using the grep condition. For more information about these parsing formats and grep condition, see Logs parsing and filtering.
The following table lists the log collection options:
Option | Description | Reference |
|---|---|---|
Configure logs from file | Use this integration to collect log files from different applications. You can use different connector types depending on the environment where the application is deployed. | |
Amazon Web Services | Use this integration to collect application logs from Amazon Web Services. | |
Kubernetes | Use this integration to collect application logs from Kubernetes clusters. |
The following image shows the integrations available to collect logs:
