troubleshooting.asciidoc 1.4 KB

123456789101112131415161718192021222324252627282930313233
  1. [role="xpack"]
  2. [[transform-troubleshooting]]
  3. = Troubleshooting {transforms}
  4. [subs="attributes"]
  5. ++++
  6. <titleabbrev>Troubleshooting</titleabbrev>
  7. ++++
  8. Use the information in this section to troubleshoot common problems.
  9. For issues that you cannot fix yourself … we’re here to help.
  10. If you are an existing Elastic customer with a support contract, please create
  11. a ticket in the
  12. https://support.elastic.co/customers/s/login/[Elastic Support portal].
  13. Or post in the https://discuss.elastic.co/[Elastic forum].
  14. If you encounter problems with your {transforms}, you can gather more
  15. information from the following files and APIs:
  16. * Lightweight audit messages are stored in `.transform-notifications-read`. Search
  17. by your `transform_id`.
  18. * The <<get-transform-stats,get {transform} statistics API>> provides
  19. information about the {transform} status and failures.
  20. * If the {transform} exists as a task, you can use the
  21. <<tasks,task management API>> to gather task information. For example:
  22. `GET _tasks?actions=data_frame/transforms*&detailed`. Typically, the task exists
  23. when the {transform} is in a started or failed state.
  24. * The {es} logs from the node that was running the {transform} might
  25. also contain useful information. You can identify the node from the notification
  26. messages. Alternatively, if the task still exists, you can get that information
  27. from the get {transform} statistics API. For more information, see
  28. <<logging>>.