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: managing-cf/app-event.html.md.erb
+7-13Lines changed: 7 additions & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -10,20 +10,14 @@ This topic explains how to query the Cloud Controller API (CAPI) to retrieve cur
10
10
11
11
## <aid='target'></a> Target and Log In
12
12
13
-
To perform the procedures in this topic, you must target the endpoint of your Cloud Controller and log in. If you do not have the cf CLI installed, see the [Installing the cf CLI](../../cf-cli/install-go-cli.html) topic.
13
+
To perform the procedures in this topic, you must authenticate to your Cloud Controller. There are two ways of doing this:
14
14
15
-
There are two ways to target your Cloud Controller endpoint. You can run the following `curl` command to target the endpoint and log in:
You can also use `cf curl` to retrieve information. To use `cf curl`, do the following:
15
+
* Run `curl` commands that include the Cloud Controller endpoint and pass in your authorization token each time with the `-H` flag.
22
16
23
-
1. Target the endpoint of your Cloud Controller:
17
+
* Run `cf curl` commands without including the endpoint or token. To do this, you must first use the Cloud Controller Command-Line Interface (cf CLI) to target the endpoint of your Cloud Controller and log in, as follows:
18
+
1. Target the endpoint of your Cloud Controller:
24
19
<preclass='terminal'>$ cf api api.YOUR-SYSTEM-DOMAIN</pre>
25
-
26
-
1. Log in as admin or as an Org Manager or Org Auditor for the org you want to obtain information about.
20
+
1. Log in as admin or as an Org Manager or Org Auditor for the org you want to obtain information about.
27
21
<preclass='terminal'>
28
22
$ cf login -u admin
29
23
API endpoint: api.YOUR-SYSTEM-DOMAIN
@@ -38,8 +32,8 @@ You can also use `cf curl` to retrieve information. To use `cf curl`, do the fol
38
32
User: user<span>@</span>example.com
39
33
Org: YOUR-ORG
40
34
Space: development
41
-
</pre>
42
-
35
+
</pre>
36
+
If you do not have the cf CLI installed, see the [Installing the cf CLI](../../cf-cli/install-go-cli.html) topic
Copy file name to clipboardExpand all lines: metrics/_diego.html.md.erb
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -48,8 +48,8 @@ Default Origin Name: bbs
48
48
ConvergenceTasksPruned | Cumulative number of times the BBS has deleted a malformed Task during its Task convergence pass. Emitted every 30 seconds.
49
49
CrashedActualLRPs | Total number of LRP instances that have crashed. Emitted every 30 seconds.
50
50
CrashingDesiredLRPs | Total number of DesiredLRPs that have at least one crashed instance. Emitted every 30 seconds.
51
-
Domain.cf-apps | Whether the 'cf-apps' domain is up-to-date, so that CF apps from CC have been synchronized with DesiredLRPs for Diego to run. `1` means the domain is up-to-date, no data means it is not. Emitted every 30 seconds.
52
-
Domain.cf-tasks | Whether the 'cf-tasks' domain is up-to-date, so that CF tasks from CC have been synchronized with tasks for Diego to run. `1` means the domain is up-to-date, no data means it is not. Emitted every 30 seconds.
51
+
Domain.cf-apps | Whether the <code>cf-apps</code> domain is up-to-date. Also known as [domain freshness](https://github.com/cloudfoundry/bbs/blob/master/doc/lrps.md#domain-freshness), this key metric indicates that CF apps from Cloud Controller have been synchronized with DesiredLRPs for Diego to run. When the domain is not up-to-date, Diego does not take corrective actions to ensure eventual consistency. In particular, Diego refuses to stop extra app instances that have no corresponding desired state.<br><br> A value of <code>1</code> means the domain is up-to-date, no data means it is not. Emitted every 30 seconds.
52
+
Domain.cf-tasks | Whether the <code>cf-tasks</code> domain is up-to-date. Also known as [domain freshness](https://github.com/cloudfoundry/bbs/blob/master/doc/lrps.md#domain-freshness), this key metric indicates that CF tasks from Cloud Controller have been synchronized with tasks for Diego to run. When the domain is not up-to-date, Diego does not take corrective actions to ensure eventual consistency.<br><br> A value of <code>1</code> means the domain is up-to-date, no data means it is not. Emitted every 30 seconds.
53
53
ETCDLeader | Index of the leader node in the etcd cluster. Emitted every 30 seconds.
54
54
ETCDRaftTerm | Raft term of the etcd cluster. Emitted every 30 seconds.
55
55
ETCDReceivedBandwidthRate | Number of bytes per second received by the follower etcd node. Emitted every 30 seconds.
0 commit comments