> ## Documentation Index > Fetch the complete documentation index at: https://gcore-doc-1894.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Configure logging and view logs Managed Logging collects logs from infrastructure components, delivers them to Kafka topics, and makes them searchable in OpenSearch Dashboards. Select the region where logs will be stored. Logging may be unavailable in some regions. Select the region that is geographically closest to the equipment. In the **Cloud** menu, navigate to **Managed Logging** and click **Set up Managed Logging**. A "Create namespace" dialog appears. A *namespace* is a prefix applied to all topic names in the region. Previously, Managed Logging automatically generated a non-human-readable namespace string (e.g., `cbc25c71af8d4f7ca6cbbcdc5a4d68fe`). Human-readable namespaces are now supported (e.g., `namespace123`), which produces topic names in the format `namespace123.topic-name`. A human-readable namespace can only be created for a new project that does not already have a default namespace assigned. Once created, the namespace name cannot be changed. Enter the namespace name according to the following restrictions: * Lowercase Latin letters and digits can be used * Underscores and spaces are prohibited * Length is between 2–32 characters * The name must be unique for the destination region. If it is already used, the system will suggest a different name. Click **Create**. Create namespace dialog In the **Topics** section, click **Create topic**, enter a name, set the retention period, and click **Save**. Gcore automatically creates an index pattern for the topic in OpenSearch Dashboards using "@timestamp" as the time field. Logging page showing the Topics section with a created topic Click **Generate credentials** in the upper-right corner. A warning dialog appears — click **Confirm** to proceed. A "Credentials" dialog shows a login (the namespace name) and password for the storage. Save the credentials immediately — they cannot be retrieved after closing the window. Use these credentials to authenticate log shippers that send logs to Managed Logging. If the credentials are lost, click **Generate credentials** again to generate a new pair. The previous credentials are deactivated automatically. Update the credentials in the settings of the installed log shippers. If Managed Logging is used in multiple regions, each region has separate storage and requires its own credentials. Select a log shipper (e.g. [Fluent Bit](/cloud/logging-as-a-service/install-a-log-shipper/install-and-configure-fluent-bit), [Filebeat](/cloud/logging-as-a-service/install-a-log-shipper/install-and-configure-filebeat), or [Logstash](/cloud/logging-as-a-service/install-a-log-shipper/install-and-configure-logstash)) that supports Kafka output. Configure the log shipper with the Kafka endpoint, credentials generated in step 4, and target topic name `.`. To find the Kafka endpoint, navigate to the Logging page and open the **Kafka endpoint** tab in the **How to use Managed Logging** section. Log message size is max 1 MB in text/JSON format, limited to 225 fields. After the log shipper is configured, logs flow automatically from the device to the Kafka topic, and then to OpenSearch for indexing. The pre-created index pattern uses "@timestamp" as the time field. If the log shipper sends a field named `@timestamp` in each log record — which most shippers do by default — no additional configuration is required in OpenSearch. If the logs use a different field name for the timestamp, a custom index pattern must be created after signing in to OpenSearch Dashboards. Navigate to OpenSearch Dashboards using the URL from the **Dashboards** field under the **OpenSearch endpoints** tab on the Logging page. Logging page showing OpenSearch endpoints tab with the Dashboards URL Log in using the credentials generated in step 4. OpenSearch Dashboards login page On first login, a dialog prompting tenant selection appears. Select **Private** and click **Confirm** to proceed. OpenSearch Dashboards uses index patterns to determine which indices to display in Discover. Gcore automatically creates an index pattern for each topic using "@timestamp" as the time field. If that matches the timestamp field in the logs, the setup is complete — proceed to step 7. If the logs use a different timestamp field, create a custom index pattern before viewing logs. **Navigate to Index patterns.** Click **Manage** in the upper-right corner of the home page, then select **Index patterns** from the left menu. OpenSearch Dashboards home page with Manage link in the upper-right corner **Delete the pre-created pattern.** Click the existing pattern name in the list to open it, then click the delete icon in the upper-right corner and confirm. **Open the creation form.** Click **+ Create index pattern** in the upper-right corner. Index patterns management page with Create index pattern button Logs are stored in an index that shares the name of the topic. The index pattern is a filter that tells OpenSearch Dashboards which index to display in Discover. **Enter the pattern name.** In the **Index pattern name** field, enter the namespace created in step 2, followed by a dot (.) and the topic name from step 3, followed by an asterisk (\*). If the namespace is `mylogging1` and the topic is `my-app-logs-1`, enter `mylogging1.my-app-logs-1*`. Click **Next step** to proceed. Create index pattern form with the pattern entered **Select the timestamp field.** Select the timestamp field from the dropdown list, and click **Create index pattern**. To view logs, navigate to the main menu and select **Discover**.