Note You can collect container logs from multiple self-managed Kubernetes clusters to the same Log Service project only if the Kubernetes clusters reside in the same region. For more information, see Create a RAM user and authorize the RAM user to access Log Service. We recommend that you use the AccessKey pair of a RAM user and attach the AliyunLogFullAccess policy to the RAM user. The AccessKey secret of your Alibaba Cloud account. The AccessKey ID of your Alibaba Cloud account. For more information, see Obtain the ID of the Alibaba Cloud account to which Log Service belongs. For more information, see Supported regions. For example, the ID of the China (Hangzhou) region is cn-hangzhou. The ID of the region where your project resides. For example, if the project name is k8s-log-custom-sd89ehdq, set the value to sd89ehdq. The part that is specified after k8s-log-custom- in the name of your project. You can configure the parameters based on your business requirements. The following table describes the parameters that are included in the preceding command. alicloud-log-k8s-custom-install.sh your-project-suffix region-id aliuid access-key-id access-key-secret On the Logs and Monitoring tab, find logtail-ds and click Install.In the left-side navigation pane of the page that appears, choose Operations > Add-ons.On the Clusters page, find and click the cluster in which you want to install Logtail components.In the left-side navigation pane, click Clusters.For more information, see Configure the ID of an Alibaba Cloud account as a user identifier. If your ACK cluster and Log Service belong to different Alibaba Cloud accounts, you must configure the ID of the Alibaba Cloud account to which your Log Service belongs as a user identifier for your cluster.If your ACK cluster is a dedicated Kubernetes cluster or a managed Kubernetes cluster, you can follow the instructions that are provided in this section to install Logtail components in your cluster.įor information about how to collect text logs and standard output (stdout) from containers in a serverless Kubernetes (ASK) cluster, see Use Log Service to collect application logs.Select the resources of the app that should forward logs to the provider.Ĭlick the Add Log Destination button to enable remote logging for the provider.Token: Create a RSyslog source in Logtail and use the generated token.Endpoint: Provider endpoint where App Platform forwards the logs.Select the provider from the dropdown list.Įnter the following values for your specific provider: Log Destination Type: List of log service providers. ), spaces ( ), and forward slash ( /), anywhere except the start or end of the name Single ( ') and double quotes ( "), only at the start or end of the name.Alphanumeric characters, both uppercase or lowercase.This name must be between 2 and 42 characters long and may only use the following characters: Name: Name of the provider being configured. In the Add Log Destination dialog box, specify the following information: In the Log Forwarding section, click Edit and then click the Add Destination button. To configure log forwarding, go to the Apps section of the control panel, click on your app, and click on the Settings tab. Forwarding logs does not count towards application’s bandwidth usage.Ĭurrently, App Platform supports log forwarding to Papertrail, Datadog, and Logtail. This allows you to use the provider to search, index and retain the logs. In addition to viewing basic logs in App Platform, you can forward application runtime logs to external log management providers. App Platform is a Platform-as-a-Service (PaaS) offering that allows developers to publish code directly to DigitalOcean servers without worrying about the underlying infrastructure.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |