troubleshooting.asciidoc 1.4 KB

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