intro.adoc 1.6 KB

1234567891011121314151617181920212223242526272829303132333435363738
  1. [#logs]
  2. = Logs
  3. OliveTin records an entry every time an action runs. The **Logs** pages in the web interface let you browse that history, open individual executions, and filter or search past runs.
  4. Each log entry includes:
  5. * When the action started (and finished, if applicable)
  6. * The action title and icon
  7. * Who triggered it
  8. * Status (for example, completed, timed out, or still running)
  9. * A link to the full execution output
  10. == Logs in the web interface
  11. Use the **Logs** link in the navigation to open the list view. From there you can:
  12. * Search and filter executions
  13. * Open the xref:logs/calendar.adoc[calendar view] to browse by date
  14. * Open the xref:logs/queue.adoc[queue view] when executions are waiting for a concurrency slot
  15. * Click an action title to see full output, timing, and exit status
  16. image::logs/views/logsList.png[]
  17. == Application logs vs action logs
  18. OliveTin has two different kinds of logging:
  19. * **Action logs** — history of commands you run through OliveTin (this section)
  20. * **Application logs** — diagnostic output from the OliveTin service itself (see xref:advanced_configuration/logs.adoc[Logging - Application])
  21. == What's next?
  22. * xref:logs/actions.adoc[Action logs] — permissions and visibility for the log viewer
  23. * xref:logs/calendar.adoc[Calendar view] — browse executions on a calendar
  24. * xref:logs/queue.adoc[Queue view] — see executions waiting for a concurrency slot
  25. * xref:logs/saving.adoc[Saving logs] — persist logs to disk across restarts
  26. * xref:action_customization/timeouts.adoc[Timeouts] — timed-out actions appear in the logs with a **Timed out** status