{"id":904,"date":"2023-02-20T01:47:00","date_gmt":"2023-02-20T01:47:00","guid":{"rendered":"https:\/\/blog.ngocha.biz\/?p=904"},"modified":"2023-02-20T01:47:00","modified_gmt":"2023-02-20T01:47:00","slug":"how-to-setup-and-push-serverapplication-logs-to-aws-cloudwatch","status":"publish","type":"post","link":"https:\/\/blog.ngocha.biz\/?p=904","title":{"rendered":"How To Push ec2 Logs to Cloudwatch [Logs And Metrics]"},"content":{"rendered":"

In this blog, I will show you how to push ec2 logs to Cloudwatch using the Cloudwatch agent. You can also send ec2 system metrics to cloudwatch.<\/p>\n

This article walks you through the steps involved in configuring the Cloudwatch agent on an ec2 instance and configuring it to push the logs and metrics generated by the applications & system services.<\/p>\n

Here is what you are going to learn in this blog.<\/p>\n

AWS Cloud Watch Agent Use Cases<\/h2>\n

AWS Cloudwatch logs service has the capability to store custom logs and process metrics generated from your application instances. Here are some example use cases for custom logs and metrics<\/p>\n

    \n
  1. Web server (Nginx, Apache, etc ) access or error logs can be pushed to Cloudwatch logs it acts as central log management for your applications running on AWS<\/li>\n
  2. Custom application logs (java, python, etc) can be pushed to cloudwatch and you can set up custom dashboards and alerts based on log patterns.<\/li>\n
  3. Ec2 instance metrics\/custom system metrics\/ app metrics can be pushed to cloudwatch.<\/li>\n<\/ol>\n

    Application Logs To AWS Cloudwatch Workflow<\/h2>\n

    You can send logs from any number of ec2 sources to Cloudwatch. All you need to have is a Cloudwatch agent running on your instance.<\/p>\n

    Here is what you have to do<\/p>\n

      \n
    1. Create a custom ec2 IAM role with Cloudwatch log write access<\/li>\n
    2. Install Cloudwatch logs ec2 agent<\/li>\n
    3. Configure log sources in the Cloudwatch agent configuration file.<\/li>\n
    4. Start the agent with the configuration file.<\/li>\n
    5. Validate logs in the Cloudwatch dashboard.<\/li>\n<\/ol>\n
      \n
      Note: <\/strong><\/b>In an actual project implemention the cloudwatch ec2 agent and configuration would be part of the AMI (Golden Image) or AMI packaging tool like packer<\/a>.<\/div>\n<\/div>\n
      \"Application
      Click to view in HD<\/span><\/figcaption><\/figure>\n

      Let’s get started with the setup.<\/p>\n

      Create an IAM role for Cloudwatch Agent<\/h2>\n

      To set up AWS custom logs, first, you need to create and add a custom ec2 IAM role to your instance. This IAM role will have policies with write access to the Cloudwatch service so that all the logs from ec2 instances can be shipped to Cloudwatch. <\/p>\n

      Before creating a role, you need to create a custom policy.<\/p>\n

      Step 1:<\/strong> Head over to AWS IAM –> Policies–> Create Policy<\/p>\n

      \"Create<\/figure>\n

      Step 2:<\/strong> Select the JSON option<\/p>\n

      \"\"<\/figure>\n

      Step 3:<\/strong> Copy the following content in the policy block. We are allowing the required permissions and the logs arn details. Read AWS arn detailed guide<\/a> to know more about arn.<\/p>\n

      \n
      {
      “Version”: “2012-10-17”,
      “Statement”: [
      {
      “Effect”: “Allow”,
      “Action”: [
      “logs:CreateLogGroup”,
      “logs:CreateLogStream”,
      “logs:PutLogEvents”,
      “logs:DescribeLogStreams”
      ],
      “Resource”: [
      “arn:aws:logs:*:*:*”
      ]
      }
      ]
      }<\/div>\n<\/div>\n

      On the next page, add a tag to the policy. Give a name, and description for your policy, and click Next<\/code><\/p>\n

      \"Cloudwatch<\/figure>\n

      On the next page, add a policy name, and description and click create policy.<\/p>\n

      \"create<\/figure>\n

      Once you create the policy, you need to create a role with the custom policy you have created.<\/p>\n

      Step 4:<\/strong> Head over to AWS IAM –> Roles –> Create Role and select options as shown below.<\/p>\n

      \"\"<\/figure>\n

      Step 5: <\/strong>From the filter, select “Customer Managed” and select the Policy <\/strong>you created in step 3.<\/p>\n

      \"\"<\/figure>\n

      Step 6: <\/strong>Next, enter a role name and create the role.<\/p>\n

      \"\"<\/figure>\n

      Add the Cloudwatch Role to the Instance<\/h2>\n

      Follow the steps given below to add the custom IAM role to the ec2 instance where you want to set up the cloud watch agent.<\/p>\n

        \n
      1. Head over to ec2 and select the instance in which you want to configure the custom logs.<\/li>\n
      2. Right-click for options and select Security<\/code> and then choose Modify IAM Role<\/code> option.<\/li>\n
      3. Select the custom cloud watch IAM role from the dropdown and save it.<\/li>\n<\/ol>\n

        Install Cloudwatch Logs Agent<\/h2>\n

        SSH into the ec2 instance and follow the steps given below.<\/p>\n

        Step 1:<\/strong> Head over to the Cloudwatch agent downloads page<\/a>. You can select region-wise packages as well.<\/p>\n

        Step 2: <\/strong>Download the appropriate agent installation file.<\/p>\n

        In my case it’s ubuntu. I am downloading the latest Ubuntu package and installing it.<\/p>\n

        \n
        wget https:\/\/s3.amazonaws.com\/amazoncloudwatch-agent\/ubuntu\/amd64\/latest\/amazon-cloudwatch-agent.deb sudo dpkg -i amazon-cloudwatch-agent.deb<\/div>\n<\/div>\n

        Redhat users,<\/p>\n

        https:\/\/s3.amazonaws.com\/amazoncloudwatch-agent\/redhat\/amd64\/latest\/amazon-cloudwatch-agent.rpm\nrpm -U amazon-cloudwatch-agent.rpm<\/code><\/pre>\n
        Configure Cloudwatch Agent<\/h2>\n
        After the installation, you can find all the cloudwatch agent-related config files and executables in the following location.<\/p>\n
        \/opt\/aws\/amazon-cloudwatch-agent<\/code><\/pre>\n
        Here is the tree structure of the files present in the directory.<\/p>\n
        \"AWS<\/figure>\n
        If you are just starting with a cloud watch agent, it is better to run the cloud watch agent wizard that helps you create the log agent configurations.<\/p>\n
        sudo \/opt\/aws\/amazon-cloudwatch-agent\/bin\/amazon-cloudwatch-agent-config-wizard<\/code><\/pre>\n
        It prompts you with all the agent-related questions. Execute the following command to start the wizard.<\/p>\n
        For the question, Do you want to store the config in the SSM parameter store?, select No.<\/p>\n
        The final config files get stored in the following location<\/p>\n
        \/opt\/aws\/amazon-cloudwatch-agent\/bin\/config.json<\/code><\/pre>\n
        If you want to collect the system metrics, install collected on your server.<\/p>\n
        sudo apt-get update -y\nsudo apt-get install collectd<\/code><\/pre>\n
        In my case, I am going to replace the default config.json<\/code> with a custom config.json<\/code> that collects the following logs and system metrics using collectd.<\/p>\n
          \n
        1. Cloudwatch agent logs<\/li>\n
        2. System logs from \/var\/log\/messages<\/li>\n
        3. Nginx access logs from \/var\/log\/nginx\/access.log<\/li>\n
        4. Nginx error logs from \/var\/log\/nginx\/error.log<\/li>\n<\/ol>\n
          \n
          Note: <\/strong><\/b>Install Nginx, if you want to follow the following configs for testing purposes. Or you can use you can replace the log locations with your applcation log path.<\/div>\n<\/div>\n
          Here is the final cloudwatch agent config.<\/p>\n
          {\n\t\"agent\": {\n\t  \"metrics_collection_interval\": 10,\n\t  \"run_as_user\": \"root\"\n\t},\n\t\"logs\": {\n\t  \"logs_collected\": {\n\t\t\"files\": {\n\t\t  \"collect_list\": [\n\t\t\t{\n\t\t\t  \"file_path\": \"\/opt\/aws\/amazon-cloudwatch-agent\/logs\/amazon-cloudwatch-agent.log\",\n\t\t\t  \"log_group_name\": \"\/apps\/CloudWatchAgentLog\/\",\n\t\t\t  \"log_stream_name\": \"{ip_address}_{instance_id}\",\n\t\t\t  \"timezone\": \"Local\"\n\t\t\t},\n\t\t\t{\n\t\t\t  \"file_path\": \"\/var\/log\/messages\",\n\t\t\t  \"log_group_name\": \"\/apps\/system\/messages\",\n\t\t\t  \"log_stream_name\": \"{ip_address}_{instance_id}\",\n\t\t\t  \"timestamp_format\": \"%b %d %H:%M:%S\",\n\t\t\t  \"timezone\": \"Local\"\n\t\t\t},\n\t\t\t{\n\t\t\t  \"file_path\": \"\/var\/log\/nginx\/access.log\",\n\t\t\t  \"log_group_name\": \"\/apps\/webservers\/nginx\/access\",\n\t\t\t  \"log_stream_name\": \"{ip_address}_{instance_id}\",\n\t\t\t  \"timestamp_format\": \"%d\/%b\/%Y:%H:%M:%S %z\",\n\t\t\t  \"timezone\": \"Local\"\n\t\t\t}\n\t\t  ]\n\t\t}\n\t  }\n\t},\n\t\"metrics\": {\n\t  \"aggregation_dimensions\": [\n\t\t[\n\t\t  \"InstanceId\"\n\t\t]\n\t  ],\n\t  \"append_dimensions\": {\n\t\t\"AutoScalingGroupName\": \"${aws:AutoScalingGroupName}\",\n\t\t\"ImageId\": \"${aws:ImageId}\",\n\t\t\"InstanceId\": \"${aws:InstanceId}\",\n\t\t\"InstanceType\": \"${aws:InstanceType}\"\n\t  },\n\t  \"metrics_collected\": {\n\t\t\"collectd\": {\n\t\t  \"metrics_aggregation_interval\": 60\n\t\t},\n\t\t\"disk\": {\n\t\t  \"measurement\": [\n\t\t\t\"used_percent\"\n\t\t  ],\n\t\t  \"metrics_collection_interval\": 10,\n\t\t  \"resources\": [\n\t\t\t\"*\"\n\t\t  ]\n\t\t},\n\t\t\"mem\": {\n\t\t  \"measurement\": [\n\t\t\t\"mem_used_percent\"\n\t\t  ],\n\t\t  \"metrics_collection_interval\": 10\n\t\t},\n\t\t\"statsd\": {\n\t\t  \"metrics_aggregation_interval\": 60,\n\t\t  \"metrics_collection_interval\": 10,\n\t\t  \"service_address\": \":8125\"\n\t\t}\n\t  }\n\t}\n  }<\/code><\/pre>\n
          Now, let’s start the Cloudwatch agent using the following.<\/p>\n
          sudo \/opt\/aws\/amazon-cloudwatch-agent\/bin\/amazon-cloudwatch-agent-ctl -a fetch-config -m ec2 -c file:\/opt\/aws\/amazon-cloudwatch-agent\/bin\/config.json -s<\/code><\/pre>\n
          You can check the agent status using the following command.<\/p>\n
          sudo \/opt\/aws\/amazon-cloudwatch-agent\/bin\/amazon-cloudwatch-agent-ctl -a status<\/code><\/pre>\n
          \"\"<\/figure>\n
          Validating Custom Logs in Cloudwatch Dashboard<\/h3>\n
          Once the setup is done, you can view all the configured logs under the cloudwatch dashboard (under the logs option)<\/p>\n
            \n
          1. Go to Logs –> Log Groups and you will see the log group you mentioned in the agent configuration.<\/li>\n
          2. Select the log group and you should see the instance identified you mentioned in the config.<\/li>\n
          3. If you click the instance identifier,  it shows all the logs. You can use the cloud watch filter option to filter and query required logs.<\/li>\n<\/ol>\n
            \"cloudwatch<\/figure>\n
            Conclusion<\/h2>\n
            I have explained the Cloudwatch logs agent setup to push application logs to the Cloudwatch logging service. It is a manual setup.<\/p>\n
            If you want this to be automated<\/strong>, all the agent configuration has to be baked in the ec2 AMI. Few configurations can be added at the system startup using the user data scripts. Again, it depends on what workflow you are opting for.<\/p>\n
            Not only just logs, but you can also push custom metrics to cloudwatch for monitoring.<\/p>\n
            If you face any issues or have any different ideas, do let me know in the comment section.<\/p>\n
            \n
            Ngu\u1ed3n:<\/strong> How To Push ec2 Logs to Cloudwatch [Logs And Metrics] \u2014 DevOpsCube<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
            Source: https:\/\/devopscube.com\/how-to-setup-and-push-serverapplication-logs-to-aws-cloudwatch\/<\/p>\n","protected":false},"author":1,"featured_media":905,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-904","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops"],"_links":{"self":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/posts\/904","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=904"}],"version-history":[{"count":0,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/posts\/904\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/media\/905"}],"wp:attachment":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=904"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=904"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=904"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}