2019-09-18 16:30:16 -04:00
|
|
|
[role="xpack"]
|
|
|
|
[testenv="basic"]
|
2019-09-11 11:44:03 -04:00
|
|
|
[[dataframe-troubleshooting]]
|
2019-09-16 11:28:19 -04:00
|
|
|
== Troubleshooting {transforms}
|
2019-09-11 11:44:03 -04:00
|
|
|
[subs="attributes"]
|
|
|
|
++++
|
|
|
|
<titleabbrev>Troubleshooting</titleabbrev>
|
|
|
|
++++
|
|
|
|
|
|
|
|
Use the information in this section to troubleshoot common problems.
|
|
|
|
|
|
|
|
include::{stack-repo-dir}/help.asciidoc[tag=get-help]
|
|
|
|
|
2019-09-16 11:28:19 -04:00
|
|
|
If you encounter problems with your {transforms}, you can gather more
|
2019-09-11 11:44:03 -04:00
|
|
|
information from the following files and APIs:
|
|
|
|
|
|
|
|
* Lightweight audit messages are stored in `.data-frame-notifications-*`. Search
|
|
|
|
by your `transform_id`.
|
|
|
|
* The
|
2019-09-16 11:28:19 -04:00
|
|
|
{ref}/get-data-frame-transform-stats.html[get {transform} statistics API]
|
|
|
|
provides information about the {transform} status and failures.
|
|
|
|
* If the {transform} exists as a task, you can use the
|
2019-09-11 11:44:03 -04:00
|
|
|
{ref}/tasks.html[task management API] to gather task information. For example:
|
|
|
|
`GET _tasks?actions=data_frame/transforms*&detailed`. Typically, the task exists
|
2019-09-16 11:28:19 -04:00
|
|
|
when the {transform} is in a started or failed state.
|
|
|
|
* The {es} logs from the node that was running the {transform} might
|
2019-09-11 11:44:03 -04:00
|
|
|
also contain useful information. You can identify the node from the notification
|
|
|
|
messages. Alternatively, if the task still exists, you can get that information
|
2019-09-16 11:28:19 -04:00
|
|
|
from the get {transform} statistics API. For more information, see
|
2019-09-11 11:44:03 -04:00
|
|
|
{ref}/logging.html[Logging configuration].
|
|
|
|
|