IBM Cloud Docs
Frequently asked questions (FAQs)

Frequently asked questions (FAQs)

Frequently asked questions about IBM Log Analysis.

As of 28 March 2024 the IBM Log Analysis and IBM Cloud Activity Tracker services are deprecated and will no longer be supported as of 30 March 2025. Customers will need to migrate to IBM Cloud Logs, which replaces these two services, prior to 30 March 2025. IBM Cloud Logs will become generally available during the summer of 2024 in Frankfurt and Madrid with day-one support for EU-managed controls. The service will continue its worldwide multizone region (MZR) roll-out through 3Q2024.

Where can I find the list of Cloud services that send logs?

You can find the list of Cloud services that generate logs in the following documentation topic: Cloud services.

Where can I find details about the logs that a Cloud service generates?

You can access more information about the logs that each Cloud service generates from the following documentation topic: Cloud services. For each Cloud service, you can link to the logging topic specific to a Cloud service where you can get more information.

Where can I find the logs that a Cloud service generates?

First, you must check whether you have enabled Platform logs in the location where your Cloud service is available.

Then, check the Cloud services by location documentation to find out the location where the logs are available for analysis.

How do I configure archiving for my instance?

To configure archiving see Archiving events to IBM Cloud Object Storage.

How do I access the logging web UI? I cannot see the logging instance in the Observability page.

To lauch the logging web UI, complete the following steps:

  1. Check that you have IAM permissions to view the logging instances through the Logging dashboard. You must have viewer platform role permissions for the IBM Log Analysis service. Learn more about managing IAM policies and access groups.
  2. Launch the logging web UI.

How do I reset an ingestion key?

An ingestion key can be reset or new ones created in the logging web UI or using the API. You can have a maximum of 10 ingestion keys active at the same time in a logging instance.

Learn more about resetting using the UI or resetting using the API.

How can I get the ID of a logging instance?

To get the ID of a logging instance, run the following command:

ic resource service-instance <INSTANCE_NAME>

To get the name of the logging instance, run the following command ibmcloud resource service-instances --all-resource-groups.

Can I import archived data into the UI?

Archived data cannot be imported to be searched or used in the IBM Log Analysis UI.

Use the IBM Cloud Data Engine service to query archive data.

Why can't I create an API key?

If you are unable to create an API key it could be because you are not authorized to do so.

Make sure your ID has the User API key creator permission enabled for the IAM service` as described here.

How can I determine the version of the logging agent that is installed?

The logging agent version that is installed is returned by running logdna-agent -V. You might need to run this command from the directory where the agent is installed.

Can I control the ingested log lines so I can control my service cost?

You can control the volume of log lines that you ingest. Controlling the log lines helps you control your Log Analysis service cost. Logs that are filtered out (excluded) are not archived and are not available for search. You do not pay for log lines that are filtered out.

There are different ways in which you can filter out logs sent to Log Analysis:

  • You can configure the agent to drop logs before sending them to the Log Analysis service.

  • If you send logs to the Log Analysis service, you can define exclusion rules to drop logs before they are stored for search.

    • You can drop the log lines entirely and not see them at all through the UI.

    • You can view the log lines in the UI, but you cannot search on them. However, you can define views and alerts based on the data from these logs.

  • You can also configure usage quotas and define conditional usage quota exclusion rules.