Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
I
icinga-checks
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
IML Open Source
icinga-checks
Commits
a0a17b34
Commit
a0a17b34
authored
1 year ago
by
Hahn Axel (hahn)
Browse files
Options
Downloads
Patches
Plain Diff
add doc page for haproxy_status
parent
10d5d875
No related branches found
No related tags found
1 merge request
!129
6468-docs-and-harmonize
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
docs/20_Checks/_index.md
+1
-1
1 addition, 1 deletion
docs/20_Checks/_index.md
docs/20_Checks/check_haproxy_health.md
+1
-1
1 addition, 1 deletion
docs/20_Checks/check_haproxy_health.md
docs/20_Checks/check_haproxy_status.md
+62
-0
62 additions, 0 deletions
docs/20_Checks/check_haproxy_status.md
with
64 additions
and
2 deletions
docs/20_Checks/_index.md
+
1
−
1
View file @
a0a17b34
...
@@ -23,7 +23,7 @@ There is one include script used by all checks:
...
@@ -23,7 +23,7 @@ There is one include script used by all checks:
*
[
check_fs_errors
](
check_fs_errors.md
)
*
[
check_fs_errors
](
check_fs_errors.md
)
*
[
check_fs_writable
](
check_fs_writable.md
)
*
[
check_fs_writable
](
check_fs_writable.md
)
*
[
check_haproxy_health
](
check_haproxy_health.md
)
*
[
check_haproxy_health
](
check_haproxy_health.md
)
*
check_haproxy_status
*
[
check_haproxy_status
](
check_haproxy_status.md
)
*
check_memory
*
check_memory
*
check_mysqlserver
*
check_mysqlserver
*
check_netio
*
check_netio
...
...
This diff is collapsed.
Click to expand it.
docs/20_Checks/check_haproxy_health.md
+
1
−
1
View file @
a0a17b34
# Check
filesystem errors
# Check
HA-Proxy health
## Introduction
## Introduction
...
...
This diff is collapsed.
Click to expand it.
docs/20_Checks/check_haproxy_status.md
0 → 100644
+
62
−
0
View file @
a0a17b34
# Check HA-Proxy Status
## Introduction
**check_haproxy_health**
show status and connections count on frontend and backend.
## Syntax
```
txt
______________________________________________________________________
CHECK_HAPROXY_STATUS
v1.8
(c) Institute for Medical Education - University of Bern
Licence: GNU GPL 3
https://os-docs.iml.unibe.ch/icinga-checks/Checks/check_haproxy_status.html
______________________________________________________________________
Check HA Proxy statistics on frontend and backend.
It shows if the status is OPEN or UP and show counts of current connectons.
The plugin reads /etc/haproxy/haproxy.cfg to detect the required statistics url and get
csv data.
It requires wget to handle the http request.
Non OK values occur:
UNKNOWN - if /etc/haproxy/haproxy.cfg cannot be read
- haproxy is not in http mode
- the url wasn't detected
- the detected status url doesn't send a response
ERROR - a frontend status is not OPEN
- a backend status is not UP
The plugin sends performance data.
SYNTAX:
check_haproxy_status [-h]
OPTIONS:
-h or --help show this help.
EXAMPLE:
check_haproxy_status
```
### Parameters
(none)
## Examples
`$ check_haproxy_status`
returns
```
txt
OK: FRONT: OPEN OPEN OPEN - 2 (max: 30010) .. BACK: UP UP UP - 0 (max: 3001)
FRONTEND - 2 BACKEND - 0 FRONTEND - 0 FRONTEND - 0 couchdb-0.example.com - 0 BACKEND - 0 couchdb-0.example.com - 0 couchdb-1.example.com - 0 couchdb-2.example.com - 0 BACKEND - 0 |frontend=2;; frontend-max=30010;; frontend-free=30008;; backend=0;; backend-max=3001;; backend-free=3001;;
```
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment