mirror of
https://github.com/Icinga/icingaweb2-module-businessprocess.git
synced 2026-02-02 16:39:25 -05:00
Layout of README file
This commit is contained in:
parent
66cd993f0a
commit
4c0c02bc28
3 changed files with 34 additions and 10 deletions
1
.gitignore
vendored
Normal file
1
.gitignore
vendored
Normal file
|
|
@ -0,0 +1 @@
|
|||
.idea/
|
||||
40
README.md
40
README.md
|
|
@ -1,31 +1,53 @@
|
|||
# Business Processes - Icinga Web 2 module
|
||||
|
||||
If you want to visualize and monitor hierarchical business processes based on any or all objects monitored by Icinga, the Icinga Web 2 business process module is the way to go.
|
||||
If you want to visualize and monitor hierarchical business processes based on
|
||||
any or all objects monitored by Icinga, the Icinga Web 2 business process
|
||||
module is the way to go.
|
||||
|
||||
Want to create custom process-based dashboards? Trigger notifications at process or sub-process level? Provide a quick top-level view for thousands of components on a single screen? That's what this module has been designed for!
|
||||
Want to create custom process-based dashboards? Trigger notifications at
|
||||
process or sub-process level? Provide a quick top-level view for thousands of
|
||||
components on a single screen? That's what this module has been designed for!
|
||||
|
||||
You're running a huge cloud, want to get rid of the monitoring noise triggered by your auto-scaling platform but still want to have detailled information just a couple of clicks away in case you need them? You will love this littled addon!
|
||||
You're running a huge cloud, want to get rid of the monitoring noise triggered
|
||||
by your auto-scaling platform but still want to have detailed information just
|
||||
a couple of clicks away in case you need them? You will love this little addon!
|
||||
|
||||
# Installation
|
||||
|
||||
Like with any other Icinga Web 2 module just drop me to one of your module folders and enable the `businessprocess` module in your web frontend or on CLI. Of course the `monitoring` module needs to be enabled and that's it, we have no farther dependencies.
|
||||
Like with any other Icinga Web 2 module just drop me to one of your module
|
||||
folders and enable the `businessprocess` module in your web frontend or on CLI.
|
||||
|
||||
Of course the `monitoring` module needs to be enabled and that's it, we have no
|
||||
further dependencies.
|
||||
|
||||
# History
|
||||
|
||||
The Business Process module is based on the ideas of the Nagios(tm) Business Process Addon written by Bernd Strößenreuther and available at http://bp-addon.monitoringexchange.org/. We always loved it's simplicity and while it looks pretty oldschool right now there are still many shops happily using it in production.
|
||||
The Business Process module is based on the ideas of the
|
||||
Nagios(tm) Business Process Addon written by Bernd Strößenreuther and available
|
||||
at http://bp-addon.monitoringexchange.org/. We always loved it's simplicity
|
||||
and while it looks pretty oldschool right now there are still many shops
|
||||
happily using it in production.
|
||||
|
||||
## Compatibiliy
|
||||
|
||||
We fully support the BPaddon config language and will continue to do so. It's also perfectly valid to run both products in parallel based on the very same config files.
|
||||
We fully support the BPaddon config language and will continue to do so. It's
|
||||
also perfectly valid to run both products in parallel based on the very same
|
||||
config files.
|
||||
|
||||
However, lot's of changes went on and are still going on under the hood. We have more features and new language constructs. We separated the config reader from the state fetcher in our code base. This will allow us to optionally support config backends like SQL databases. They are not faster than plain old text files, but they make it much easier to distribute configuration in a large environment.
|
||||
However, lot's of changes went on and are still going on under the hood. We
|
||||
have more features and new language constructs. We separated the config reader
|
||||
from the state fetcher in our code base. This will allow us to optionally
|
||||
support config backends like SQL databases. They are not faster than plain old
|
||||
text files, but they make it much easier to distribute configuration in a large
|
||||
environment.
|
||||
|
||||
## Improvements
|
||||
|
||||
### Speed
|
||||
|
||||
This module is definitively faster than the BPaddon used to be. No need for IDO caching or similar.
|
||||
This module is definitively faster than the BPaddon used to be. No need for IDO
|
||||
caching or similar.
|
||||
|
||||
## Todos
|
||||
|
||||
TODO: business impact of a specific object
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,4 @@
|
|||
# Collection of ideas
|
||||
|
||||
Filter "appserver" = host=*-rz-app-* & service=*jmx*
|
||||
|
||||
|
|
@ -5,6 +6,6 @@ Filter "appserver kunde1" = Filter["appserver"] & _host_customer = kunde1
|
|||
|
||||
Process "kunde1" = 1 of: Filter["appserver kunde1"]->group('hostname')
|
||||
|
||||
|
||||
Customer App * => host_name = customer-app-* => service_description = lx-jmx-* | service_description = lx-procs tomcat
|
||||
|
||||
Customer App = 1 of: Audi App *
|
||||
Loading…
Reference in a new issue