02-17-2020
Quote:
I'm not inclined to install an application which relies on HTTP at the data transport layer to monitor a LAMP application where HTTP and apache2 are at the core of the problem. However, for a different scenario, an HTTP-transport based monitoring system might be "just the ticket".
I'm not sure if you understood it right. Prometheus is getting the Performance data via http, that's correct, but it does not use the installed http-server which is serving normal http requests. That obviously would be senseless for the reason you mentioned.
That data provisioning is done by
exporters which are tiny lightweight webservers running standalone on the target systems. Like the apache exporter(see
here). And well - "lightweight" might be a bit irritating label for a binary with 12 MB size, but as it is
go it is statically compiled that's a bit different from a normal dynamically linked executable.
The apache exporter fetches data from apache status module and listens on port 9117 by default.
Last edited by stomp; 02-17-2020 at 12:56 PM..
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
we have an unix system which has
load average normally about 20.
but while i am running a particular unix batch which performs heavy
operations on filesystem and database average load
reduces to 15.
how can we explain this situation?
while running that batch idle cpu time is about %60-65... (0 Replies)
Discussion started by: gfhgfnhhn
0 Replies
2. UNIX for Dummies Questions & Answers
Hello all, I have a question about load averages.
I've read the man pages for the uptime and w command for two or three different flavors of Unix (Red Hat, Tru64, Solaris). All of them agree that in the output of the 2 aforementioned commands, you are given the load average for the box, but... (3 Replies)
Discussion started by: Heathe_Kyle
3 Replies
3. UNIX for Dummies Questions & Answers
Hello, Here is the output of top command. My understanding here is,
the load average 0.03 in last 1 min, 0.02 is in last 5 min, 0.00 is in last 15 min.
By seeing this load average, When can we say that, the system load averge is too high?
When can we say that, load average is medium/low??... (8 Replies)
Discussion started by: govindts
8 Replies
4. Solaris
Hi,
i have installed solaris 10 on t-5120 sparc enterprise.
I am little surprised to see load average of 2 or around on this OS.
when checked with ps command following process is using highest CPU. looks like it is running for long time and does not want to stop, but I do not know... (5 Replies)
Discussion started by: upengan78
5 Replies
5. UNIX for Dummies Questions & Answers
Hello AlL,..
I want from experts to help me as my load average is increased and i dont know where is the problem !!
this is my top result :
root@a4s # top
top - 11:30:38 up 40 min, 1 user, load average: 3.06, 2.49, 4.66
Mem: 8168788k total, 2889596k used, 5279192k free, 47792k... (3 Replies)
Discussion started by: black-code
3 Replies
6. UNIX for Advanced & Expert Users
Hi ,
I am using 48 CPU sunOS server at my work.
The application has facility to check the current load average before starting a new process to control the load.
Right now it is configured as 48. So it does mean that each CPU can take maximum one proces and no processe is waiting.
... (2 Replies)
Discussion started by: kumaran_5555
2 Replies
7. Solaris
NPROC USERNAME SWAP RSS MEMORY TIME CPU
320 oracle 23G 22G 69% 582:55:11 85%
47 root 148M 101M 0.3% 99:29:40 0.3%
53 rafmsdb 38M 60M 0.2% 0:46:17 0.1%
1 smmsp 1296K 5440K 0.0% 0:00:08 0.0%
7 daemon ... (2 Replies)
Discussion started by: snjksh
2 Replies
8. UNIX for Dummies Questions & Answers
Hi,
I am getting a high load average, around 7, once an hour. It last for about 4 minutes and makes things fairly unusable for this time.
How do I find out what is using this. Looking at top the only thing running at the time is md5sum.
I have looked at the crontab and there is nothing... (10 Replies)
Discussion started by: sm9ai
10 Replies
9. UNIX for Dummies Questions & Answers
how load average is calculated and what exactly is it
difference between cpu% and load average (9 Replies)
Discussion started by: robo
9 Replies
10. Programming
Here we go....
Preface:
..... so in a galaxy far, far, far away from commercial, data sharing corporations.....
For this project, I used the ESP-WROOM-32 as an MQTT (publish / subscribe) client which receives Linux server "load averages" as messages published as MQTT pub/sub messages.... (6 Replies)
Discussion started by: Neo
6 Replies
LEARN ABOUT CENTOS
ocf_heartbeat_apache
OCF_HEARTBEAT_APACHE(7) OCF resource agents OCF_HEARTBEAT_APACHE(7)
NAME
ocf_heartbeat_apache - Manages an Apache Web server instance
SYNOPSIS
apache [start | stop | status | monitor | meta-data | validate-all]
DESCRIPTION
This is the resource agent for the Apache Web server. This resource agent operates both version 1.x and version 2.x Apache servers.
The start operation ends with a loop in which monitor is repeatedly called to make sure that the server started and that it is operational.
Hence, if the monitor operation does not succeed within the start operation timeout, the apache resource will end with an error status.
The monitor operation by default loads the server status page which depends on the mod_status module and the corresponding configuration
file (usually /etc/apache2/mod_status.conf). Make sure that the server status page works and that the access is allowed *only* from
localhost (address 127.0.0.1). See the statusurl and testregex attributes for more details.
See also http://httpd.apache.org/
SUPPORTED PARAMETERS
configfile
The full pathname of the Apache configuration file. This file is parsed to provide defaults for various other resource agent
parameters.
(unique, optional, string, default "/etc/httpd/conf/httpd.conf")
httpd
The full pathname of the httpd binary (optional).
(optional, string, default "/usr/sbin/httpd")
port
A port number that we can probe for status information using the statusurl. This will default to the port number found in the
configuration file, or 80, if none can be found in the configuration file.
(optional, integer, no default)
statusurl
The URL to monitor (the apache server status page by default). If left unspecified, it will be inferred from the apache configuration
file.
If you set this, make sure that it succeeds *only* from the localhost (127.0.0.1). Otherwise, it may happen that the cluster complains
about the resource being active on multiple nodes.
(optional, string, no default)
testregex
Regular expression to match in the output of statusurl. Case insensitive.
(optional, string, default "exists, but impossible to show in a human readable format (try grep testregex)")
client
Client to use to query to Apache. If not specified, the RA will try to find one on the system. Currently, wget and curl are supported.
For example, you can set this parameter to "curl" if you prefer that to wget.
(optional, string, no default)
testurl
URL to test. If it does not start with "http", then it's considered to be relative to the Listen address.
(optional, string, no default)
testregex10
Regular expression to match in the output of testurl. Case insensitive.
(optional, string, no default)
testconffile
A file which contains test configuration. Could be useful if you have to check more than one web application or in case sensitive info
should be passed as arguments (passwords). Furthermore, using a config file is the only way to specify certain parameters.
Please see README.webapps for examples and file description.
(optional, string, no default)
testname
Name of the test within the test configuration file.
(optional, string, no default)
options
Extra options to apply when starting apache. See man httpd(8).
(optional, string, no default)
envfiles
Files (one or more) which contain extra environment variables. If you want to prevent script from reading the default file, set this
parameter to empty string.
(optional, string, default "/etc/apache2/envvars")
use_ipv6
We will try to detect if the URL (for monitor) is IPv6, but if that doesn't work set this to true to enforce IPv6.
(optional, boolean, default false)
SUPPORTED ACTIONS
This resource agent supports the following actions (operations):
start
Starts the resource. Suggested minimum timeout: 40s.
stop
Stops the resource. Suggested minimum timeout: 60s.
status
Performs a status check. Suggested minimum timeout: 30s.
monitor
Performs a detailed status check. Suggested minimum timeout: 20s. Suggested interval: 10.
meta-data
Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5.
validate-all
Performs a validation of the resource configuration. Suggested minimum timeout: 5.
EXAMPLE
The following is an example configuration for a apache resource using the crm(8) shell:
primitive p_apache ocf:heartbeat:apache
op monitor depth="0" timeout="20s" interval="10"
SEE ALSO
http://www.linux-ha.org/wiki/apache_(resource_agent)
AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors)
resource-agents UNKNOWN 06/09/2014 OCF_HEARTBEAT_APACHE(7)