Skip to content
Elasticsearch Metricbeat for Peoplesoft
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
_meta Fix beat yaml file and kibana dashboards Jun 10, 2019
include
logs Release build tweaks Jun 7, 2019
module/psoft
modules.d Fix beat yaml file and kibana dashboards Jun 10, 2019
vendor/github.com/elastic/beats Fix beat yaml file and kibana dashboards Jun 10, 2019
.gitignore Added the custom package config. May 31, 2019
AppDetails.JPG Add doc images Jun 11, 2019
CONTRIBUTING.md Initial commit for new psoftbeat project May 6, 2019
EnvironmentList.JPG
EnvironmentSummary.JPG Add doc images Jun 11, 2019
JMXQuery-1.0-SNAPSHOT.jar
LICENSE.txt
Makefile
NOTICE.txt
README.md
TargetIssues.JPG
app_metric.yaml
blackoutList.csv_sample
domainList.csv_sample Redesign with single metricset. May 30, 2019
exclusionList.csv_sample Initial commit for new psoftbeat project May 6, 2019
fields.yml
magefile.go Redesign with single metricset. May 30, 2019
main.go Redesign with single metricset. May 30, 2019
make.bat
nailgun-server-1.0.0-SNAPSHOT-uber.jar Initial commit for new psoftbeat project May 6, 2019
prc_metric.yaml
psoftbeat.reference.yml
psoftbeat.yml
web_details.JPG
web_metric.yaml

README.md

psoftbeat

Summary

Psoftbeat is a beat based on metricbeat which was generated with metricbeat/metricset generator. Psoftbeat captures metrics for PeopleSoft targets like Weblogic, App Server (Tuxedo) and Scheduler(Tuxedo).

The psoftbeat monitor uses the psoftjmx library that provides a fast concurrent loader of JMX metrics from all PeopleSoft target types.

See releases for current packaged deployment ready to be used.

Steps for running the beat are on the wiki page https://github.com/UMN-PeopleSoft/psoftbeat/wiki/Implementing-the-psoftbeat-on-the-ElasticSearch-and-Kibana

Development

Getting started

To get started run the following command. This command should only be run once.

make setup

It will ask you for the module and metricset name. Insert the name accordingly.

To compile your beat run make. Then you can run the following command to see the first output:

psoftbeat -e -d "*"

In case further modules are metricsets should be added, run:

make create-metricset

After updates to the fields or config files, always run

make collect

This updates all fields and docs with the most recent changes.

Use vendoring

We recommend to use vendoring for your beat. This means the dependencies are put into your beat folder. The beats team currently uses govendor for vendoring.

govendor init
govendor update +e

This will create a directory vendor inside your repository. To make sure all dependencies for the Makefile commands are loaded from the vendor directory, find the following line in your Makefile:

ES_BEATS=${GOPATH}/src/github.com/elastic/beats

Replace it with:

ES_BEATS=./vendor/github.com/elastic/beats

Versioning

We recommend to version your repository with git and make it available on Github so others can also use your project. The initialise the git repository and add the first commits, you can use the following commands:

git init
git add README.md CONTRIBUTING.md
git commit -m "Initial commit"
git add LICENSE
git commit -m "Add the LICENSE"
git add .gitignore
git commit -m "Add git settings"
git add .
git reset -- .travis.yml
git commit -m "Add psoftbeat"

Packaging

The beat frameworks provides tools to crosscompile and package your beat for different platforms. This requires docker and vendoring as described above. To build packages of your beat, run the following command:

make release

This will fetch and create all images required for the build process. The hole process to finish can take several minutes.

You can’t perform that action at this time.