| copyright | lastupdated | keywords | subcollection | ||
|---|---|---|---|---|---|
|
2020-07-01 |
LogDNA, IBM, Log Analysis, logging, config agent |
Log-Analysis-with-LogDNA |
{:new_window: target="_blank"} {:shortdesc: .shortdesc} {:screen: .screen} {:pre: .pre} {:table: .aria-labeledby="caption"} {:codeblock: .codeblock} {:tip: .tip} {:download: .download} {:important: .important} {:note: .note}
{: #control_usage}
In {{site.data.keyword.la_full_notm}}, you can control the data that is collected and available for analysis through a LogDNA instance. You can define exclusion rules in the UI that apply to data collected in that instance. You can also configure LogDNA agents and customize them to collect and forward specific log data. In addition, you can define an alert that is triggered when the data usage threshold that you define for that LogDNA instance is reached. {:shortdesc}
{: #control_usage_agent}
You can stop logs from being forwarded to your logging instance by customizing the LogDNA agent to exclude any files that you do not want the LogDNA agent to monitor.
- By default, the agent monitors all files with extension .log, and extensionless files under /var/log/.
- You must configure the EXCLUDE parameter in the LogDNA agent configuration file to exclude files that are located in any of the paths that are defined through the logdir parameter.
- To define the files that you want to exclude, you can separate multiple files by using commas. You can use glob patterns. You can also configure specific files.
{: #control_usage_rule}
You can configure exclusion rules through the LogDNA web UI to stop logs from counting against your data usage quota and from being stored for search. For example, you might want to collect and forward all logs from a source to a LogDNA instance. However, you might be interested in a subset of those logs such as error logs.
Logs that are excluded do not count towards your data usage quota. Also, logs that match the exclusion rule are not archived. {: note}
When you exclude logs through an exclusion rule, you can choose to Preserve these lines for live-tail and alerting. When you check this option, log lines that match the exclusion rule are shown through the live tail and you can set up an alert for that data.
{: #control_usage_alert}
In a {{site.data.keyword.la_full_notm}} instance, you can define an alert to notify when the data usage in the instance reaches the data usage threshold that you set for the instance. {:shortdesc}
Complete the following steps to configure an alert that informs you when you reach a specific data volume in the instance:
-
Select the Settings icon
. Then select Usage.In the Dashboard section, you can see your data usage.
-
Define a Usage Alert to set the threshold for data usage in the instance. When the threshold is reached, you are notified. Enter a value to set the data usage threshold.
-
In the Add recipient section, enter one or more emails where the notification will be sent.
