Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request to incorporate CopperEggWriter configuration files into this repo #51

Open
wants to merge 17 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
17 commits
Select commit Hold shift + click to select a range
b70cc1b
copperegg_default_config.json as a good starting configuration for me…
scottcjohnson Jul 16, 2013
c752266
Clean-up of the copperegg-specific jmxtrans.json file.
scottcjohnson Jul 16, 2013
fbe15d3
Updated to show all Cocktail demo metrics.
scottcjohnson Jul 17, 2013
01b5fae
Optimized the query & export intervals for CopperEgg 15 second updates.
scottcjohnson Jul 17, 2013
8d19f86
Tweaks of Cocktail-app specifc copperegg_config.json
scottcjohnson Jul 17, 2013
e424e9a
Tweaks of Cocktail-app specifc jmxtrans.json file.
scottcjohnson Jul 17, 2013
4a9dd76
Instructions for enabling the CopperEggWriter for the Cocktail APp Demo.
scottcjohnson Jul 17, 2013
d620dbe
Tweaks to CopperEgg specific Cocktail-app copperegg_config.json
scottcjohnson Jul 17, 2013
83196d2
Updated links
scottcjohnson Jul 17, 2013
231fb92
Corrected disconnect between metric group names and dashboards.
scottcjohnson Jul 18, 2013
0c34232
Cleaned up the config files.
scottcjohnson Jul 22, 2013
6083fae
Corrected several time units.
scottcjohnson Jul 22, 2013
48719e7
Added copperegg-jmxmon to this repo. Adjusted a number of configurati…
scottcjohnson Jul 25, 2013
9c8bfaa
Added copperegg-jmxmon to this repo. Adjusted a number of configurati…
scottcjohnson Jul 25, 2013
45ae65e
Removed README_CopperEgg.md, removed copperegg-jmxmon, removed all Co…
scottcjohnson Aug 5, 2013
fa603a2
CE-1696 Replaced terminologies and URLs related to CopperEgg
Oct 18, 2015
f33d9bf
Merge pull request #1 from CopperEgg/copperegg_rebranding
Oct 21, 2015
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
97 changes: 97 additions & 0 deletions embedded-jmxtrans-webapp-coktail/src/main/copperegg/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,97 @@
# Using the CopperEggWriter Output Writer

## Deploying with the Cocktail Demo App

### 1. Save a copy of your current resources/jmxtrans.json file

```xml
cd <path-to-embedded-jmxtrans-samples>
mv embedded-jmxtrans-webapp-coktail/src/main/resources/jmxtrans.json embedded-jmxtrans-webapp-coktail/src/main/resources/jmxtrans.json.original
```

### 2. Copy the CocktailDemo-specific copperegg_config.json and jmxtrans.json to resources/

```xml
cd <path-to-embedded-jmxtrans-samples>
cp embedded-jmxtrans-webapp-coktail/src/main/copperegg/copperegg_configCocktailApp/*.json embedded-jmxtrans-webapp-coktail/src/main/resources/
```

### 3. Edit the (newly-copied) jmxtrans.json file

```xml
cd <path-to-embedded-jmxtrans-samples>
nano embedded-jmxtrans-webapp-coktail/src/main/resources/jmxtrans.json
In the "OutputWriters" array, find the CopperEggWriter settings.
Replace <YOUR_USER_NAME> with your user name
Replace <YOUR_APIKEY> with your Uptime Cloud Monitor APIKEY
Optionally, add any other OutputWriters to the OutputWriters array.
Save and close jmxtrans.json
```

### 4. Build and Deploy the Cocktail Demo App as usual.


## Integrating with your Spring-enabled or Plain Java Servlet

### 1. Save a copy of your current resources/jmxtrans.json file, as in Step 1 above

### 2. Copy the copperegg_config.json and jmxtrans.json to resources/

```xml
cp src/main/copperegg/*.json <path-to-your-resources-directory>
```
### 3. Edit the (newly-copied) jmxtrans.json file, as descibed in Step 3 above


### 4. Follow the embedded-jmxtrans instructions for building and deploying

For Spring integration:

[embedded-jmxtrans wiki](https://github.com/jmxtrans/embedded-jmxtrans/wiki/Spring-Integration)

For Plain-Java-Servlet integration:

[embedded-jmxtrans wiki](https://github.com/jmxtrans/embedded-jmxtrans/wiki/Plain-Java-Servlet-Integration)


For the documentation about the embedded-jmxtrans module, refer to:
* [Documentation](https://github.com/jmxtrans/embedded-jmxtrans/wiki)
* [Latest javadocs](http://jmxtrans.github.com/embedded-jmxtrans/apidocs/)

To learn more about Uptime Cloud Monitor, and to sign up for a free trial:
* [Uptime Cloud Monitor Homepage] (https://www.idera.com/infrastructure-monitoring-as-a-service/)
* [Uptime Cloud Monitor Signup] (https://www.idera.com/infrastructure-monitoring-as-a-service/freetrialsubscriptionform)
* [Uptime Cloud Monitor Login] (https://app.copperegg.com/login)


License
==================

Please refer to the LICENSE and NOTIFICATION files included by the authors of embedded-jmxtrans and embedded-jmxtrans-samples.

Uptime Cloud Monitor has provided three JSON files in this repository, which can be used to configure the CopperEggWriter.
These files are made available under the terms of the MIT License:

Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the "Software"),
to deal in the Software without restriction, including without
limitation the rights to use, copy, modify, merge, publish, distribute,
sublicense, and/or sell copies of the Software, and to permit persons
to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL
THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR
OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.






Loading