Provisioning an instance
You can provision an instance of the IBM Cloud Logs service through the IBM Cloud catalog, and programmatically by using a terraform script or the Resource Controller API.
IBM Cloud Logs integrates with IBM Cloud Object Storage for long term storage of the data and for collection of metrics, and with IBM Cloud Event Notifications for triggering of alerts. Authorization between services is done by configuring IAM service to service authorizations in the account.
You can run Cloud Logs without a data bucket or a metrics bucket. However, features like TCO Optimizer to manage data thorugh different data pipelines at different costs, long term data querying or metrics related features would not be available.
There are limits for each provisioned instance. For more information, see Limits per instance.
Provisioning an instance through the Observability dashboard
To provision an instance from the Observability dashboard in the IBM Cloud, complete the following steps:
-
Log in to your IBM Cloud account.
After you log in, the IBM Cloud UI opens.
-
Click the Menu icon > Observability to access the Observability dashboard.
-
Click Logging > Instances. You might need to click the Cloud Logs tab to see your IBM Cloud Logs instances.
-
Click Create.
-
Select the required service for your instance.
-
Select the location where you plan to provision the instance.
-
Enter a name for the service instance.
-
Select a resource group.
By default, the default resource group is set.
Note: If you are not able to select a resource group, check that you have editing permissions on the resource group where you want to provision the instance.
-
Select the
Standard
service plan.By default, the Standard plan is set.
For more information about service plans, see Service plans and pricing.
-
Choose a retention plan. Valid values are
7 days
,14 days
,30 days
,60 days
or90 days
. -
Click Create.
After you provision an instance, the UI opens.
Provisioning an instance through the catalog
To provision an instance of IBM Cloud Logs through the IBM Cloud catalog, complete the following steps:
-
Log in to your IBM Cloud account.
After you log in, the IBM Cloud UI opens.
-
Click Catalog. The list of the services that are available in IBM Cloud opens.
-
To filter the list of services that is displayed, select the Logging and Monitoring category.
-
Click the IBM Cloud Logs tile.
-
Select the location where you plan to provision the instance.
-
Enter a name for the service instance.
-
Select a resource group.
By default, the Default resource group is set.
Note: If you are not able to select a resource group, check that you have editing permissions on the resource group where you want to provision the instance.
-
Select the
Standard
service plan.By default, the standard plan is set. For more information about service plans, see Service plans and pricing.
-
Choose a retention plan. Valid values are
7 days
,14 days
,30 days
,60 days
or90 days
. -
Click Create.
After you provision an instance, the UI opens.
Provisioning an instance through the CLI
To provision an instance of IBM Cloud Logs through the command line, complete the following steps:
-
[Pre-requisite] Installation of the IBM Cloud CLI.
For more information, see Installing the IBM Cloud CLI.
If the CLI is installed, continue with the next step.
-
Log in to the region in the IBM Cloud where you want to provision the instance. Run the following command: ibmcloud login
-
Set the resource group where you want to provision the instance. Run the following command: ibmcloud target
By default, the
default
resource group is set. -
Create the instance. Run the ibmcloud resource service-instance-create command:
ibmcloud resource service-instance-create NAME logs SERVICE_PLAN_NAME LOCATION -p '{"private_endpoints_only": PRIVATE_ENDPOINT}'
Where
NAME
is the name of the instanceSERVICE_PLAN_NAME
is the type of plan. Valid value is standard.LOCATION
is the region where the logging instance is created. To get the latest list of locations that are available for the IBM Cloud Logs service, see Locations.-
PRIVATE_ENDPOINT
is eithertrue
orfalse
. Iftrue
only private endpoints can be used to access the instance.Unless otherwise specified when provisioning an instance, the default is for the instance to be accessible by both public and private endpoints.
For example, to provision an instance with the standard plan that can be accessed only by private endpoints, run the following command:
ibmcloud resource service-instance-create my-instance logs standard us-south -p '{"private_endpoints_only": true}'
-
Next steps
IBM Cloud Logs integrates withIBM Cloud Object Storage for long term storage of the data and for collection of metrics, and with IBM Cloud Event Notifications for triggering of alerts. Authorization between services is done by configuring IAM service to service authorizations in the account.
After you provision the instance, you can:
- Attach a data bucket and a metrics bucket. For more information, see Configuring buckets.
- Configure an outbound integration. For more information, see Configuring an outbound integration to connect IBM Cloud Logs with IBM Cloud Event Notifications.
- Configure a log source by adding a logging agent. This agent is responsible for collecting and forwarding logs to your instance.