| copyright |
|
||
|---|---|---|---|
| lastupdated | 2024-12-06 | ||
| keywords | |||
| subcollection | cloud-logs |
{{site.data.keyword.attribute-definition-list}}
{: #getting-started}
{{site.data.keyword.logs_full}} is a scalable logging service that persists logs and provides users with capabilities for querying, tailing, and visualizing logs. {: shortdesc}
Logs are comprised of events that are typically human-readable and have different formats, for example, unstructured text, JSON, delimiter-separated values, key-value pairs, and so on. The {{site.data.keyword.logs_full_notm}} service can manage general purpose application logs, platform logs, or structured audit events. {{site.data.keyword.logs_full_notm}} can be used with logs from both {{site.data.keyword.cloud_notm}} services and customer applications.
The following steps guide you in creating an {{site.data.keyword.logs_full_notm}} service instance, reviewing the UI, and sending logs to the service instance. These steps will let you create an environment for evaluation purposes only.
{: #gs-prereqs}
You must have a user ID that is a member or an owner of an {{site.data.keyword.cloud_notm}} account. To get an {{site.data.keyword.cloud_notm}} user ID, go to: Registration{: external}.
{: #gs-iam}
To access and manage the {{site.data.keyword.logs_full_notm}} service, users and service IDs must be assigned access policies. An access policy maps a user or a service ID to certain IAM roles where these IAM roles define the actions that the user or the service ID can do with the {{site.data.keyword.logs_full_notm}} service.
Follow the steps in Granting access to {{site.data.keyword.logs_full_notm}} service to set up access to the {{site.data.keyword.logs_full_notm}} service.
Step 2. Creating {{site.data.keyword.cos_full_notm}} buckets or using an existing {{site.data.keyword.cos_full_notm}} buckets
{: #gs-creating-cos-bucket}
You need two dedicated {{site.data.keyword.cos_full_notm}} buckets that will be used by your {{site.data.keyword.logs_full_notm}} service instance to store log artifacts.
For more information on buckets, see Configuring buckets for long term storage and search.
Follow the steps in Create some buckets to store your data to create new {{site.data.keyword.cos_full_notm}} buckets if you do not already have buckets. If you already have {{site.data.keyword.cos_full_notm}} buckets that you will use with {{site.data.keyword.logs_full_notm}} you can skip this step.
{: #gs-creating-instance}
Next, create an {{site.data.keyword.logs_full_notm}} service. An {{site.data.keyword.logs_full_notm}} instance is created using the {{site.data.keyword.cloud_notm}} catalog.
Follow the steps in Provisioning an instance to set up an {{site.data.keyword.logs_full_notm}} instance.
{: #gs-access-ui}
Once you instance is provisioned, you can explore the {{site.data.keyword.logs_full_notm}} UI.
-
Launch the {{site.data.keyword.logs_full_notm}} UI. {: #launch-ui}
-
Click the Explore logs icon
> Logs.
When initially provisioned, you might not see data flowing to the instance, so all dashboards and views might be blank. {: note}
{: #gs-route-logs}
You can send {{site.data.keyword.cloud_notm}} platform data, and application, infrastructure, and operational logs to the {{site.data.keyword.logs_full_notm}} instance.
- Use the {{site.data.keyword.logs_routing_full_notm}} service to route logs from your IBM Cloud account to your chosen target. For more information, see Getting started with {{site.data.keyword.logs_routing_full_notm}}.
- Use {{site.data.keyword.atracker_full_notm}} to configure how to route auditing events, both global and location-based event data, in your IBM Cloud account. For more information, Getting started with {{site.data.keyword.atracker_full_notm}}.
- Use the {{site.data.keyword.agent}} to send data to a {{site.data.keyword.openshiftlong_notm}} cluster. For more information, see Deploying the Logging agent on OpenShift using a Helm chart.
- Use the {{site.data.keyword.agent}} to send data to an {{site.data.keyword.containerlong_notm}} cluster. For more information, see Deploying the Logging agent on Kubernetes using a Helm chart.
- Use the {{site.data.keyword.agent}} to send data to a Linux server. For more information, see Managing the {{site.data.keyword.agent}} for Linux.
- Use the {{site.data.keyword.agent}} to send data to a Windows server. For more information, see Managing the {{site.data.keyword.agent}} for Windows.
{: #gs-cleaning}
After you have evaluated {{site.data.keyword.logs_full_notm}} and you want to clean up your environment, you can delete your instance to remove the {{site.data.keyword.logs_full_notm}} service you created for evaluation.