You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+16-77Lines changed: 16 additions & 77 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,8 +37,6 @@ cf uninstall-plugin AutoScaler
37
37
|[autoscaling-policy, asp](#cf-autoscaling-policy)| Retrieve the scaling policy of an application |
38
38
|[attach-autoscaling-policy, aasp](#cf-attach-autoscaling-policy)| Attach a scaling policy to an application |
39
39
|[detach-autoscaling-policy, dasp](#cf-detach-autoscaling-policy)| Detach the scaling policy from an application |
40
-
|[create-autoscaling-credential, casc](#cf-create-autoscaling-credential)| Create custom metric credential for an application |
41
-
|[delete-autoscaling-credential, dasc](#cf-delete-autoscaling-credential)| Delete the custom metric credential of an application |
42
40
|[autoscaling-metrics, asm](#cf-autoscaling-metrics)| Retrieve the metrics of an application |
43
41
|[autoscaling-history, ash](#cf-autoscaling-history)| Retrieve the scaling history of an application|
44
42
@@ -141,13 +139,13 @@ Showing policy for app APP_NAME...
141
139
```
142
140
$ cf asp APP_NAME --output PATH_TO_FILE
143
141
144
-
Saving policy for app APP_NAME to PATH_TO_FILE...
142
+
Showing policy for app APP_NAME...
145
143
OK
146
144
```
147
145
148
146
### `cf attach-autoscaling-policy`
149
147
150
-
Attach a scaling policy to an application, the policy file must be a JSON file, refer to [policy specification](https://github.com/cloudfoundry/app-autoscaler/blob/develop/docs/policy.md) for the policy format.
148
+
Attach a scaling policy to an application, the policy file must be a JSON file, refer to [policy specification](https://github.com/cloudfoundry-incubator/blob/master/docs/policy.md) for the policy format.
Detach the scaling policy from an application, the policy will be **deleted** when detached.
170
168
171
169
```
172
-
cf detach-autoscaling-policy APP_NAME
170
+
cf detach-as-policy APP_NAME
173
171
```
174
172
#### ALIAS: dasp
175
173
@@ -182,87 +180,27 @@ OK
182
180
```
183
181
184
182
185
-
### `cf create-autoscaling-credential`
186
-
187
-
Credential is required when submitting custom metrics to app-autoscaler. If an application is connecting to autoscaler through a service binding approach, the required credential could be found in Cloud Foundry `VCAP_SERVICES` environment variables. Otherwise, you need to generate the required credential explicitly with this command.
188
-
189
-
The command will generate autoscaler credential and display it in JSON format. Then you need to set this credential to your application through environment variables or user-provided-service.
190
-
191
-
Note: Auto-scaler only grants access with the most recent credential, so the newly generated credential will overwritten the old pairs. Please make sure to update the credential setting in your application once you launch the command `create-autoscaling-credential`.
192
-
193
-
Random credential pair will be created by default when username and password are not specified by `--username` and `--password` option.
Saving new created credential for app APP_NAME to PATH_TO_FILE...
224
-
OK
225
-
```
226
-
227
-
228
-
### `cf delete-autoscaling-credential`
229
-
230
-
Delete the custom metric credential of an application.
231
-
232
-
```
233
-
cf delete-autoscaling-credential APP_NAME
234
-
```
235
-
#### ALIAS: dasc
236
-
237
-
#### EXAMPLES:
238
-
```
239
-
$ cf delete-autoscaling-credential APP_NAME
240
-
241
-
Deleting custom metric credential for app APP_NAME...
242
-
OK
243
-
```
244
-
245
-
246
183
### `cf autoscaling-metrics`
247
184
248
-
Retrieve the aggregated metrics of an application. You can specify the start/end time of the returned query result, and the display order(ascending or descending). The metrics will be shown in a table.
185
+
Retrieve the aggregated metrics of an application. You can specify the start/end time or the number of the returned query result, and the display order(ascending or descending). The metrics will be shown in a table.
-`METRIC_NAME` : default metrics "memoryused, memoryutil, responsetime, throughput, cpu" or customized name for your own metrics.
194
+
-`METRIC_NAME` : available metric supported: memoryused, memoryutil, responsetime, throughput and cpu.
258
195
-`--start` : start time of metrics collected with format `yyyy-MM-ddTHH:mm:ss+/-HH:mm` or `yyyy-MM-ddTHH:mm:ssZ`, default to very beginning if not specified.
259
196
-`--end` : end time of the metrics collected with format `yyyy-MM-ddTHH:mm:ss+/-HH:mm` or `yyyy-MM-ddTHH:mm:ssZ`, default to current time if not speficied.
260
-
-`--asc` : display in ascending order, default to descending order if not specified
197
+
-`--number|-n` : the number of the records to return, will be ignored if both start time and end time are specified.
198
+
-`--desc` : display in descending order, default to ascending order if not specified
Retrieve the scaling event history of an application. You can specify the start/end time of the returned query result, and the display order(ascending or descending). The scaling event history will be shown in a table.
219
+
Retrieve the scaling event history of an application. You can specify the start/end time or the number of the returned query result, and the display order(ascending or descending). The scaling event history will be shown in a table.
-`--start` : start time of the scaling history with format `yyyy-MM-ddTHH:mm:ss+/-HH:mm` or `yyyy-MM-ddTHH:mm:ssZ`, default to very beginning if not specified.
290
228
-`--end` : end time of the scaling history with format `yyyy-MM-ddTHH:mm:ss+/-HH:mm` or `yyyy-MM-ddTHH:mm:ssZ`, default to current time if not speficied.
291
-
-`--asc` : display in ascending order, default to descending order if not specified
229
+
-`--number|-n` : the number of the records to return, will be ignored if both start time and end time are specified.
230
+
-`--desc` : display in descending order, default to ascending order if not specified
0 commit comments