logchart nuxeo tool
This tool generates a monitor report with charts from miscellaneous log files:
JVM Garbage collector logging (gc.log)
Java Virtual Machine logging (jvm.log)
JBoss threads logging (webthreads.log)
NuxeoDS Data source usage (nuxeo-ds.log)
jmxstat output (jmxstat.log)
Sysstat sar logging, cpu and disk activity (sysstat-sar.log)
PostgreSQL logs (pgsql.log)
PostgreSQL vacuum output (vacuum.log)
View a report example.
Requirements
python
python-docutils
gnuplot >= 4.2 (with png support)
sysstat sar, same version used during the monitor.
pgFouine for PostgreSQL log and vacuum analysis
On Debian:
sudo aptitude install gnuplot sysstat python-docutils pgfouine
Usage
The logchart.py tool expects that all the logs are in the same directory and produce a detail report:
logchart.py [options] LOG_PATH REPORT_PATH
The hudson.sh scripts can be used from an hudson job to scan other jobs and produces logchart monitor reports.
How to setup monitoring on jboss/tomcat
The Nuxeo monitorctl.sh script generates all the logs.
Here are some details on how to do it by hand.
Garbage collector monitoriing
Using the jvm verbose:gc option:
JAVA_OPTS="$JAVA_OPTS -Xloggc:$JBOSS_HOME/server/default/log/gc.log -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps"
Disk and systeme monitoring
Using sysstat sar utility, just run something like:
sar -d -o $JBOSS_HOME/server/default/log/sysstat-sar.log 5 720 >/dev/null 2>&1 &
This will monitor the activity every 5s during 1h.
JBoss logging monitor
Check documentation http://doc.nuxeo.com/display/KB/Monitoring+Nuxeo+DM
JMX logging
Using jmxstat:
jmxstat localhost:1089 --contention "Catalina:type=Manager,path=/nuxeo,host=localhost[activeSessions]" > jmxstat.log 2>&1 &
PostgreSQL monitoring
Visit the pgFouine tutorial to setup properly your PostgreSQL instance
http://pgfouine.projects.postgresql.org/tutorial.html
For instance log only request slower than 100ms:
log_min_duration_statement = 100
PostgreSQL vacuum analysis
Just catch the vacuum output:
vacuumdb -fzv database-name &> vacuum.log
1 maintainer
Metadata
1 maintainer
Release files for logchart 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| logchart-1.0.1.tar.gz | 11.5 kB | Without provenance | Details for logchart-1.0.1.tar.gz |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| logchart-1.0.1-py2.7.egg | Legacy Egg format | - | - | Details for logchart-1.0.1-py2.7.egg |
| logchart-1.0.1-py2.6.egg | Legacy Egg format | - | - | Details for logchart-1.0.1-py2.6.egg |
Total release size: 50.7 kB
Release files / logchart-1.0.1.tar.gz
| Download URL | logchart-1.0.1.tar.gz |
|---|---|
| Size | 11.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7ded2e6b6d6c471682e624282ca41e8dbfe224353f1c27549b22db4df7b9c045
|
|
BLAKE2b-256 checksum How to use checksums |
2075786bd536bdf861d3e772bf4875a41f3b4b2ce761cb3ee500b062f6e85a9c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / logchart-1.0.1-py2.7.egg
| Download URL | logchart-1.0.1-py2.7.egg |
|---|---|
| Size | 19.6 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
c5326dbc325fa762e68a014891c21444789797585264034b69edfbf8731307f6
|
|
BLAKE2b-256 checksum How to use checksums |
4c37281dbe961016c26786ff0a656a516eb67b24d72fb9f2b1be1d04f28accff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / logchart-1.0.1-py2.6.egg
| Download URL | logchart-1.0.1-py2.6.egg |
|---|---|
| Size | 19.6 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
707f5d1d4c67839cdb415675681ea32e8c2ce518f7f4ebfba4d02320619e5586
|
|
BLAKE2b-256 checksum How to use checksums |
85104d777eafc11fce8026c94430b246d4aa0ed220518d2f71cce42c5200dc46
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for logchart 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
