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