@@ -72,9 +72,109 @@ include::{docdir}/rest-api/common-parms.asciidoc[tag=size-transforms]
72
72
[[get-transform-stats-response]]
73
73
==== {api-response-body-title}
74
74
75
- `transforms`::
76
- (array) An array of statistics objects for {transforms}, which are
77
- sorted by the `id` value in ascending order.
75
+ The API returns an array of statistics objects for {transforms}, which are
76
+ sorted by the `id` value in ascending order. All of these properties are
77
+ informational; you cannot update their values.
78
+
79
+ `checkpointing`::
80
+ (object) Contains statistics about <<transform-checkpoints,checkpoints>>.
81
+ `checkpointing`.`changes_last_detected_at`:::
82
+ (date) The timestamp when changes were last detected in the source indices.
83
+ `checkpointing`.`last`:::
84
+ (object) Contains statistics about the last completed checkpoint.
85
+ `checkpointing`.`last`.`checkpoint`::::
86
+ (integer) The sequence number for the checkpoint.
87
+ `checkpointing`.`last`.`time_upper_bound_millis`::::
88
+ (date) When using time-based synchronization, this timestamp indicates the
89
+ upper bound of data that is included in the checkpoint.
90
+ `checkpointing`.`last`.`timestamp_millis`::::
91
+ (date) The timestamp of the checkpoint, which indicates when the checkpoint
92
+ was created.
93
+ `checkpointing`.`next`:::
94
+ (object) Contains statistics about the next checkpoint that is currently in
95
+ progress. This object appears only when the {transform} `state` is `indexing`.
96
+ `checkpointing`.`next`.`checkpoint`::::
97
+ (integer) The sequence number for the checkpoint.
98
+ `checkpointing`.`next`.`checkpoint_progress`::::
99
+ (object) Contains statistics about the progress of the checkpoint. For example,
100
+ it lists the `total_docs`, `docs_remaining`, `percent_complete`,
101
+ `docs_processed`, and `docs_indexed`. This information is available only for
102
+ batch {transforms} and the first checkpoint of {ctransforms}.
103
+ `checkpointing`.`next`.`time_upper_bound_millis`::::
104
+ (date) When using time-based synchronization, this timestamp indicates the
105
+ upper bound of data that is included in the checkpoint.
106
+ `checkpointing`.`next`.`timestamp_millis`::::
107
+ (date) The timestamp of the checkpoint, which indicates when the checkpoint was
108
+ created.
109
+
110
+ `id`::
111
+ (string)
112
+ include::{docdir}/rest-api/common-parms.asciidoc[tag=transform-id]
113
+
114
+ `node`::
115
+ (object) For started {transforms} only, the node upon which the {transform} is
116
+ started.
117
+ `node`.`attributes`:::
118
+ (object) A list of attributes for the node.
119
+ `node`.`ephemeral_id`:::
120
+ (string) The node ephemeral ID.
121
+ `node`.`id`:::
122
+ (string) The unique identifier of the node. For example, "0-o0tOoRTwKFZifatTWKNw".
123
+ `node`.`name`:::
124
+ (string) The node name. For example, `0-o0tOo`.
125
+ `node`.`transport_address`:::
126
+ (string) The host and port where transport HTTP connections are accepted. For
127
+ example, `127.0.0.1:9300`.
128
+ `state`::
129
+ (string) The status of the {transform}, which can be one of the following values:
130
+ +
131
+ --
132
+ * `aborting`: The {transform} is aborting.
133
+ * `failed`: The {transform} failed. For more information about the failure,
134
+ check the reason field.
135
+ * `indexing`: The {transform} is actively processing data and creating new
136
+ documents.
137
+ * `started`: The {transform} is running but not actively indexing data.
138
+ * `stopped`: The {transform} is stopped.
139
+ * `stopping`: The {transform} is stopping.
140
+ --
141
+
142
+ `stats`::
143
+ (object) An object that provides statistical information about the {transform}.
144
+ `stats`.`documents_indexed`:::
145
+ (long) The number of documents that have been indexed into the destination index
146
+ for the {transform}.
147
+ `stats`.`documents_processed`:::
148
+ (long) The number of documents that have been processed from the source index of
149
+ the {transform}.
150
+ `stats`.`exponential_avg_checkpoint_duration_ms`:::
151
+ (double) Exponential moving average of the duration of the checkpoint, in milliseconds.
152
+ `stats`.`exponential_avg_documents_indexed`:::
153
+ (double) Exponential moving average of the number of new documents that have been
154
+ indexed.
155
+ `stats`.`exponential_avg_documents_processed`:::
156
+ (double) Exponential moving average of the number of documents that have been
157
+ processed.
158
+ `stats`.`index_failures`:::
159
+ (long) The number of indexing failures.
160
+ `stats`.`index_time_in_ms`:::
161
+ (long) The amount of time spent indexing, in milliseconds.
162
+ `stats`.`index_total`:::
163
+ (long) The number of indices created.
164
+ `stats`.`pages_processed`:::
165
+ (long) The number of search or bulk index operations processed. Documents are
166
+ processed in batches instead of individually.
167
+ `stats`.`search_failures`:::
168
+ (long) The number of search failures.
169
+ `stats`.`search_time_in_ms`:::
170
+ (long) The amount of time spent searching, in milliseconds.
171
+ `stats`.`search_total`:::
172
+ (long) The number of search operations on the source index for the {transform}.
173
+ `stats`.`trigger_count`:::
174
+ (long) The number of times the {transform} has been triggered by the scheduler.
175
+ For example, the scheduler triggers the {transform} indexer to check for updates
176
+ or ingest new data at an interval specified in the
177
+ <<put-transform-request-body,`frequency` property>>.
78
178
79
179
[[get-transform-stats-response-codes]]
80
180
==== {api-response-codes-title}
0 commit comments