Get social


Search Exchange


Recently updated


Most downloaded


Frequently asked questions

Icinga Exchange

Accounts

What do i need to upload a plugin or addon?

If you don't have an Icinga or Monitoring Exchange account yet, just signup here. You'll then need

How can i restore my password?

Can't remember your account's password? Restore your account here.

Can i use my old Monitoring Exchange account?

You can simply use your existing Monitoring Exchange accounts. Just login and your account will be migrated to Icinga Exchange.


Projects

GitHub Sync - what's that?

If you have an existing project on GitHub (or another git repository), you can easily add it here using our project-sync feature. You'll need the following files in your repository tree:

Navigate to Create project and choose to synchronize a project. Note: GitHub https clone url requires "GIT" as method.
  • Fill in your project details (name, git repo url, category)
  • Hit "Create Project".
Create sync Create sync success

How to create a project?

Navigate to Create project and choose to manually create a project.

  • Fill in your project details (name, url, license, category)
  • Select tags for your project: your custom ones, vendor, type and target
  • Insert files for the release (version, description) and upload it
  • Hit "Create Project".
Congratulations and thanks for your contribution! Please make sure to upload new releases of your plugin and spread the word :-)
Create manually Project tags Upload files

Manually created or synchronized project?

If you already manage your plugin on GitHub, use the synchronized project. Icinga Exchange will then sync the changes once a day and you don't need to manually update it every time. Note: The icingaexchange.yml file is required as meta information.

If you just want to share your plugin with the community in its final and stable release, you can manually create your project on Icinga Exchange. Choose the tags wisely and receive feedback on your project.

Missing tag or vendor, what now?

You want to add a vendor or category but you cannot find it? Please let us know and we'll come back to you.

icingaexchange.yml Details

  • name identifies the project. Must match the name in your synced project
  • description should reference the README.md file in markdown format by using file:///README.md
  • url sets your project url
  • tags sets your custom tags (if not matched using vendor,target,type). Use ~ as default.
  • vendor sets the vendor tag as comma separated list. Check the main page for a list of available vendor tags.
  • target sets the target tag as comma separated list. Check the main page for a list of available target tags.
  • type sets the type tag as comma separated list. Check the main page for a list of available type tags.
  • license sets your project's license
  • releases defines a list of releases identified by name
    • name sets the release name
    • description sets the release description
    • files defines a list of files included in this release
      • name sets the filename
      • url defines the file location (use the special file:/// prefix)
      • description sets additional information on this file
      • checksum defines the md5 checksum (tip: run 'md5sum pluginfile' to generated the checksum once)
Below is an example how it could look like:
name: check_sar_perf
description: "file:///README.md"
url: "https://github.com/dnsmichi/check-sar-perf"
tags: Statistic
vendor: Linux
target: Operating System
type: Plugin
license: gplv3
releases: 
  - 
    name: 1.0
    description: "1.0 Release"
    files: 
      - 
        name: check_sar_perf.py
        url: "file:///check_sar_perf.py"
        description: "First release"
        checksum: ba6aba3f7116d132c508dec8d39fa4e0

Markdown Quick Reference

Tip: Use the dillinger.io Online Markdown Editor to get a live preview of changes.
Markdown editor

Emphasis

*italic*   **bold**

_italic_   __bold__

Headers

Header 1
=========================

Header 2
-------------------------

### Header 3

#### Header 4

Lists

Unordered List
* Item 1
* Item 2
  * Item 2a
  * Item 2b
Ordered List
1. Item 1
2. Item 2
3. Item 3
   * Item 3a
   * Item 3b

Manual Line Breaks

End a line with two or more spaces:

Roses are red,   
Violets are blue.

Links

Use a plain http address or add a link to a phrase:

http://example.com

[linked phrase](http://example.com)

Images

Images on the web or local files in the same directory:

![alt text](http://example.com/logo.png)

![alt text](figures/img.png)

Blockquotes

A friend once said:

> It's always better to give 
> than to receive.

R Code Blocks

R code will be evaluated and printed

```{r}
summary(cars$dist)
summary(cars$speed)
```

Inline R Code

There were `r nrow(cars)` cars studied

Plain Code Blocks

Plain code blocks are displayed in a fixed-width font but not evaulated

```
This text is displayed verbatim / preformatted
```

Inline Code

We defined the `add` function to 
compute the sum of two numbers.

LaTeX Equations

See also: Using Equations with Markdown

Inline Equation
$equation$

$latex equation$

\( equation \)
Display Equation
$$ equation $$

$$latex equation $$

\[ equation \]

Horizontal Rule / Page Break

Three or more asterisks or dashes:

******

------

Tables

First Header  | Second Header
------------- | -------------
Content Cell  | Content Cell
Content Cell  | Content Cell

Reference Style Links and Images

Links
A [linked phrase][id]. 

At the bottom of the document:

[id]: http://example.com/ "Title"
Images
![alt text][id]

At the bottom of the document:

[id]: figures/img.png "Title"

Miscellaneous

superscript^2

~~strikethrough~~

Typographic Entities

ASCII characters are transformed into typographic HTML entities:

  • Straight quotes ( " and ' ) into “curly” quotes
  • Backtick quotes (``like this'') into “curly” quotes
  • Dashes (“--” and “---”) into en- and em-dash entities
  • Three consecutive dots (“...”) into an ellipsis entity
  • Fractions 1/4, 1/2, and 3/4 into ¼, ½, and ¾.
  • Symbols (c), (tm), and (r) into ©, ™, and ®