1
0

get-calendar.asciidoc 2.0 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889
  1. [role="xpack"]
  2. [testenv="platinum"]
  3. [[ml-get-calendar]]
  4. === Get calendars API
  5. ++++
  6. <titleabbrev>Get calendars</titleabbrev>
  7. ++++
  8. Retrieves configuration information for calendars.
  9. [[ml-get-calendar-request]]
  10. ==== {api-request-title}
  11. `GET _ml/calendars/<calendar_id>` +
  12. `GET _ml/calendars/_all`
  13. [[ml-get-calendar-prereqs]]
  14. ==== {api-prereq-title}
  15. * If the {es} {security-features} are enabled, you must have `monitor_ml`,
  16. `monitor`, `manage_ml`, or `manage` cluster privileges to use this API. See
  17. <<security-privileges>>.
  18. [[ml-get-calendar-desc]]
  19. ==== {api-description-title}
  20. You can get information for a single calendar or for all calendars by using
  21. `_all`.
  22. For more information, see
  23. {ml-docs}/ml-calendars.html[Calendars and scheduled events].
  24. [[ml-get-calendar-path-parms]]
  25. ==== {api-path-parms-title}
  26. `<calendar_id>`::
  27. (Required, string) Identifier for the calendar.
  28. [[ml-get-calendar-request-body]]
  29. ==== {api-request-body-title}
  30. `page`.`from`::
  31. (Optional, integer) Skips the specified number of calendars.
  32. `page`.`size`::
  33. (Optional, integer) Specifies the maximum number of calendars to obtain.
  34. [[ml-get-calendar-results]]
  35. ==== {api-response-body-title}
  36. The API returns an array of calendar resources, which have the following
  37. properties:
  38. `calendar_id`::
  39. (string) A numerical character string that uniquely identifies the calendar.
  40. `job_ids`::
  41. (array) An array of {anomaly-job} identifiers. For example:
  42. `["total-requests"]`.
  43. [[ml-get-calendar-example]]
  44. ==== {api-examples-title}
  45. The following example gets configuration information for the `planned-outages`
  46. calendar:
  47. [source,console]
  48. --------------------------------------------------
  49. GET _ml/calendars/planned-outages
  50. --------------------------------------------------
  51. // TEST[skip:setup:calendar_outages_addjob]
  52. The API returns the following results:
  53. [source,console-result]
  54. ----
  55. {
  56. "count": 1,
  57. "calendars": [
  58. {
  59. "calendar_id": "planned-outages",
  60. "job_ids": [
  61. "total-requests"
  62. ]
  63. }
  64. ]
  65. }
  66. ----