metadata.yaml 6.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168
  1. plugin_name: python.d.plugin
  2. modules:
  3. - meta:
  4. plugin_name: python.d.plugin
  5. module_name: litespeed
  6. monitored_instance:
  7. name: Litespeed
  8. link: "https://www.litespeedtech.com/products/litespeed-web-server"
  9. categories:
  10. - data-collection.web-servers-and-web-proxies
  11. icon_filename: "litespeed.svg"
  12. related_resources:
  13. integrations:
  14. list: []
  15. info_provided_to_referring_integrations:
  16. description: ""
  17. keywords:
  18. - litespeed
  19. - web
  20. - server
  21. most_popular: false
  22. overview:
  23. data_collection:
  24. metrics_description: "Examine Litespeed metrics for insights into web server operations. Analyze request rates, response times, and error rates for efficient web service delivery."
  25. method_description: "The collector uses the statistics under /tmp/lshttpd to gather the metrics."
  26. supported_platforms:
  27. include: []
  28. exclude: []
  29. multi_instance: false
  30. additional_permissions:
  31. description: ""
  32. default_behavior:
  33. auto_detection:
  34. description: "If no configuration is present, the collector will attempt to read files under /tmp/lshttpd/."
  35. limits:
  36. description: ""
  37. performance_impact:
  38. description: ""
  39. setup:
  40. prerequisites:
  41. list: []
  42. configuration:
  43. file:
  44. name: python.d/litespeed.conf
  45. options:
  46. description: |
  47. There are 2 sections:
  48. * Global variables
  49. * One or more JOBS that can define multiple different instances to monitor.
  50. The following options can be defined globally: priority, penalty, autodetection_retry, update_every, but can also be defined per JOB to override the global values.
  51. Additionally, the following collapsed table contains all the options that can be configured inside a JOB definition.
  52. Every configuration JOB starts with a `job_name` value which will appear in the dashboard, unless a `name` parameter is specified.
  53. folding:
  54. title: "Config options"
  55. enabled: true
  56. list:
  57. - name: update_every
  58. description: Sets the default data collection frequency.
  59. default_value: 5
  60. required: false
  61. - name: priority
  62. description: Controls the order of charts at the netdata dashboard.
  63. default_value: 60000
  64. required: false
  65. - name: autodetection_retry
  66. description: Sets the job re-check interval in seconds.
  67. default_value: 0
  68. required: false
  69. - name: penalty
  70. description: Indicates whether to apply penalty to update_every in case of failures.
  71. default_value: yes
  72. required: false
  73. - name: name
  74. description: Job name. This value will overwrite the `job_name` value. JOBS with the same name are mutually exclusive. Only one of them will be allowed running at any time. This allows autodetection to try several alternatives and pick the one that works.
  75. default_value: ""
  76. required: false
  77. - name: path
  78. description: Use a different path than the default, where the lightspeed stats files reside.
  79. default_value: "/tmp/lshttpd/"
  80. required: false
  81. examples:
  82. folding:
  83. enabled: false
  84. title: "Config"
  85. list:
  86. - name: Set the path to statistics
  87. description: Change the path for the litespeed stats files
  88. config: |
  89. localhost:
  90. name: 'local'
  91. path: '/tmp/lshttpd'
  92. troubleshooting:
  93. problems:
  94. list: []
  95. alerts: []
  96. metrics:
  97. folding:
  98. title: Metrics
  99. enabled: false
  100. description: ""
  101. availability: []
  102. scopes:
  103. - name: global
  104. description: "These metrics refer to the entire monitored application."
  105. labels: []
  106. metrics:
  107. - name: litespeed.net_throughput
  108. description: Network Throughput HTTP
  109. unit: "kilobits/s"
  110. chart_type: area
  111. dimensions:
  112. - name: in
  113. - name: out
  114. - name: litespeed.net_throughput
  115. description: Network Throughput HTTPS
  116. unit: "kilobits/s"
  117. chart_type: area
  118. dimensions:
  119. - name: in
  120. - name: out
  121. - name: litespeed.connections
  122. description: Connections HTTP
  123. unit: "conns"
  124. chart_type: stacked
  125. dimensions:
  126. - name: free
  127. - name: used
  128. - name: litespeed.connections
  129. description: Connections HTTPS
  130. unit: "conns"
  131. chart_type: stacked
  132. dimensions:
  133. - name: free
  134. - name: used
  135. - name: litespeed.requests
  136. description: Requests
  137. unit: "requests/s"
  138. chart_type: line
  139. dimensions:
  140. - name: requests
  141. - name: litespeed.requests_processing
  142. description: Requests In Processing
  143. unit: "requests"
  144. chart_type: line
  145. dimensions:
  146. - name: processing
  147. - name: litespeed.cache
  148. description: Public Cache Hits
  149. unit: "hits/s"
  150. chart_type: line
  151. dimensions:
  152. - name: hits
  153. - name: litespeed.cache
  154. description: Private Cache Hits
  155. unit: "hits/s"
  156. chart_type: line
  157. dimensions:
  158. - name: hits
  159. - name: litespeed.static
  160. description: Static Hits
  161. unit: "hits/s"
  162. chart_type: line
  163. dimensions:
  164. - name: hits