pax_global_header 0000666 0000000 0000000 00000000064 15014016017 0014505 g ustar 00root root 0000000 0000000 52 comment=d8295e306606dfd06f86bf0365e43394bd4afeb4
nagvis-nagvis-1.9.47/ 0000775 0000000 0000000 00000000000 15014016017 0014363 5 ustar 00root root 0000000 0000000 nagvis-nagvis-1.9.47/.github/ 0000775 0000000 0000000 00000000000 15014016017 0015723 5 ustar 00root root 0000000 0000000 nagvis-nagvis-1.9.47/.github/ISSUE_TEMPLATE/ 0000775 0000000 0000000 00000000000 15014016017 0020106 5 ustar 00root root 0000000 0000000 nagvis-nagvis-1.9.47/.github/ISSUE_TEMPLATE/bug_report.md 0000664 0000000 0000000 00000002227 15014016017 0022603 0 ustar 00root root 0000000 0000000 ---
name: Bug report
about: Create a report to help us improve
title: "[BUG]"
labels: bug
---
Verify first that your issue is not already reported [here](https://github.com/NagVis/nagvis/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc).
Complete all sections as described!
**Describe the bug**
**NagVis Version**
**Checkmk Version**
```console
e.g. 2.X.YpZ (CRE)
```
**Environment**
**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Run '....'
3. Execute '....'
4. See error
**Expected behavior**
**Actual behavior**
**Screenshots**
**Additional context**
nagvis-nagvis-1.9.47/.github/workflows/ 0000775 0000000 0000000 00000000000 15014016017 0017760 5 ustar 00root root 0000000 0000000 nagvis-nagvis-1.9.47/.github/workflows/ci.yml 0000664 0000000 0000000 00000000332 15014016017 0021074 0 ustar 00root root 0000000 0000000 name: CI
on: [push]
jobs:
phpstan:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: PHPStan Static Analysis
uses: php-actions/phpstan@v3
with:
path: .
nagvis-nagvis-1.9.47/COPYING 0000664 0000000 0000000 00000036023 15014016017 0015422 0 ustar 00root root 0000000 0000000 GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and
modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.
You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.
In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.
5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.
10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
nagvis-nagvis-1.9.47/ChangeLog 0000664 0000000 0000000 00000234346 15014016017 0016151 0 ustar 00root root 0000000 0000000 1.9.47
* FIX: Don't show complete backtrace if crashing. Now the backtrace is being logged to the apache error log
* FIX: Fix potential XSS via WYSIWYG editor. Now the option to edit these such elements is moved to a specific
permission and only administrators can use this editor per default. (CVE-2024-47090)
* FIX: Fix possible livestatus injection via dynmaps (CVE-2024-38866) (#398 Thanks to Shortfinga)
(CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:L)
1.9.46
* Feature: add option to verify session cookie via curl. Before when having allow_url_fopen
disabled, NagVis was not able to verify the session cookie. Now you can use curl to verify
the session cookie. Depending on your distribution the curl extension can be installed differently.
* Checkmk BI backend: Add option 'site_internal_auth' to enable the Checkmk 2.4 site internal
authentication. This option is configured automatically for the sites local
backend ('backend_[site]_bi') which is created automatiocally in Checkmk sites.
1.9.45
* FIX: Fix XSS on support info page (Thanks to jmacario24)
* FIX: Fix not working cookie session timestamps validation introduced with 1.9.43 in
when localhost is blocked or takes a long time to resolve
1.9.44
* FIX: Fix not working cookie session timestamps validation introduced with 1.9.43 in
some HTTPS scenarios
1.9.43
Core:
* FIX: Fix error when entering correct proxy URLs with ports and proxy schemas.
Entering correct proxy URLS with ports and one of the following schemas
(tcp, udp, unix, udg, ssl, tls) would cause an error (Invalid format given)
even though these proxies are correct.
Frontend:
* FIX: URLs still pointing to mathias-kettner.de documentation are now pointing to
the Checkmk documentation (docs.checkmk.com).
* FIX: Support forum links to no longer existing forum (monitoring-portal.org) are
now pointing to the Checkmk forum (forum.checkmk.com).
Security
* Added cookie session timestamps validation when Nagvis is run within Checkmk
1.9.42
Security:
* FIX: Fix various XSS issues (std_table.php gadget, malicious graph elements, service names and script outputs).
CVE is requested and will be added once available. (CVSS score 8.8)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
* FIX: Fix potential RCE due to being able to upload and configure a malicious map as authorisation_multisite_file.
You can no longer upload such maps and the maps path is excluded from the authorisation_multisite_file upload
path.
* FIX: Insecure password hashing algorithm for dedicated NagVis users (CVSS score: 5.1)
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
* FIX: Leak of installation path in error message
* FIX: Make cookie hash comparison timing safe
1.9.41
Frontend:
* FIX: Fix PHP 5.4 compatibility issue (syntax error, unexpected 'list')
* Added option "line_width" to default section of global config
* FIX: Fix failing reporting of errors when messages contained special characters
1.9.40
Core:
* FIX: Fix PHP 5.4 and 5.5 compatibility issue (Fatal error: Arrays are not allowed in class constants)
1.9.39
Core:
* FIX: Fix PHP 5.4 compatibility issue (syntax error, unexpected ':', expecting '{' in)
* FIX: Fix PHP 8.2 deprecation warnings caused by std_speedometer gadget
1.9.38
Frontend:
* FIX: Fix XSS vulnerability
* FIX: Fix PHP 8.2 deprecation warnings caused by shapes on automaps and host alias
* FIX: Fix PHP 8.2 deprecation warnings caused by gettext.inc
1.9.37
Frontend:
* FIX: Fix "mb_convert_encoding(): Argument #2 ($to_encoding) must be a valid encoding,..."
* FIX: Fix "implicit conversion from float" on overview page background image preview
* FIX: Sound events, which are triggered e.g. in case an object turns CRITICAL, now work in modern
browsers (Edge 12+, Firefox 20+, Internet Explorer 9+, Opera 15+, Safari 4+, Chrome)
1.9.36
Core:
* FIX: Fix various PHP 8.2 incompatibilities
* FIX: MySQL 8.0 - Fix "Invalid JSON response" (#348 Thanks to KayckMatias)
* FIX: PHP 8.1 Deprecated: Implicit conversion from float (#347 Thanks to KayckMatias)
Frontend:
* FIX: Fix context menu not hiding in some situations (#333 Thanks to euniceremoquillo)
Geomap:
* Fix PHP 5.4 incompatibility (#341 Thanks to loocars)
1.9.35
Core
* FIX: Fix PHP 8.2 various incompatibilities
* FIX: Fix PHP 8.1 fsockopen incompatibility (#337 Thanks to loocars)
* FIX: Fix Checkmk Snapin displaying status output when hovering the state icon
* FIX: Disable state preview for worldmaps in Checkmk snapin. The state
previews do not work correctly for worldmaps. To be able to calculate the
state preview, we would need the area of the map the user would see when
opening the map. To be able to do so, we need this information when
rendering the snapin: a) the viewport size and b) the NagVis javascript
code. Both is not available in this situation, so we can not correctly
render it. In the past the computation was done based on information cached
in NagVis, which could produce aggregated states, but these might be
misleading as they did not necessarily represent the state of the objects
you see in the map.
1.9.34
Core:
* Checkmk BI backend: Add verify_peer, ca_path and verify_depth options to configure
parameters for HTTPS certificate verification (#317 Thanks to loocars)
Frontend:
* FIX: Fix PHP 8.1 incompatibility in different configuration dialogs
Worldmap:
* FIX: Fix PHP 8.1 incompatibility (#316 Thanks to loocars)
Security:
* FIX: Fix SSRF (triggerable by admin users) in geomap.php (#319 Thanks to dontqwerty)
* FIX: Fix arbitrary file read in (#322 Thanks to Shortfinga)
* FIX: Fix type juggling vulnerability in cookie hash processing (#321 Thanks to Shortfinga)
* Add option to enable compatibility with Checkmk 2.2 cookies. This needs to
be enable with a new configuration option (logon_multisite_cookie_version).
This setting will automatically be enabled when NagVis is shipped together
with Checkmk. (#323 Thanks to Shortfinga)
1.9.33
Frontend:
* FIX: Weathermap lines of Checkmk monitored network interfaces displaying
network traffic in bytes instead of bits
* FIX: Weathermap lines of Checkmk use 1000 as base instead of 1024
(#315 Thanks to soeren-gugel)
1.9.32
Core:
* FIX: Fix PHP 8.1 incompatibility
1.9.31
Frontend:
* FIX: Add support for services with single quotes in names (#314 Thanks to Yogibaer75)
* FIX: Fix scrolling on overview page (#307 Thanks to ArminRadmueller)
1.9.30
Frontend:
* FIX: Fix reload of gadgets in chrome in some situations (#305 Thanks to gzalo)
* FIX: Fix line_label_y_offset on weather map line labels (#301 Thanks to
corus87)
* Remove builtin "on-demand-filter" header template. It was introduced for
supporting NagVis backed "network topology" views in Checkmk, which are not
used anymore from Checkmk. Since the template relies on an outdated jquery
and select2 3rd party dependency and there does not seem to be a use for it
anymore, we drop it now.
1.9.29
Security:
* FIX: Fix possible deletion of arbitrary files (CVE-2021-33178)
An authenticated user with enough permissions to access the NagVis
ManageBackgrounds endpoint, such as admin, can delete arbitrary files on the
server limited by the rights of the Apache system user. In OMD environments,
such as Checkmk, this is limited to files owned by the site user. In other
environments this may affect all files that are writable by the web server
user.
1.9.28
Frontend
* Add support for svg image based icon sets (#298 Thanks to itsul)
* FIX: Fix off-screen text input boxes in popups (#300 Thanks to jacobbaungard)
* FIX: Fix weathermap lines handling "Bit" of Checkmk checks (#296 Thanks to BlackFlash5)
1.9.27
Core
* FIX: Fix PHP 7 (or older) incompatibilities introduced with 1.9.26
(Error (Error): Call to undefined method ReflectionType::getName())
1.9.26
Core
* FIX: Fix PHP 8 incompatibilites
Worldmap
* Add new option filter_group for filtering host objects on a worldmap based
on the membership of hosts in a host group.
1.9.25
Core
* FIX: Fix map corruption regression introduced with 1.9.24
This issue was triggered by objects on a map having a numeric "object_id"
attribute. The issue resulted in map configuration files without "define
global" object at the beginning of the map. In this situation NagVis will
show an error like "Error: (0) in_array() expects parameter 2 to be array, bool given".
You will have to find the problematic map config (.cfg) and readd the global
section.
* FIX: Fix possible map corruption caused by object ID cleanup (#280)
* FIX: Fix missing socket string in some livestatus backend error messages
Frontend
* FIX: Fix editing map options when object_id not set in global section object
1.9.24
Core
* FIX: Fix more PHP 7.4 incompatibilites (#265)
(This fixes one issue related to the PDO auth module and one issue related
to map configurations with numeric object_id attributes.)
* FIX: Fix Checkmk BI backend error when pending services are in downtime
(Undefined index 'downtime' was shown)
1.9.23
Frontend
* Make NagVis compatible with Checkmk 2.0 auth cookies
1.9.22
Core
* FIX: Fix error handling of DB backends when DB opening failed
(Undefined property: CorePDOHandler::$dsn) (#267)
Frontend
* Colors with alpha channel are now allowed (format: #RRGGBBAA) (#270)
* FIX: Improve validation of file names in several places to prevent input of
not printable characters.
Worldmap
* Improve recently introduced textbox scaling according to zoom (pull #263)
1.9.21
Frontend:
* FIX: Additional fix for weathermap lines byte/bit handling for Checkmk
interface checks (issue #256)
* FIX: Fix random error "NotFoundError: Node.removeChild"
* FIX: Fix relative coordinate handling (issue #250)
* FIX: Remove "\r", "\t" and 0x00 - 0x1F from multiline text boxes (issue #258)
Worldmap:
* textbox scaling according to zoom (scale_to_zoom option) (pull #255)
1.9.20
Core:
* Drop some PHP < 5.2 compatibility code for json encoding / decoding
* FIX: PHP 7.4 compat fix (Trying to access array offset on value of type int)
1.9.19
Frontend:
* FIX: Fix weathermap lines displaying byte/s instead of bit/s for Checkmk
interface checks (issue #230)
* FIX: New textboxes introduced with 1.9.18 broke the map configs (issue #245)
* FIX: Fix potential javascript error when zooming (issue #242)
1.9.18
Core:
* Add new map global option "ignore_linked_maps_summary_state" (issue #223)
* FIX: Worldmap max_zoom is now 20 (issue #228)
Frontend:
* Weathermap lines: New options line_label_in/line_label_out to configure
the name of the perfdata values to use for in/out traffic (#244)
* Weathermap lines: Use "CRITICAL" color when no perfdata is available (#243)
* Sidebar map states now indicate acknowledgement and downtime states (issue #221)
* Textboxes can now be edited using a simple WYSIWIG editor (issue #216)
* Worldmap: render middle sections of long lines
1.9.17
Core:
* FIX: Fix PHP 5.3 incompatibility introduced with 1.9.16
* FIX: Fix IE 11 incompatibility on worldmaps in relation to lines
which was introduced with 1.9.13
* FIX: Fix incompatibility with Check 1.6 auth cookies of users with special
characters in the user ID
1.9.16
Core:
* Add support for Encrypted livestatus. You can now configure "tcp-tls:[address]:[port]"
as socket address and control the TLS verification using the new backend specific
settings "verify_tls_peer" and "verify_tls_ca_path".
1.9.15
Core:
* FIX: "You are not permitted to access this page (ChangePassword/view/)" for users (issue #215)
Frontend:
* FIX: Fix IE 11 incompatibility regression introduced with 1.9.13
1.9.14
Core:
* MKBI backend: Use "htmlcgi" URL/path for building links to the Checkmk GUI
(Aggregations used the base_url, which should not be used for user URLs)
Worldmap:
* Consistent page reloads: center + zoom of the map kept in URL
* Memory and performance optimization: line rendering - clip long lines protruding out of viewport
* Memory and performance optimization: fix getMapObject SQL query (lng/lat rectangle)
Frontend
* FIX: Fix creating users when mbstring extension is not available
1.9.13
Worldmap:
* Configurable OpenStreetMap tile server URL (worldmap_tiles_{url,attribution})
* OpenStreetMap tile colors can now be dimmed using the
worldmap_tiles_saturate configuration option so that larger colorful
backgrounds do not interfere with the map objects.
* Optional 2nd map layer (satellite imagery)
* FIX: Worldmap textbox visibility per zoom level
* FIX: The "clone object" functionality did sometimes break with an error
message like "Invalid argument supplied for foreach()"
(Thanks to Vojtech Pithart for taking the time to improve the NagVis worldmap!)
1.9.12
Core:
* FIX: Allow "*" character to be part of backend dbpass values
* Multisite Snapin: Reworked data export API to snapin. The new API is
compatible with Checkmk 1.6b2 and newer.
Frontend
* FIX: Fixed incompatibility with PHP 7.2 (count(STRING)) when creating roles
Geomap:
* Improved error handling of CSV lines with less than 4 fields
1.9.11
Frontend
* FIX: Weathermap lines now respect the configured error colors
* FIX: Fixed wrapping of long map names in sidebar
1.9.10
Frontend
* FIX: Network error popups are now shown when an error occurs and hidden again
automatically when a subsequent call succeeds
1.9.9
Frontend:
* FIX: Fixed possible "Cannot read property 'conf' ... Line 4383" error when
trying to interact with the map while it is initially loading
* FIX: Fixed incompatibility with PHP 7.2 when creating new users
* FIX: Fixed loading sounds when using non standard HTTP/HTTPS ports
* FIX: Fixed "JavaScript Error : checkHideMenu" on worldmaps when header is
disabled
1.9.8
Frontend:
* FIX: Fixed incompatibility with PHP 7.2 in Dwoo 3rd party code
* FIX: Fixed outdated Monitoring portal link in header menu
Automap:
* FIX: Fixed automaps filter_group when using ndomy/pgsql backend
Installer:
* FIX: Prevent error when trying to replace old map options and no map exists
1.9.7
Frontend:
* FIX: Fixed object sort by state regression in 1.9.6
1.9.6
Core:
* Dynamic map objects can now be sorted by state (Using the new map global
settings dynmap_sort and dynmap_order)
* FIX: Improved error handling when trying to use aggregation objects with
backends that don't support these object types
* FIX: Fixed "A non-numeric value encountered" when creating new automaps
without width/height attributes. A workaround would be to add
height/width options manually to the map configuration.
1.9.5
Frontend:
* FIX: Fixed wrong hostname label in service hover menus
* FIX: Fixed repeated zoom of background image on state updates
Worldmap:
* FIX: Fixed errors when saving viewport as new map
* FIX: Fixed rare issue when cloning just added objects
* FIX: Fixed broken worldmap when using relative objects
Installer:
* FIX: Fixed displaying wrong backend option "-b" in summary output
* FIX: Don't display "update backend configuration" confirm in quiet mode
* FIX: Don't fail updating map configurations when no maps are defined
* FIX: Don't register demo rotation when using the "-o" option
1.9.4
Core:
* List of hover menu childs (e.g. services in host object hover) can now be
left unsorted (keep original sorting). This is useful for aggregation objects
where the single elements have a defined order and should not be sorted by state
(Configure this per object by adding the attribute hover_childs_sort=k).
Frontend:
* On demand automaps: Hostgroup filter in header menu is now a searchable dropdown field
* FIX: Fixed moving textbox objects in IE
1.9.3
Core:
* Multisite auth: Dropped support for WATO folder permissions
(See
http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=6a1845bcba346111c391f28dfc3214b0e5dd8876)
Frontend:
* std_html_bar Gadget: Added new optional parameters "perfdata" to specify
the perfdata index to show and "border" to enable/disable the border of the
bar using the values 0/1
1.9.2
Core:
* The default values for the "url" option of map objects can now be
configured in the map global sections using the options
host_url, hostgroup_url, service_url, servicegroup_url, map_url,
dyngroup_url and aggr_url
1.9.1
Core:
* FIX: Fixed incompatibility with pecl-http (Cannot redeclare http_redirect())
* FIX: Fixed duplicate global section in sample automaps after editing
Frontend:
* FIX: Fixed wrong positioned labels of gadgets
* FIX: Added missing stale images of the std_small iconset
* FIX: Fixed map update (background color, title, favicon) on changed state
1.9
Core:
* MKBI backend: New option "auth_secret_file" to read the secret from a file
1.9b19
Core:
* FIX: Fixed "hanging" user/role related actions with older SQLite versions
(e.g. seen on CentOS 6 or older)
Frontend:
* FIX: Fixed problems while editing roles of users
* FIX: Fixed checkHideMenu is not defined issue when header menu is disabled
Installer:
* FIX: Fixed install of apache config to /etc/apache2/config-available
instead of /etc/apache2/config-available/conf.d
1.9b18
Core:
* FIX: Fixed additional PHP 5.3 compatibility issue with new pgsql/ndomy code
1.9b17
Core:
* FIX: Fixed PHP 5.3 compatibility issue with new pgsql/ndomy code
1.9b16
Core:
* FIX: Fixed broken service group processing with pgsql/ndomy backends
Frontend:
* FIX: Temporary template files/directories are now created only user writable
1.9b15
Core:
* New backend "pgsql" to connect with PostgreSQL databases of Icinga
(Thanks a lot to Peter Pentchev for doing the work!)
* FIX: Security fix: Authenticated users could read contents of local files
by opening a custom URL (#29). Only https/http URLs can now be used.
* FIX: Security fix: Only configured ULRs can be fetched using the Url module (#29)
1.9b14
Frontend:
* FIX: Fixed wrong positioning of icon labels during object refresh (when no
state but plugin output or perfdata changed) (#81 #93)
* FIX: Fixed too small stale icons of the std_medium iconset
1.9b13
Frontend:
* FIX: Fixed Javascript error when closing the object edit dialog after
using the color picker
* FIX: Now really fixed refresh of changed map properties (like background image)
* FIX: Fixed possible XSS in std_table.php gadget (#91, CVE-2017-6393)
(If you want to solve this issue for your installation without updating NagVis,
you can remove the file std_table.php from your installation. It is
only needed if you use the std_table.php gadget.)
1.9b12
Frontend:
* FIX: Fixed possible empty maps when manually disabling the header menu
* FIX: Fixed refresh of changed map properties (like background image)
Core:
* FIX: Fixed NDO/IDO MySQL backend compatibility with ONLY_FULL_GROUP_BY MySQL
mode (Thanks to SteScho)
* FIX: NDO/IDO MySQL backend: Fixed problem connecting to database
* FIX: NDO/IDO MySQL backend: Fixed problem reporting database connection issues
1.9b11
Core:
* FIX: Livestatus backend was calculating wrong services for host group
objects having the "exclude_members" attribute configured
* Check_MK BI backend: Added "timeout" parameter to adapt the default
5 second timeout
* NDO/IDO MySQL backend: Now using mysqli PHP functions (Thanks to SteScho)
* NDO/IDO MySQL backend: Fixed compatibility with ONLY_FULL_GROUP_BY MySQL
mode (Thanks to SteScho)
Frontend:
* FIX: Fixed wrong positioning of icon labels (regression since ~1.9b9)
* FIX: Fixed lines using ack_bgcolor (when configured)
* FIX: Fixed wrong visualization (hover text, line color) of acknowledged services
* FIX: Overview page: Fixed disappearing maps on state changes
* FIX: Sidebar menu: Deleted maps were still visible in sidebar
* FIX: Fixed broken error message in case of communication issue during updates
1.9b10
Core:
* CoreLogonMultisite: In case a user is already authenticated via the web
server, the authenticated user name is treated as authenticated, just
like when using LogonEnv. If no user is authenticated, the regular
Check_MK multisite login is done
Frontend:
* Added localization for Simplified Chinese (zh_CN) (Thanks to Kevin Jin!)
* FIX: Fixed removal of labels and hover menus right after editing objects
* FIX: Fixed repositioning of (line) labels on object updates
Worldmap:
* FIX: Fixed broken worldmap (duplicate global section) after saving viewport
* FIX: Fixed "TypeError: this.objects[parentObjId] is undefined" issue on
worldmap when having long lines and zooming in a lot
1.9b9
Core:
* FIX: CoreAuthorisationModGroups - Logout of users is now possible
Frontend:
* FIX: Fixed missing context menu for stateless lines
* FIX: Fixed line actions in case of scrolled browser windows
* FIX: Closing eventual open context menu when dragging an object
* FIX: Gadgets can now be dragged again
Automap:
* filter_by_state=1 can now be used with automaps using the NDO MySQL backend
* FIX: Fixed possible error "TypeError: this.objects[parentObjId] is undefined..."
* FIX: Fixed automap issue when object having redundant links
Worldmap:
* FIX: Fixed broken left click URLs of objects after editing attributes
until next reload
* FIX: Fixed keeping lock state of objects after editing object attributes
1.9b8
Core:
* MK BI backend: Now prints an error message when trying to use it with
objects that are not aggregations.
* NDO MySQL backend: Filtering out legacy objects from DB (setting is_active filter)
* FIX: Updated php-gettext to 1.0.12 and commented out unused code because it contains
some exploitable PHP code which could be used to inject code using modified .mo files.
However, NagVis has never used these functions, so was never affected by this issue.
Frontend:
* FIX: Fixed error in ad-hoc automaps (Network Topology in Check_MK) during state updates
* FIX: Prevent JS/CSS caching issues during updates of NagVis
* FIX: Improved error handling in case of modifying objects which
backends report issues
* FIX: Improved error handling in case of missing backend configured
* FIX: Fixed keeping unlisted values of dropdowns (object names, backend_id)
* FIX: Cleaning up host/service attributes when changing the backend_id
* FIX: Fixed broken hover_delay (JS error when hovering an object)
* FIX: Multisite Snapin: Fixed wrong EDIT link
* FIX: Improved error handling in case of internal server error (500)
* FIX: The host and service downtime/acknowledgement URLs in context menu
can now be configured via main configuration
Automap:
* FIX: Fixed error when searching for objects on non initialized automaps
Worldmap:
* FIX: Fixed permanent error state showed by automap objects on worldmaps
1.9b7
Fronted:
* FIX: Fixed "function sidebarUpdatePosition is not defined" when header not shown
* FIX: The context menus can now be disabled again (e.g. using URL var context_menu=0)
Core:
* FIX: Fixed some compatibility issues with PHP 7. NagVis should work with it.
The NDOMySQL backend is known not to work with PHP 7. Use MKLivestatus instead.
1.9b6
Frontend:
* FIX: Fixed possible wrong scaling of icons when using NagVis zoom
* FIX: Fixed moving objects on zoomed maps
* FIX: Fixed line create indicator position on zoomed maps
* FIX: Labels of weathermap lines were rendered multiple times overlaying
eachother during state / perfdata changes
* FIX: Map permissions where mixed up (delete permissions was granted when
adding view permissions, ...)
* FIX: Added missing "modify map" menu for users with limited edit permissions
* FIX: Fixed broken add/modify page for users with limited edit permissions
* FIX: Template management: Fixed wrong options shown on result page after editing
Core:
* FIX: Fixed error with Icinga 2 when querying for not existant objects
(happened with default worldmap in previous versions)
* FIX: Livestatus backend is now returning correct host info for pending hosts
1.9b5
Frontend:
* FIX: Multisite Snapin: Fixed broken snapin contents
* FIX: Fixed the bandwith showing weathermap lines showing BW values again
* FIX: Fixed update of the hover menu child infos while a map is open
* FIX: Fixed broken header toggle icon on on-demand-automaps
* FIX: Fixed wrong scaling of object labels in IE
Core:
* FIX: Negative lat/long coordinates can now be configured
* Changed handling of deprecated map object attributes: They are silently
ignored by NagVis now. We inform users about deprecated (useless)
attributes in the ChangeLog and will mark old options in the documentation,
but the map loading will not be affected by the deprecated options anymore
* BI-Backend: Is now handling the acknowledgement and downtime infos of BI
* FIX: Fixed possible broken global section during editing of maps when an
object on the map got an object ID starting with "0e."
* FIX: Added proper error message when trying to use dynamic groups with NDO
MySQL backend (which does not support dynamic groups)
* FIX: Only reading map configuration files with lower ".cfg" suffix. Maps
having e.g. an upper case ".CFG" suffix caused problems in NagVis and
will not be read anymore. Please rename your map config files to match
the ".cfg" suffix.
Automap:
* FIX: Fixed exception when filtering maps by non existant host groups. Now
the map is just left empty instead of raising an exception.
1.9b4
Frontend:
* FIX: Fixed JS error in case of re-rendering stateless objects
* FIX: Fixed JS error "yOffset is not defined" when rendering lines of type 14
* FIX: Fixed wrong label for inbound absolute traffic on lines of type 14
Core:
* FIX: Fixed issue "The attribute is unknown." when adding/editing objects
with PHP < 5.4
1.9b3
Core:
* FIX: NDO/IDO backend: Correctly excluding deprecated objects from hosts and
hostgroups (having is_active=0 set)
Frontend:
* Supporting some more older browsers. Very outdated browsers will get an
error message when they don't support essential features
* Multisite Snapin: Added link to overview page for creating / editing maps
* FIX: Fix Undefined variable: list when there is no map
Geomap:
* Improved error handling when creating geomaps but missing width or height
parameters
Automap:
* Added missing option "prism" to overlap parameter
* FIX: Detecting and preventing loops in automap
(Fixes PHP error: Allowed memory size ... bytes exhausted)
1.9b2
Core:
* FIX: Improved handling of not existing objects when using Test backend
Frontend:
* Using color picker for color configuration in global settings
* Removed mostly useless "create background" form (you can use the background_color)
* Grouped permissions in role permissions config in tabbed navigation
* FIX: Fixed icon_size related PHP errors in some PHP versions (implode error)
* FIX: Fixed issue in backend management when adding/editing backends
* FIX: Fixed usability issues when selecting object names from name lists
while adding / editing objects
* FIX: Fixed js error when weathermap lines get no perfdata at all
* FIX: Fixed form submit confusions in role and user management dialogs
Worldmap:
* FIX: Ignoring min_zoom/max_zoom when min_zoom equal or larger than max_zoom
1.9b1
Core:
* Added option only_permitted_objects to restrict the objects a user can see
to the objects which a user is a contact for. This feature is currently
used only with the livestatus backend. It's disabled by default to keep
the default behaviour of NagVis. Thanks to norbert for providing the patch!
* Stale object states have the same state weight as when they are not stale
now. In previous versions the stale states were treated as being "less"
worse, but this seem to be logically wrong to me. If you want the old
behaviour back, you might change the state weights in your main
config.
* Deprecated unused config option header_fade / headerfade
* Removed unusued config option line_arrow from all objects
* Removed unused config option controls_size from main configuration
Worldmap:
* Introduced new interactive worldmaps. You can use these maps to position
all kind of NagVis objects on a geographical maps where you can browse
interactively in (zooming, panning, ...)
Automap:
* Reimplemented missing "filter_by_state" functionality
Frontend:
* Showing header menu on full page error messages to give the users the
option to navigate away from the error situation
* Header menu dropdown menus now open on click instead of hover which is
hopefully more user friendly as it is more unlikely to open/close the
menu unintended
* The sidebar is now toggled using a small control below the NagVis logo
* Reworked frontend dialogs to show form error messages directly in the dialog
instead of showing the old error popup window
* The map / object editing dialog is now using a tab navigation to reduce
the number of options shown at once for a more user friendly handling
* It's now possible to use the macro [obj_display_name] in child objects
in hover menus of hosts or any other objects having childs (Thanks to
Andreas Steinel)
* Dropped jsGraphics line rendering (browser needs to support canvas now)
for being able to use lines within NagVis
* Maps are not reloaded anymore when adding/editing objects. Only the
affected objects on the map are reloaded
* Overview: Broken map configs do not prevent to open the map anymore
* Lines: Are now rendered nicely on high resolution devices (e.g. 4k screens)
* Lines: Re-implemented borders round the lines for better visibility
* Lines: Removed line action areas (small dotted boxes). The line related
actions (hover, context, link) are now possible on the whole lines
* Removed need to confirm object deletion (you already need at least two clicks:
open the context menu, maybe unlock, and then click on delete)
* Adding/modifying map objects does not trigger map reload anymore. This makes
editing maps much more fun since you can do your work much faster! :-)
* Labels: When center/Bottom positioned labels are dragged, the resulting
coordinates will still be relative ones to the object coordinates
* Labels: When dragging relative positioned labels, the object is highlighted
* Showing hint about absolute/relative coords while dragging objects
* FIX: Stateless lines now handle line_color and line_color_border correctly
* FIX: Removed useless weathermap line type selections from stateless lines
* FIX: Fixed annoying browser warning message when reloading pages which
are shown up right after logging in to NagVis
* FIX: Fixed duplicate map config processing for rendering the header menu
* FIX: Fixed js error when moving an object out of the screen
1.8.6
Core:
* FIX: Template objects can now be used recursive
* FIX: Fixed missing Url/view/* permission. It was not possible to permit
non admin users to access external URLs in rotation pools without this
permissions.
1.8.5
Core:
* FIX: Livestatus Backend: Fixed exception handling when fetching services
which are marked to be in a downtime, but the downtime defails can not
be fetched
* FIX: Fixed missing Action/perform/* permission for auth databases created
with NagVis versions newer than NagVis 1.7b3. All auth databases which
have been created before, have the Action/perform/* permission available.
It was not possible to permit user not having the */*/* permission to the
acknowledgement and custom actions via the context menu
Frontend:
* Multisite Snapin: Improved performance when a lot of users use the snapin.
The snapin contents were calculated on each access in the past. Now, the
snapin contents are cached for 15 seconds. This gives a good performance
boost when multiple users have use the snapin while having access to the
same set of maps.
1.8.4
Core:
* FIX: BI Backend: Fixed wrong summary state of aggregation objects when
not using the worst aggregation function. NagVis is now using the summary
state provided by the backend
* BI Backend: it's now possible to use URLs configured in object attributes
1.8.3
Core:
* FIX: Fixed error in example custom actions for RDP and SSH
* FIX: Fixed showing wrong options for [defaults] hoverchildssort global cfg
* FIX: Fixed error with Check_MK integration when user is not permitted to
write a WATO folder related map
* FIX: Fixed choosing services from test backends
Automap:
* FIX: The pseudo map root node is also shown when another host is the root
* FIX: The pseudo map root node can be made root again by context menu
* FIX: Fixed setting too many view options when changing the root node
Frontend:
* FIX: Forcing IE to always use the last available engine
* FIX: Fixed dynmap_object_types exception after creating a dynmap
(the option is not declared as being mandatory anymore)
* FIX: Maps with source related problems (like geomaps without location file)
can now be deleted again using the map management dialog
* FIX: Don't raise whole page errors when fetching of container URLs failed
instead the javascript error message is shown in the container
* FIX: Fixed too many context actions showing up for non host objects
* FIX: Hiding eventual open color pickers on closing frontend windows
* FIX: It's possible to put javascript code in labels or textboxes again
1.8.2
Core:
* Improved handling of map config files without read permissions on overview
page and in header menu (such maps are simply hidden)
* NagiosBP-Backend: Fixed exception when component state is not known
Frontend:
* FIX: Map import: Added missing validation of map name format
* FIX: Hiding "loading..." animation when maps are disabled on overview page
* FIX: Fixed sorting of maps on overview page
* FIX: Fixed js exception "g_map_names" not defined when having
header_show_states set to disabled
* FIX: Fixed overlapping sub-hover menus for adding icons/lines
1.8.1
Core:
* It is now possible to configure external URLs within rotations in two types:
a) embed it directly on the page: [http://url...]
This is useful when including only snippets of HTML without own styles,
scripts etc.
b) show the URL within an iframe: [iframe:http://...]
This is useful when including a whole webpage with own styles and scripts
Frontend:
* FIX: Fixed form processing (e.g. user- and role management, pw change dialogs)
* FIX: Cached ajax queries last no longer than 30 seconds now
1.8
Core:
* All stateful objects can now be rendered as gadgets
(Although there is no gadget available yet which is useful for objects
which have no perfdata. But you can build one now)
* The option gadget_type is now deprecated as the type is automatically detected
* Gadgets can use object member states now
Gadgets are now called with mixed POST request where the GET vars used in previous
versions are still handed over to the gadgets per GET parameters to
maintain compatibility. More complex parameters are now given to the
gadget with POST vars. For example there is the POST var "members" now,
which provides information about the object members states.
(e.g. to be able to parse units like Kb/s, even when they are not allowed
according to nagios plugin guidelines)
* FIX: gadgets_core.php perfdata parsing allows "/" for perfdatas UOM now
Frontend:
* Huge update of GUI design for a more consistent look n feel
* Overview page uses whole page width (floating layout) for maps
* Deprecated "cellsperrow" configuration option in [index] section
* URLs of shape images can now be configured via configuration dialog
* Added std_table.php gadget which can render state tables for any stateful object type
(Thanks to Thibault Cohen for providing the idea and base code!)
* Usability fix: Header dropdowns now only close when clicking somewhere out
of the menu instead of hiding when moving the mouse out of the menu
* Reworked map management dialog for more comfortable form handling (errors, validation etc.)
* Map sources can now only be selected during map creation via GUI. When you like to
change map sources for an existing map, you will need to to it by modifying the
map configuration files directly. But this should be a very rare situation
* FIX: Fixed exception when trying to define Multiple/Other values for "sources"
* FIX: Fixed relative label positioning (center, bottom) on first page load sometimes wrong
1.8rc3
Core:
* New backend: Check_MK Business Intelligence (mkbi) which can be used to
add Check_MK BI aggregations to your maps
(Configure this new backend, then add "Aggregation" objects to your maps)
* FIX: Livestatus: Fixed wrong state aggregation for dynamic service groups
Frontend:
* FIX: Changed sorting of maps in sidebare/header to ignore case of names (natural sorting)
* FIX: Fixed exception preventing editing the map options of geomaps
1.8rc2
Core:
* FIX: Aliases were not processed for host- and servicegroups
* FIX: Fixed mixed up version number in 1.8rc1
1.8rc1
Geomap:
* FIX: Fixed handling of multiple backends on one geomap
Core:
* FIX: Livestatus: Fixed wrong state aggregation for servicegroups
* FIX: Livestatus: Fixed check_command value of host/services
Frontend:
* Service-/Hosttags are shown in default hover template now (when available)
* Taggroups, values and their titles can now be used to be displayed in hover menu
(When using NagVis in an OMD environment together with Check_MK 1.2.5i6p4 or newer)
* Reworked main configuration editing dialog to be much more user friendly
* Consolidated styling of the popup dialogs
* FIX: Background images could not be deleted
* FIX: Natural sorting object names in add/modify dialog
1.8b7
Frontend:
* Highlighting the current map in sidebar and header dropdown menus
* FIX: The zoombar is now rendered below the header menu layer
* FIX: The line_arrow is now configured using a dropdown field
Core:
* Multisite Authorisation: It is now possible to specific manage map view/edit permissions
* Livestatus: Added missing space OutputFormat livestatus header (worked before, but was
implementing the livestatus protocol strictly not strict
* Livestatus: Using "name" column instead of "host_name" when querying the hosts table now
(Also worked as implemented before, but was using non documented livestatus behaviour)
Automap:
* Now using line_color and line_width for connectors from map global definitions
* Now using label_(show|border|background|maxlen) definitions from map globals
* FIX: Removed useless "Make root" link for connector lines
* FIX: Removed map editing options from menus which make no sense
* FIX: Removed line_type option from map global definitions
Geomap:
* FIX: Removed map editing options from menus which make no sense
* FIX: Removed not working geomap types osmarender and cycle
* FIX: Removed global map parameter map_image. Technically it could be changed,
but seems a bit senseless for geomaps
(where the background is rendered automatically)
* FIX: Tried to fix geomap_zoom parameter, but does still not work with all zoom levels
1.8b6
Geomap:
* Geomaps support multiple backends as object source now
1.8b5
Frontend:
* Multisite snapin: Parent maps in tree mode can now be clicked to open the map
* Add support for secure and httponly cookies (sesscookiehttponly, sesscookiesecure)
(Thanks to mikael.falkvidd@op5.com for the patch)
* FIX: Fixed links of rotation steps (always linking to last step)
* FIX: Hiding empty "Action" header menu entry on overview page
* FIX: Trying to fix too long map list in dropdown menu (menu is scrollable now)
* FIX: Fixed small styling issues in header menu
Core:
* Dealing with the staleness value of hosts and services as a new sub-state
(like downtime / ack); The staleness marks the state of a host/service as outdated
* FIX: Deleting no longer required map permission entries (e.g. of maps deleted
by hand) before rendering the manage roles dialog
* FIX: Updating map permissions during renaming of maps (not renaming via CLI)
1.8b4
Frontend:
* Multisite snapin now transports downtime / acknowledgement information
* FIX: Custom context actions: Conditions, e.g. filtering by custom vars, did not work
* FIX: Fixed zoom of text in textbox objects in chrome
* FIX: Not altering relative object coordinates when zoom_scale_objects is
disabled
* FIX: Disabling save button during adding new objects to prevent double adding
* FIX: Roles can not be deleted when used by users
* FIX: Last assigned role can now be removed from a user
Automap:
* FIX: Removed debug code which might prevent map rendering in some cases
1.8b3
Frontend:
* Added option "zoom_scale_objects" to default section of global config to
allow users to control the scaling behaviour of zoomed objects. By
default the whole maps is zoomed like in previous versions. But when
zoom_scale_objects is set to 0, the map objects and labels are not
resized, but only repositioned according to the given zoom factor.
* FIX: Fixed broken NagVis Multisite sidebar dashlet
* FIX: Fixed showing URLs as hover menus (hover_url option)
* FIX: Coord calculation - better validation in internal code
(Thanks to Daniel Albers for the patch)
* FIX: Add/Modify dialog: scroll to top of page on submission
* FIX: Add object: Stop adding an object when clicking on header menu
* FIX: center/bottom label positions now work with lines
Core:
* Allowing ~ chars in URLs now (Thanks to Daniel Albers for the patch)
* FIX: Fixed rare occuring encoding problems of vars in several places
* FIX: Fixed PHP error with map objects linking to not existing maps
* FIX: Trying to workaround broken processing of non UTF-8 pages in hover_urls
Geomap:
* FIX: Improved error handling in case of invalid webservice data
1.8b2
Frontend:
* FIX: Fixed warning icon of std_area iconset
Core:
* Processing Rotation/view/* permission when using Multisite authorisation
* FIX: Fixed PHP error when using status hosts in backends
* FIX: Encoding _origtarget URL parameter handed over to multisite now
* FIX: The NDO backend is now usable again with maps and automaps
(Just for the next stable release - on the later releases it will be dropped)
* FIX: The NagiosBP backend is now usable again
* FIX: Fixed host alias attribute in livestatus backend
* Dropped the merlinmy backend for the moment as it was not working for a
time. Please provide a fixed one if you like to see this working again
* FIX: Fixed PHP errors when acknowleding host/service problems
* FIX: Fixed missing values alias, display_name, address values in hover templates
Installer:
* FIX: Installer uses /etc/apache2/conf-available instead of the old conf.d
directory for installing it's apache sample configuration. It is
currently not enabled by default. Use "a2enconf nagvis" to enable it.
1.8b1
Core:
* Changed internal structures to improve memory consumtion on large maps
* Added authorisation module based on the users contact group memberships
defined in the monitoring core
* It is now possible to merge states of host, hostgroup and servicegroup
objects with equal names from different backends. For example, this can
be used to create a single hostgroup object on a map which is populated
by different hostgroups from several monitoring instances. This is simply
configured by putting several backend ids to the backend_id parameter
(separated by ",").
* Added new object called "dynamic groups". Can only be used with livestatus
backend. It uses the configuration option object_filter to group a dynamic
list of services or hosts in a NagVis map object without having to define
it in the monitoring core.
* Added new map source "dynmap" which can be used to realize some sort of
dynamic maps. Those maps list several objects matching a given livestatus
filter on the map. In first instance it automatically gathers the list of
objects to add on this map and positions them in a grid on the map. The
user can then modify all the objects, for example change their options
like, positions and visualisation.
* Changed default http_timeout from 10 to 2 seconds
* Added new iconset std_area, which can be used to create maps which are
visible from a greater distance
Automap:
* Added "on-demand-filter" header menu to support quick filter mechanism
for on demand automaps
* Host labels are now limited to 14 chars on automaps
* Again, trying to improve the default automap rendering
Frontend:
* All nodes with assigned childs in sidebar are now expandable. The state
is stored for each user individually.
* Changed map rendering on overview from a single bulk request to one
request per map.
* Added optional zoom bar and mousewheel zoom handlers (ALT + wheel move)
(Must be enabled with option "zoombar=1")
* Added new option multisite_snapin_layout to render the multisite snapin
in a "tree" instead of a "list"
* Summary states of maps can now be displayed in the sidebar menu (must be
enabled by setting header_show_states=1 in [defaults] section in global
configuration)
* The "zoom" parameter can be configured to "fill" to make the view fill the
whole viewport of the browser
* FIX: Fixed centering of overview tables when opening the sidebar
* FIX: Fixed mouse pointer confusions when adding a new object and hovering
another menu which then shows up the hover menu
* FIX: Ajax request: Not setting headers which are usually set by the browser
* FIX: Fixed displaying default value in object / global attribute edit dialog
* FIX: Fixed dependent attribute update in case of "parent" toggle/untoggle
1.7.10
Frontend:
* Weathermap lines now deal with bit/byte values provided by Check_MKs
interface checks
* FIX: Fixed "TypeError: oLabel is null" on at least geomaps
* FIX: Fixed shape image displaying when using external URLS
* FIX: Hiding "Edit Map" link for "on demand" automaps
* FIX: Fixed "modify view" dialog for "on demand" automaps
* FIX: Fixed wrong viewport html header (Thanks to Carl Helmertz NagVis ist ein Visualisierungs-Addon für das bekannte Netzwerk-Management-System Nagios® (bzw. Icinga, das ein Fork von Nagios ist). NagVis kann benutzt werden, um Nagios-Daten zu visualisieren, d.h. IT-Prozesse wie ein Mail-System oder eine Netzwerkinfrastruktur darzustellen.
Durch die Benutzung von Daten, die von einem Backend zur Verfügung gestellt werden, kann NagVis die Objekte auf den Maps in regelmäßigen Intervallen aktualisieren.
Diese Maps ermöglichen es, die Objekte auf verschiedene Arten zu arrangieren:
Über
Was ist NagVis?
NagVis ist ein Präsentationswerkzeug für die Informationen, die von Nagios gesammelt und mit Hilfe eines Backends zur Verfügung gestellt werden.
Die unterstützten Backends sind:
Sie können alle Nagios-Objekte (Hosts, Services, Hostgroups, Servicegroups) zu so genannten Maps hinzufügen. Jede Map kann durch ihre eigene Konfigurationsdatei konfiguiert werden. Sie können diese Konfigurationsdateien mit Ihrem bevorzugten Texteditor oder mit Hilfe des Web-Konfigurations-Tool namens WUI anpassen. Außerdem können Sie einige spezielle NagVis-Objekts zu den Maps hinzufügen. Diese Objekte sind "Shapes", "Textboxen" und Referenzobjekte für andere Maps.
Jedes der Objekte auf Ihren Maps kann nach Ihren Bedürfnissen angepasst werden.
Es gibt z.B. Verweise auf das Nagios-Frontend für jedes Objekt, das ein Nagios-Objekt repräsentiert.
Sie können diese Verweise einfach anpassen.
Es gibt ein Hover-Menü, das per Default aktiviert ist.
Das Hover-Menü zeigt detaillierte Informationen für jedes Objekt.
Hover-Menüs können einfach geändert werden, indem die Templates angepasst werden.
Sie können auch das Hover-Menü deaktivieren.
Per Default werden die Zustände von Objekten als Icons auf der Map angezeigt.
Sie können diese Icons durch Iconsets von der NagVis-Homepage oder durch eigene ersetzen.
Die Zustände von Objekten können auch als Linien oder als Gadgets angezeigt werden.
Neben den normalen Maps gibt es die Automap. Abhängig von der Einstellung der Direktive "filterByState" zeigt sie alle Objekte oder nur diejenigen in einem nicht-OK-Zustand inklusive des Weges vom Root-Objekt bis zum jeweiligen nicht-OK-Objekt.
Sie wird automatisch auf Basis der Nagios-Konfiguration generiert.
Zur Nutzung der Automap müssen Sie die "Parent"-Abhängigkeiten in Nagios nutzen.
Die Automap erzeugt ein Hintergrundbild basierend auf der Konfiguration, den Layout-Parametern und den Parent-Abhängigkeiten.
Ab NagVis 1.5 können Sie auch mehrere Automaps definieren.
NagVis ist freie Software. Sie können es unter den Bedingungen der GNU General Public License Version 2 verteilen und/oder modifizieren, die von der Free Software Foundation veröffentlicht wurden.
NagVis wird in der Hoffnung verteilt, dass es nützlich ist, aber OHNE JEGLICHE GARANTIE, auch ohne die implizite Garantie der VERMARKTBARKEIT oder der TAUGLICHKEIT FüR EINEN BESTIMMTEN ZWECK. Genauere Details finden Sie in der GNU General Public License.
nagvis-nagvis-1.9.47/docs/de_DE/after_installation.html 0000664 0000000 0000000 00000012263 15014016017 0023027 0 ustar 00root root 0000000 0000000Nach der Installation enthält NagVis verschiedene Demo-Maps. Außerdem ist eine Rotation definiert, um Ihnen ein Beispiel für die Möglichkeiten von NagVis zu zeigen. Sicherlich hat NagVis viel mehr Features als wir Ihnen mit Hilfe dieser Demo-Konfigurationen zeigen können. Daher sollten Sie die Dokumentation lesen und kreativ sein.
Wenn Sie mit NagVis vertraut sind, können Sie diese Demo-Maps und die Rotation ohne Probleme löschen.
NagVis basiert auf verschiedenen Konfigurationsdateien.
Die Hauptkonfigurationsdatei enthält grundlegende und globale Konfigurationsoptionen.
Die Map-spezifischen Konfigurationsoptionen werden in etc/maps/
in den Map-Konfigurationsdateien abgelegt.
Ein spezieller Typ von Maps sind die Automaps. Mehr Informationen dazu finden Sie in der Dokumentation zur Automap-Konfiguration.
Die gesamte NagVis-Konfiguration kann mit Hilfe des webbasierten Konfigurationsprogramms geändert werden.
Als Standard benutzt NagVis eine interne Benutzer- und Berechtigungsdatenbank (SQLite) für Authentifizierung und Autorisierung. NagVis besitzt ein rollenbasiertes Berechtigungssystem. Nach der Installation sind zwei Default-Benutzer definiert:
Die folgenden Rollen mit diesen Berechtigungen sind verfügbar:
Diese Default-Benutzer und Rollen sollten für den Anfang ausreichen. Sie können diese Benutzer und Rollen löschen, aber passen Sie auf, dass Sie nicht den letzten administrativen Benutzer löschen.
während der Installation
Bitte stellen Sie sicher, dass Sie eine aktuelle PHP-Version benutzen, dass alle für NagVis und das Backend benötigten Module vorhanden sind und dass GraphViz bereits installiert ist. Einige PHP-Module sind ggf. im Basis-Paket enthalten (bitte benutzen Sie "php -m" zur Prüfung).
Bitte prüfen Sie install.log
auf Fehler.
Nach der Installation
Bitte prüfen Sie die Apache-Logs auf "permission denied"-Meldungen. Es ist ziemlich wahrscheinlich, dass SElinux aktiviert ist. Bitte deaktivieren Sie es (setenforce 0) oder erlauben Sie NagVis den Zugriff auf die Dateien.
Bitte prüfen Sie die Apache-Logs auf "memory limit exceeded"-Meldungen. Es ist ziemlich wahrscheinlich, dass die memory-Einstellungen in der php.ini erhöht werden müssen. Starten Sie Ihren Web-Server nach der Änderung neu.
Bitte werfen Sie außerdem einen Blick auf die doc section der offiziellen Website ("FAQ" und "Often reported errors"). Falls das nicht hilft, dann lesen Sie weiter.
HILFE
Möglicherweise suchen Sie Hilfe auf der offiziellen NagVis-Website oder benutzen das Monitoring-Portal, das auch ein Board für NagVis-Fragen anbietet.
Bitte liefern Sie in jedem Fall WENIGSTENS Informationen über
grep "^[^;|^$]" <config-Datei>
(falls Sie ein Problem mit der Konfiguration haben). Ersetzen Sie "<config-Datei>" durch den Namen der Datei, in der Sie einen Fehler vermutenIn den Versionen vor 1.5 kümmerte sich NagVis nicht viel um Authentifizierung und Autorisierung.
In den meisten Umgebungen nutzte es die Authentifizierung von Nagios.
Das war ein Nebeneffekt, da NagVis im nagios/share
-Verzeichnis platziert war.
Mit NagVis 1.5 wurde das Default-Installationsverzeichnis in ein eigenes Basisverzeichnis verschoben. Dieser Schritt erforderte einen neuen Authentifizierungs- und Autorisierungsmechanismus. Das Hauptaugenmerk dieses Konzeptes liegt auf Modularität und Flexibilität.
Das AA wurde in drei Module aufgeteilt: LogonDialogs, Authentifizierung, Autorisierung. Jedes einzelne Modul kann geändert werden, ohne die anderen zu beeinträchtigen.
Per Default nutzt NagVis einen gemischten Logon-Request-Modus für die Anmeldung und eine SQLite-Datenbank für die Speicherung von Benutzern, Passwörtern und Berechtigungen. Dafür verwendet NagVis das LogonMixed-Modul, das im Hintergrund auf LogonEnv und LogonDialog zugreift. Das LogonMixed-Modul versucht, den Benutzernamen über das Web-Server-Environment zu ermitteln. Das bedeutet, dass NagVis der Web-Server-Authentifizierung vertraut, wenn eine benutzt wird. Falls keine verwendet wird, zeigt es den LogonDialog an, um interaktives Login durch den HTML-Logon-Dialog zu ermöglichen.
Bei der Auslieferung gibt es nur die o.g. Authentifizierungs- und Autorisierungsmodule. Durch die modulare Struktur sollte es einfach sein, LDAP-, MySQL- und dateibasierende Authentifizierungs- und Autorisierungsmechanismen zu erstellen.
nagvis-nagvis-1.9.47/docs/de_DE/auth_old_style.html 0000664 0000000 0000000 00000003763 15014016017 0022171 0 ustar 00root root 0000000 0000000In den Versionen vor 1.5 kümmerte sich NagVis nicht viel um die Authentifizierung und Autorisierung.
In den meisten Umgebungen nutzte es die Authentifizierung von Nagios.
Dies war ein Nebeneffekt, da NagVis im Verzeichnis nagios/share
platziert war.
Mit NagVis 1.5 wurde das Default-Installationsverzeichnis in ein eigenes Basisverzeichnis verschoben. Dieser Schritt erforderte einen neuen Authentifizierungs- und Autorisierungsmechanismus. Das Hauptaugenmerk dieses Konzeptes liegt auf Modularität und Flexibilität.
Wenn Sie wirklich die Authentifizierung von Nagios nutzen möchten, dann können Sie das LogonMixed- (default) oder das LogonEnv-Modul nutzen, um eine zuverlässige Authentifizierung einzusetzen. Der einzige Unterschied besteht darin, dass das LogonMixed-Modul den HTML-LogonDialog nutzt, wenn kein Benutzer vom Web-Server übergeben wird, während LogonEnv einfach nur eine "Zugriff verweigert"-Meldung anzeigt.
Um dies zu erreichen, setzen Sie einfach die folgenden Optionen im [global]
-Abschnitt der NagVis-Hauptkonfigurationsdatei:
logonmodule="LogonEnv" logonenvvar="REMOTE_USER" logonenvcreateuser="1"
Diese Zeilen weisen NagVis an, das LogonEnv-Modul zu nutzen, das den authentifizierten Benutzer aus einer Umgebungsvariablen ausliest. Der zweite Parameter teilt dem LogonEnv-Modul mit, welche Variable für das Auslesen benutzt werden soll. Die dritte Variable bewirkt, dass unbekannte Benutzer in der NagVis-AA-Datenbank angelegt werden sollen.
nagvis-nagvis-1.9.47/docs/de_DE/authorisation_roles_perms.html 0000664 0000000 0000000 00000013355 15014016017 0024453 0 ustar 00root root 0000000 0000000Ab Version 1.5 enthält NagVis eine sehr detaillierte Berechtigungsverwaltung. Es ist ein rollenbasiertes Konzept, bei dem Benutzer einer oder mehreren Rollen zugeordnet werden, denen die Berechtigungen zugeordnet sind.
Die Berechtigungen der verschiedenen Rollen eines Benutzers werden zusammengefasst und kontrollieren die Aktionen, die ein Benutzer ausführen darf.
Diese Standardrollen sollten für den Anfang ausreichen. Sie können diese Benutzer und Rollen löschen, aber denken Sie daran, dass Sie NICHT die letzte administrative Rolle bzw. den Benutzer löschen.
Es ist möglich, neue Rollen anzulegen, um die Berechtigungen von Benutzern und Benutzergruppen anzupassen.
Es ist z.B. einfach, eine Rolle für alle SAP-Administratoren anzulegen, die nur auf die SAP-relevanten Maps zugreifen können.
Die Berechtigungen sind in NagVis hartkodiert. Eine Berechtigung besteht aus drei Teilen:
Jedes dieser drei Dinge kann durch einen dedizierten Namen oder alternativ durch ein Wildcard-Zeichen "*" gesetzt werden, das dann auf alle Module, Aktionen oder Objekts zutrifft.
Hier ist eine Liste aller verfügbaren Berechtigungen:
Modul | Aktion | Objekt | Beschreibung |
---|---|---|---|
* | * | * | Gewährt vollen Zugriff auf NagVis. Es werden keine weiteren Berechtigungen benötigt. |
Auth | logout | * | Erlaubt einem Benutzer, sich aus NagVis abzumelden. |
AutoMap | add | * | Anlegen einer neuen Automap. |
AutoMap | delete | * | Löschen aller Automaps. |
AutoMap | edit | * | Editieren aller Automaps. |
AutoMap | view | * | Ansehen aller Automaps. |
AutoMap | delete | <Name> | Löschen einer bestimmten Automap. |
AutoMap | edit | <Name> | Editieren einer bestimmten Automap. |
AutoMap | view | <Name> | Ansehen einer bestimmten Automap. |
ChangePassword | change | * | Erlaubt einem Benutzer, das eigene Passwort zu ändern. |
General | * | * | |
MainCfg | edit | * | |
Map | add | * | |
Map | delete | * | |
Map | edit | * | |
Map | view | * | |
Map | delete | <Name> | Löschen einer bestimmten Map. |
Map | edit | <Name> | Editieren einer bestimmten Map. |
Map | view | <Name> | Ansehen einer bestimmten Map. |
Overview | view | * | |
RoleMgmt | manage | * | |
Rotation | view | * | |
Rotation | view | <Name> | Ansehen einer bestimmten Rotation. |
Search | view | * | Suche Objekte auf Maps und Automaps. |
UserMgmt | manage | * |
Parameter | Default | Beschreibung |
---|---|---|
show | Der Name der Automap. Seit NagVis 1.5 können verschiedene Automap-Konfigurationsdateien definiert werden. Die anzuzeigende Automap muss hier angegeben werden. | |
backend_id | default backend | Die Backend-Id des Backends, dessen Objekte benutzt werden sollen. Einzelheiten finden Sie im [backend_*]-Abschnitt der Beschreibung der Hauptkonfigurationsdatei. |
root | siehe root object definition | Dies ist der Name des Root-Objektes. Es ist nicht notwendig, den Host hier zu setzen. Es gibt mehrere Wege, das Root-Objekt zu ermitteln. Einzelheiten finden Sie im Root-Objekt-Definition-Kapitel auf dieser Seite |
child_layers | 2 | maximale Anzahl von anzuzeigenden Ebenen abhängiger "Child"-Hosts. |
parent_layers | 0 | maximale Anzahl von anzuzeigenden Ebenen darüber liegender "Parent"-Hosts. |
render_mode | undirected | Setzt den Render-Modus der Map. Einzelheiten finden Sie unter verfügbare Render-Modi |
width | 1024 | Breite der Automap in Pixeln |
height | 786 | Höhe der Automap in Pixeln |
ignore_hosts | none | Kommaseparierte Liste von Hosts (einschließlich abhängiger Hosts), die nicht angezeigt werden sollen |
filter_by_state | none | Bei einem Wert von 1 ist der "Problem Automap"-Modus aktiviert. Dabei werden alle Zweige ausgefiltert, die nur Hosts im Status "UP" enthalten. Das resultiert in einer "Problem-Automap", die einen Baum zeigt, in dem in jedem Zweig mindestens einen Host mit einem Problem gibt |
filter_by_id | Die angegebenen object_ids ausschließen; wird hauptsächlich intern genutzt . | |
filter_group | none | Geben Sie den Namen einer Hostgruppe an. Nur Hosts dieser Hostgruppe werden auf der Map angezeigt. |
search | none | Suche nach einem Map-Objekt während des Map-Ladens. Passende Objekte werden hervorgehoben. |
rankdir | LRnone | Konfiguriert die Richtung von gerichteten Automaps, kann auf TB (Top/Bottom) oder LR (Links/Rechts) gesetzt werden. |
rotation | none | Rotieren der Map-Objekte im angegebenen Rotations-Pool |
header_menu | none | Aktivieren/Deaktivieren des Header-Menüs durch 1 bzw. 0. Übersteuert die Konfiguration. |
hover_menu | none | Aktivieren/Deaktivieren des Hover-Menüs durch 1 bzw. 0. Übersteuert die Konfiguration. |
context_menu | none | Aktivieren/Deaktivieren des Context-Menüs durch 1 bzw. 0. Übersteuert die Konfiguration. |
margin | none | Setzt den freien Bereich am Rand des Automap-Graphen. Die Angabe erfolgt in Pixeln. |
overlap | none | Konfigurieren der Kollisionsbehandlung von Objekten (eine Erklärung der Werte finden Sie in der GraphViz-Dokumentation) |
root
gesetzt werdendefaultroot
-Option kann im [automap]
-Abschnitt gesetzt werdenModus | Beispiel-Bild |
directed | ![]() |
undirected | ![]() |
radial | |
circular | |
undirected2 |
Seit NagVis 1.5 ist es möglich, die aktuelle Automap-Ansicht als normale NagVis-Map zu exportieren. Durch den Export erhalten Sie Vorteile aus beiden Ansichten.
Sie können mit der Automap beginnen, um mit Hilfe der Automap-Render-Modi die Objekte auf Ihrer Automap zu positionieren. Sobald Sie fertig sind, exportieren Sie die Automap zusammen mit dem generierten Hintergrundbild in eine reguläre Map. Dazu benutzen Sie den Punkt "Export to map", den Sie im "Aktionen"-Menü Ihres Header-Menüs finden.
Auf der exportierten Map können Sie - abhängig von Ihren Anforderungen - zusätzliche Design-Elemente platzieren oder das Layout anpassen.
Eine Automap kann beliebig oft in die gleiche Ziel-Map exportiert werden (wodurch natürlich Ihre Anpassungen in der Ziel-Map überschrieben werden!). Sie können nur Maps überschreiben, wenn Sie die Berechtigung dazu haben.
Eine normale Map kann nicht in eine Automap konvertiert werden.
Die URLs von Host-Objekten werden zur Identifizierung der Objekte während des Renderns benutzt. Speziell der "host="-Parameter ist wichtig. Wenn dieser Parameter in der Host-URL fehlt, dann können die Objektpositionen nicht ermittelt werden.
Normalerweise sollte diese Information nicht von Interesse für Sie sein. Wenn Sie aber die Host-URLs in Ihrer NagVis-Installation anpassen, dann ist es wichtig zu wissen, dass Ihre benutzerdefinierte URL den Parameter "host=" enthalten muss, der mit dem Hostnamen des Objekts zu füllen ist, damit die Hosts in der Automap benutzt werden können.
nagvis-nagvis-1.9.47/docs/de_DE/automap_config_format.html 0000664 0000000 0000000 00000031031 15014016017 0023502 0 ustar 00root root 0000000 0000000Das NagVis-Automap-Konfigurationsformat gleicht dem Map-Konfigurationsformat mit kleinen Unterschieden bei den verfügbaren Parametern.
Die erste Definition in jeder Konfigurationsdatei sollte vom speziellen Typ "global" sein. Optionen in diesem Paragraph gelten für die gesamte Map und werden auf andere Typen vererbt, die nachfolgend definiert werden.
Beispiel mit allen Optionen, die gesetzt werden müssen:
define global { map_image=lan.png }
Wert | Default | Beschreibung |
---|---|---|
alias | Map-Name | Der Alias ist das Label für jede Map. Wenn definiert, wird es überall im NagVis-Frontend und WUI angezeigt |
backend_id | vererbt (nagvis.ini.php) | Die in der Hauptkonfigurationsdatei definierte Backend-ID, die angibt, wo NagVis nach Objektzuständen suchen soll. Wenn dieser Parameter nicht angegeben wird, wird das in der Hauptkonfigurationsdatei unter "defaultbackend" angegebene Backend benutzt. |
background_color | vererbt (nagvis.ini.php) | Hintergrundfarbe dieser Map. Falls dieser Wert nicht gesetzt wird, wird die Hintergrundfarbe aus der Hauptkonfigurationsdatei genommen. |
context_menu | vererbt (nagvis.ini.php) | Aktivieren/deaktivieren des Kontext-Menüs auf Ihren Map-Objekten. |
context_template | vererbt (nagvis.ini.php) | Default Context-Template, das auf dieser Map benutzt werden soll |
default_params | vererbt (nagvis.ini.php) | zu benutzende Default-Parameter, wenn keine per URL übergeben wurden. Das Format ist wie bei dem URL, z.B. &childLayers=2 . Gültige Optionen finden Sie hier. |
event_background | vererbt (nagvis.ini.php) | Aktivieren/deaktivieren der sich ändernden Hintergrundfarbe bei Statusänderungen (die konfigurierte Farbe wird angezeigt, wenn der Gesamtstatus PENDING, OK oder UP ist). |
event_highlight | vererbt (nagvis.ini.php) | Aktivieren/deaktivieren der Hervorhebung des sich ändernden Objekts durch eine blinkende Umrandung. |
event_highlight_duration | vererbt (nagvis.ini.php) | Setzt die Dauer der Hervorhebung in Millisekunden. |
event_highlight_interval | vererbt (nagvis.ini.php) | Setzt die Dauer des Hervorhebungs-Intervalls in Millisekunden. |
event_log | vererbt (nagvis.ini.php) | Aktivieren/deaktivieren des Eventlogs im neuen JavaScript-Backend. Das Eventlog protokolliert wichtige Aktionen und Informationen. |
event_log_level | vererbt (nagvis.ini.php) | Loglevel des Eventlogs (verfügbar: debug, info, warning, critical). |
event_log_height | vererbt (nagvis.ini.php) | Höhe des JavaScript-Eventlogs in Pixeln. |
event_log_hidden | vererbt (nagvis.ini.php) | Verstecken/zeigen des JavaScript-Eventlogs während des Map-Ladens. |
event_scroll | vererbt (nagvis.ini.php) | Aktivieren/deaktivieren des Fokussierens auf das Icon, das den Zustand verändert hat, wenn dieses außerhalb des sichtbaren Bereichs ist. |
event_sound | vererbt (nagvis.ini.php) | Aktivieren/deaktivieren von Sound-Signalen bei Statusänderungen. |
header_menu | vererbt (nagvis.ini.php) | aktivieren/deaktivieren des Header-Menüs |
header_template | vererbt (nagvis.ini.php) | header template für diese Map |
hover_menu | vererbt (nagvis.ini.php) | aktivieren/deaktivieren von Hover-Menüs |
hover_delay | vererbt (nagvis.ini.php) | Verzögerung der Anzeige des Hover-Menus in Sekunden |
hover_template | vererbt (nagvis.ini.php) | Default hover template für diese Map |
hover_childs_limit | vererbt (nagvis.ini.php) | max. Anzahl von Child-Objekten |
hover_childs_order | vererbt (nagvis.ini.php) | Reihenfolge von Child-Objekten ("asc"=aufsteigend, "desc"=absteigend) |
hover_childs_show | vererbt (nagvis.ini.php) | Anzeigen von Child-Objekten in Hover-Menüs |
hover_childs_sort | vererbt (nagvis.ini.php) | Sortierreihenfolge von Child-Objekten ("s"=Status, "a"=Alphabet) |
iconset | vererbt (nagvis.ini.php) | Iconset, das als Standard für alle auf der Map platzierten Objekte benutzt werden soll. Kann für jedes Objekt überschrieben werden. Im Beispiel wird "std_small" benutzt, was bedeutet, dass ein OK-Zustand das Icon "std_small_ok.png", benutzt, ein CRITICAL-Zustand "std_small_critical.png" usw. |
in_maintenance | 0 | aktiviert/deaktiviert den Wartungsmodus. Wenn eine Map im Wartungsmodus ist, wird statt der Map lediglich ein Hinweis angezeigt |
label_show | 0 | Labelanzeige für die Map-Objekte aktivieren/deaktivieren |
label_x | -20 | x-Position der Label in Pixeln (mit Vorzeichen +/- relativ zur linken, oberen Ecke der Icons, sonst absolute Position) |
label_y | +20 | y-Position der Label in Pixeln (mit Vorzeichen +/- relativ zur linken, oberen Ecke der Icons, sonst absolute Position) |
label_width | auto | Default-Breite der Label in Pixeln |
label_background | transparent | Default-Hintergrundfarbe der Label. Die Farbe sollte als Hexcode angegeben werden, kann aber auch "transparent" sein. |
label_border | #000000 | Default-Rahmenfarbe der Label. Die Farbe sollte als Hexcode angegeben werden, kann aber auch "transparent" sein. |
label_style | Benutzerdefiniertes Aussehen des Label-Textes im Format von HTML-Style-Attributen, z.B. font-family:sans;font-weight:bold; . |
|
line_type | Gibt den Linientyp an, wenn view_type=line. Gültige Werte sind: "11" für Linien mit einem Pfeil am Linienende. "10" für Linien mit zwei Pfeilen, die in der Linienmitte aufeinander zeigen. "12" für Linien ohne Pfeil(e). |
|
line_width | 3 | Dies definiert die Linienbreite in px, wenn dieses Objekt als Linie angezeigt wird. |
only_hard_states | vererbt (nagvis.ini.php) | Gibt an, ob Soft-Zustände ignoriert werden sollen. Default ist 0. |
recognize_services | vererbt (nagvis.ini.php) | Definiert, ob die Services des Hosts den angezeigten Status beeinflussen. Wenn auf "1" gesetzt, wird ein Service im Status CRITICAL auch den HOST als CRITICAL anzeigen. Wenn auf "0" gesetzt, wird nur der Host-Zustand (UP oder DOWN) angezeigt und der Status der Services ignoriert. Ist dieser Wert nicht in der Konfiguration angegeben, wird er auf 1 gesetzt. |
show_in_lists | vererbt (nagvis.ini.php) | Map-Anzeige in Listenformat (Dropdowns, Indexseite, ...) |
stylesheet | vererbt (nagvis.ini.php) | Dateiname des benutzerdefinierten Stylesheets zur Verwendung in den Maps. Die Datei muss im share/nagvis/style-Verzeichnis abgelegt sein. |
url_target | _self | Ziel des Icon-Links, diese Option passt <a target=""> an (_self ist das gleiche Fenster) |
Das NagiosBP-Backend wird benutzt, NagVis direkt mit den Nagios Business Process-Addons zu verbinden, die verwendet werden, um aus den Nagios-Statusinformationen Geschäftsprozessaggregationen zu erstellen.
NagiosBP bietet einen Web-Service, der durch HTTP-Get-Anfragen aufgerufen wird und mit JSON-Objekten antwortet. Die Dokumentation dieser JSON-API finden Sie hier.
Dieses Backend ist besonders verglichen mit den anderen Backends, die Nagios-Statusinformationen 1:1 behandeln. Dieses Backend verarbeitet hauptsächlich Geschäftsprozesse, aber auch Nagios-Zustandsinformationen. Als Ergebnis dieser Tatsache muss das Backend eine Art von Übersetzung durchführen, um aus den Geschäftsprozessen Nagios-ähnliche Objekte zu erzeugen.
Während der Entwicklung dieses Backends stellte sich heraus, dass die Geschäftsprozesse auf Servicegruppen-Objekte abgebildet werden sollten. Daraus ergeben sich zwei Dinge:
Eine andere besondere Eigenschaft des NagiosBP-Backends besteht darin, dass NagVis nicht die Gesamt- (aggregierten) Zustände mit eigenen Algorithmen berechnen muss. Statt dessen setzt das NagiosBP-Backend die Zustände/Ausgaben der NagiosBP-Servicegruppen mit Hilfe der von NagiosBP gelieferten Zustandsinformationen.
Die Servicegroup-Verweise (Links-Klick auf Icon) werden automatisch durch das NagiosBP-Backend gesetzt,
um auf die NagiosBP-GUI zu zeigen, außer wenn der url
-Parameter der Servicegruppe
konfiguriert ist, um auf eine andere Map zu zeigen
(z.B. [htmlbase]/index.php?mod=Map&act=view&show=bp-webshop-details
).
Sie können die folgenden Parameter benutzen, um das NagiosBP-Addon zu konfigurieren:
Wert | Default | Beschreibung |
---|---|---|
base_url | http://localhost/nagios/cgi-bin/nagios-bp.cgi | Die vollständige URL zum nagios-bp.cgi -Script, das Teil von NagiosBP ist.
Es bedient die AJAX-API, mit der sich das Backend verbindet. Diese URL muss von dem Host
erreichbar sein, auf dem NagVis läuft. |
auth_user | Optionaler Benutzer, der als Basic-Authentifizierungs-Benutzer benutzt werden soll, um auf die base_url zuzugreifen. |
|
auth_pass | Optionales Passwort, das als Basic-Authentifizierungs-Passwort benutzt werden soll, um auf die base_url zuzugreifen. |
Es gibt auch einige allgemeine Parameter. Sie finden sie in der Formatbeschreibung der Hauptkonfigurationsdatei.
nagvis-nagvis-1.9.47/docs/de_DE/backends.html 0000664 0000000 0000000 00000003513 15014016017 0020715 0 ustar 00root root 0000000 0000000Der NagVis-Code besteht aus mehreren Schichten. Eine dieser Schichten ist die "Daten-Schicht". Die Datenschicht wird benutzt, um Informationsanfragen von Dritten zu behandeln, wie z.B. Nagios NDO. Wir nennen diese Schicht im Allgemeinen "Backend". Innerhalb von NagVis gibt es einige Komponenten, um diese Backends zu verwalten und sie dienen als "Kleber" zwischen den einzelnen Backends und den anderen Schichten.
Zur Zeit werden mit dem NagVis-Kern drei Backends ausgeliefert: das mklivestatus, ndomy und merlinmy Backend.
Alle Backends werden im Folgenden genauer beschrieben.
Das ndomy-Backend ist das Default-Backend von NagVis 1.0 bis NagVis 1.4.x.
Es holt Nagios-Informationen aus der NDO-MySQL-Datenbank.
Seit NagVis 1.5 ist MKLivestatus das Default-Backend.
Die Backends werden in der Hauptkonfigurationsdatei definiert. Schauen Sie in die Formatbeschreibung der Hauptkonfigurationsdatei, wie Backends definiert werden.
nagvis-nagvis-1.9.47/docs/de_DE/changelog.html 0000664 0000000 0000000 00000001127 15014016017 0021071 0 ustar 00root root 0000000 0000000Die aktuellen Änderungen finden Sie im NagVis Change Tracker. Das Tracking-System "trac" wird von sourceforge.net zur Verfügung gestellt.
Alle Änderungseinträge finden Sie hier.
nagvis-nagvis-1.9.47/docs/de_DE/changelog2.html 0000664 0000000 0000000 00000003534 15014016017 0021157 0 ustar 00root root 0000000 0000000
Changelog
Kontext-Templates sind HTML-Dateien, die u.a. Makros enthalten. Dieses Dateien können als Kontextmenüs ("Rechtsklick"-Menüs) für die Objekte auf der Map benutzt werden.
Die Kontextmenüs befinden sich in share/userfiles/templates/
relativ zum NagVis-Root-Verzeichnis.
Die Templates sind wie folgt benannt: <name>.context.html
.
Es ist möglich, eine CSS-Datei zum Template hinzuzufügen, der Name lautet dann: <name>.context.css
.
Es gibt einige sogenannte Makros in Kontextmenüs, die für alle Objekte verfügbar sind, und einige, die nur für spezielle Makros gelten. Alle Standardmakros sind nachfolgend aufgeführt.
Die folgenden Makros sind in Hover-Menüs für alle Objekttypen verfügbar:
Makro | Beschreibung |
---|---|
Allgemein | |
[obj_id] | ID des Objekts in JavaScript. Wird benötigt, um die objektspezifischen Teile zu lokalisieren, z.B. für eine manuelle Aktualisierung einer Statusinformation. |
[type] | Typ des Objekts |
[name] | Name des Objekts (Hostname, Hostgroupname, Servicegroupname, Mapname,...) |
[backend_id] | Die backend_id des verwendeten Backends dieses Objekts. |
[custom_1] | Das erste benutzerdefinierte Makro je Backend. Kann nützlich sein, um Backend-spezifische URLs zu setzen. |
[custom_2] | Zweites benutzerdefiniertes Makro je Backend (s.o.). |
[custom_3] | Drittes benutzerdefiniertes Makro je Backend (s.o.). |
[map_name] | Name der aktuellen Map/Automap. |
Sprachmakros | |
[lang_refresh_status] | Bezeichnung für die Auffrischung des Zustands des Objekts im Frontend. |
[lang_schedule_downtime] | Bezeichnung für die Planung einer Ausfallzeit in Nagios. |
[lang_reschedule_next_check] | Bezeichnung für die erneute Planung der nächsten Prüfung des Objekts in Nagios. |
[lang_connect_by_ssh] | Label für die Verbindung eines Hosts per ssh. |
Pfade | |
[html_base] | Absolute URL zur HTML-Basis (Default: /nagios/nagvis) |
[html_cgi] | Absolute URL zu den Nagios-CGIs. Benutzt einen objektabhängigen Wert. Hängt vom verwendeten Backend ab. Wird kein backend-spezifischer Wert gesetzt, gilt der Default. (Default: /nagios/cgi-bin) |
[html_templates] | Pfad zum Context-Templates-Verzeichnis (Default: /nagios/nagvis/nagvis/etc/templates/context) |
[html_template_images] | Pfad zum Context-Template-Images-Verzeichnis (Default: /nagios/nagvis/nagvis/images/templates/context) |
Es gibt Makros für Context-Templates eines bestimmten Typs. Diese Makros sollten zwischen "Section"-Makros stehen. Die "Section"-Makros definieren, dass der eingeschlossene Code entfernt wird, wenn das Hover-Template nicht für diesen Typ geparst wird.
Ein "Section"-Makro für Host-Makros sieht wie folgt aus:
<!-- BEGIN host -->.+?<!-- END host -->
Nachfolgend finden Sie eine vollständige Liste der speziellen Makros.
Makro | Beschreibung |
---|---|
[address] | Adresse des in Nagios konfigurierten Hosts |
[pnp_hostname] | Hostname für Links zu PNP (Leerzeichen ersetzt) |
Makro | Beschreibung |
---|---|
[service_description] | Service-Beschreibung in Nagios |
[pnp_service_description] | Service-Beschreibung für Links zu PNP (Leerzeichen ersetzt) |
<!-- BEGIN hostgroup -->
und <!-- BEGIN servicegroup -->
existieren, um speziellen Template-Code für Hostgroup- und Servicegroup-Kontextmenüs zu ermöglichen.
Beide bringen keine speziellen objektspezifischen Makros mit sich.
Es gibt einige andere spezielle Abschnittsmakros. Um bspw. Teile des Templates nur für Line-Objekts zu zeigen:
<!-- BEGIN line -->This is only shown on line objects<!-- BEGIN servicegroup -->
Abschnitt | Beschreibung |
---|---|
line | Dies nur für Line-Objekte zeigen. |
stateful | Dies nur für "stateful"-Objekte zeigen. |
not_automap | Dies nur für nicht-Automap-Ansichten zeigen (reguläre Maps). |
locked | Dies nur für gesperrte Objekte zeigen. |
unlocked | Dies nur für nicht gesperrte Objekte zeigen. |
permitted_edit | Nur zeigen, wenn der Benutzer die Map editieren darf. |
NagVis 1.4 bringt ein neues mächtiges Feature namens Kontext-Menüs. Dies sind grundsätzlich
Rechtsklick-Menüs bei Status-Icons. Sie können diese Menüs durch Editieren von Template-Dateien
anpassen. Diese Template-Dateien sind einfache HTML-Dateien mit einigen Makros, die während des Renderns
im NagVis ersetzt werden.
Die Kontext-Menüs geben Ihnen die Möglichkeit, Ihre administrative Arbeitsweise mit den Überwachungsinformationen dramatisch zu verbessern. Stellen Sie sich vor, Sie haben eine NagVis-Map als das primäre Benutzer-Interface, um Statusinformationen über Ihre Systeme zu sammeln oder sogar als Basis zur Kontrolle Ihrer Systeme. Stellen Sie sich vor, Sie können Statusinformationen über NagVis ansehen und sich mit zwei einfachen Klicks per ssh oder über eine Terminal-Session mit dem problematischen System verbinden. Es ist auch möglich, einige Standard-Wiederherstellungsjobs in Scripts zu speichern oder ähnliches.
Werfen Sie einen Blick in diese Anleitung, um einen Eindruck über die Mächtigkeit dieses neuen Features zu bekommen.
Dies ist ein kurzes How-To, um eine "connect by ssh"-Option zu den NagVis-Host-Kontext-Menüs hinzuzufügen. Die meisten der Änderungen müssen beim Client-Browser durchgeführt werden, damit mit dieser SSH-Verbindungen umgehen kann. In dieser Anleitung benutze ich den Firefox-Browser auf Ubuntu. Es ist kein Problem, diese Dinge auch auf anderen Systemen wie z.B. Windows zum Laufen zu bringen.
cd /usr/local/nagvis cp share/userfiles/templates/default.context.html share/userfiles/templates/default-ssh.context.htmlNun fügen Sie eine Zeile zum Host-spezifischen Makroabschnitt hinzu
<li><a href="ssh://[address]">[lang_connect_by_ssh]</a></li>Das Template ist fertig.
context_menu=true context_template=default-sshSie können diese Option im global-Abschnitt einer Map setzen, in einem Host-Objekt oder sogar ein Template, das in einem Host-Objekt benutzt wird.
about:config
im Firefox. Fügen Sie einige neue Optionen hinzu:
Name: network.protocol-handler.app.ssh Type: String Value: /usr/local/bin/ssh-connect-handler
Name: network.protocol-handler.expose.ssh Type: Boolean Value: true
Name: network.protocol-handler.external.ssh Type: Boolean Value: true
Name: network.protocol-handler.warn-external.ssh Type: Boolean Value: false
/usr/local/bin/ssh-connect-handler
.
#!/bin/bash xterm -e ssh ${1#ssh:\/\/*}Sie müssen das Script ausführbar machen.
chmod +x /usr/local/bin/ssh-connect-handler
ssh://<test-host>
in Ihre Browser-Zeile ein und drücken Enter.
Wenn sich ein xterm mit der ssh-Session öffnet, ist alles OK hier.
Mit diesem Wissen sind Sie bereit, NagVis als Kern Ihrer täglichen Administratiions- und Überwachungs-Aufgaben zu konfigurieren. Seien Sie kreativ!
Wir freuen uns auf Ihr Feedback zu diesem Feature und wie Sie es nutzen.
nagvis-nagvis-1.9.47/docs/de_DE/extending/iconsets.html 0000664 0000000 0000000 00000020444 15014016017 0022761 0 ustar 00root root 0000000 0000000Ein vollständiges Iconset besteht aus mehreren Dateien. Diese Dateien sind PNG-Bilder, die folgendermaßen heißen müssen:
Dateiname | Beschreibung |
---|---|
<set>_critical.png | kritischer Zustand (critical) |
<set>_critical_ack.png | Acknowledged critical state |
<set>_critical_dt.png | Critical state in downtime |
<set>_critical_stale.png | Stale critical state |
<set>_down.png | Down-Zustand (Host) |
<set>_down_ack.png | Acknowledged down state |
<set>_down_dt.png | Down state in downtime |
<set>_down_stale.png | Stale down state |
<set>_error.png | Fehler beim Holen des Zustands |
<set>_ok.png | OK-Status |
<set>_ok_dt.png | OK state in downtime |
<set>_ok_stale.png | Stale ok state |
<set>_pending.png | Pending-Zustand |
<set>_unchecked.png | ungeprüfter Zustand (Pending) |
<set>_unknown.png | unbekannter Zustand (unknown) |
<set>_unknown_ack.png | Acknowledged unknown state |
<set>_unknown_dt.png | Unknown state in downtime |
<set>_unknown_stale.png | Stale unknown state |
<set>_unreachable.png | unerreichbarer Zustand (Host) |
<set>_unreachable_ack.png | Acknowledged unreachable state |
<set>_unreachable_dt.png | Unreachable state in downtime |
<set>_unreachable_stale.png | Stale unreachable state |
<set>_up.png | Up-Zustand (Host) |
<set>_up_dt.png | Up state in downtime |
<set>_up_stale.png | Stale up state |
<set>_warning.png | Warning-Zustand |
<set>_warning_ack.png | Acknowledged warning state |
<set>_warning_dt.png | Warning state in downtime |
<set>_warning_stale.png | Stale warning state |
<set>_ok.png
-Bildern, um die Iconsets aufzulisten. Das heißt, dass ein <set>_ok.png
-Bild vorhanden sein muss,
damit man ein komplettes Iconset über die WUI auswählen kann.
Iconset | Icon-Größe | Icon-Map |
---|---|---|
std_small | 16x16 pixel | ![]() |
mini | 9x9 pixel | ![]() |
share/userfiles/images/iconsets
).
Mit NagVis 1.4 ist das Sprachformat von XML-Dateien ins gettext-Sprachformat geändert worden. Die alten XML-Dateien bedeuteten eine Menge Overhead und verbrauchten viel CPU-Zeit beim Parsen.
Der Hauptvorteil besteht in viel besserer Performance. Mehr Informationen zu gettext finden Sie auf der offiziellen gettext-Seite.
Die Sprachdateien werden in nagvis/includes/locale
abgelegt.
Die deutsche Sprachdatei ist de_DE/LC_MESSAGES/nagvis.mo
.
Im Moment gibt es Sprachdateien für die folgenden Sprachen:
Ihre Sprache wird von NagVis nicht unterstützt? Kein Problem! Sie können einfach Ihre eigene Sprachdatei erstellen. Kopieren Sie eine bestehende Datei, benennen Sie sie um und passen Sie alle Werte an, die Sie ändern möchten.
Wenn Sie eine neue Sprachdatei erstellt oder etwas in einer bestehenden korrigiert haben, dann schicken Sie diese bitte an uns, so dass wir sie in die nächste NagVis-Version einbauen oder auf Nagvis.org veröffentlichen können.
Es gibt Unterstützung für die Ersetzung von vorgegebenen Zeichenketten durch einige Werte.
Ein Beispiel für ein Makro ist die Zeichenkette ([USER]
), die vor der Anzeige in NagVis ersetzt wird, wenn der Spracheintrag dies unterstützt.
Default-Makros sind so etwas wie HTML-Tags, die nicht durch den Benutzer definiert werden müssen. Zur Zeit werden die folgenden Default-Makros unterstützt:
Makro | ersetzt durch |
---|---|
[i] | <i> |
[/i] | </i> |
[b] | <b> |
[/b] | </b> |
Spezielle Zeichen wie ä,ö,ü,",',... müssen als HTML-Entities geschrieben werden (z.B. )
nagvis-nagvis-1.9.47/docs/de_DE/extending/shapes.html 0000664 0000000 0000000 00000002702 15014016017 0022412 0 ustar 00root root 0000000 0000000nagvis/images/shapes
abgelegt. Kopieren Sie sie einfach in dieses Verzeichnis und dann können sie in Ihren Maps benutzt werden.
Hinweis: Die Verzeichnisstruktur hat sich zwischen den NagVis-Versionen mehrfach geändert, so dass es Kompatibilitätsprobleme geben kann.
tar xvzf NagVis-Template-<name>-<version>.tar.gz
cp -r nagvis /usr/local/nagvis/share/userfiles/templates
Nun sollten Sie das neue Template nutzen können. Sie müssen nur die Maps oder Objekte so konfigurieren, dass sie das Template nutzen.
Sie können das Header-Template in der Hauptkonfiguration von NagVis oder im global-Abschnitt der Map-Konfiguration setzen. Details finden Sie in der Map-Konfigurationsformatbeschreibung.
Sie können das Hover-Template in der Hauptkonfiguration für all Ihre Maps setzen, im global-Abschnitt einer Map für alle Objekte auf dieser Map oder in jedem Objekt, um ein angepasstes Menü für spezielle Objekte zu erhalten. Details finden Sie in der Map-Konfigurationsformatbeschreibung.
nagvis-nagvis-1.9.47/docs/de_DE/gadgets.html 0000664 0000000 0000000 00000025423 15014016017 0020565 0 ustar 00root root 0000000 0000000"Gadgets" sind kleine Programme, die Bilder aus Informationen erzeugen, die von NagVis geliefert werden.
Die Hauptidee besteht darin, die Performance-Daten von Nagios an diese Programme zu liefern, um daraus nette Grafiken oder schicke Tachos, Thermometer oder ähnliches zu machen.
share/userfiles/gadgets
enthält einige Beispiele, andere finden Sie unter Nagvis Exchange[1].
Die Gadgets können in jeder Sprache geschrieben werden, die von Ihrem Webserver interpretiert wird, wie z.B. PHP, Perl, ...
Gadgets werden nur für Services unterstützt. Ein Objekt kann in ein Gadget verwandelt werden, indem Sie view_type="gadget" und eine gültige gadget_url setzen.
NagVis unterstützt Gadgets ab Version 1.4[1].
Seit NagVis 1.6 &oum;nnen die Gadgets nicht nur Bilder rendern. Als neue Option können die Gadgets HTML-Code rendern,
der auch JavaScript oder jede Art von dynamischem HTML-Code enthalten kann.
Um die Benutzung von HTML zu aktivieren muss die Option gadget_type
auf den Wert "html" gesetzt werden.
NagVis 1.4 std_speedometer-Gadget auf einer Test-Map mit aktiviertem Label.
Die Gadgets bekommen ihre Informationen durch einen HTTP-Get-Aufruf von NagVis (wenn Sie share/userfiles/gadgets/gadget_core.php
einbinden, werden zwei Arrays gefüllt.
Mehr Informationen finden Sie in der (englischen) Beschreibung dort).
Die folgenden Parameter werden an die Gadgets geliefert:
Parameter | Beispielwert | Beschreibung | Variable |
---|---|---|---|
name1 | localhost | Der Name des Hosts | $aOpts['name1'] |
name2 | Current Load | Die Service-Beschreibung des Objekts | $aOpts['name2'] |
scale | 100 | Die Größe des Gadgets (in Prozent) | $aOpts['scale'] |
state | OK | Die Zeichenkette, die den aktuellen Status beschreibt (OK, WARNING, CRITICAL, UNKNOWN) | $aOpts['state'] |
stateType | HARD | Der Typ des aktuelles Status. Kann HARD oder SOFT sein | $aOpts['stateType'] |
ack | 0 | Wird auf 1 gesetzt, wenn der Status des entsprechenden Objekts bestätigt wurde | $aOpts['ack'] |
downtime | 0 | Wird auf 1 gesetzt, wenn sich das entsprechende Objekt in einer Ausfallzeit (Downtime) befindet | $aOpts['downtime'] |
perfdata | load1=0.960;5.000;10.000;0; load5=0.570;4.000;6.000;0; load15=0.540;3.000;4.000;0; | Die aktuellen Performance-Daten, die von Nagios geliefert werden. Es ist wichtig, gültige Performance-Daten zu haben! | $aPerfdata[<index>][<tag>] |
Ein gültiger HTTP-get zum std_speedometer.php sieht wie folgt aus:
std_speedometer.php?name1=localhost&name2=Current%20Load&state=OK&stateType=HARD&perfdata=load1=0.450;5.000;10.000;0;%20load5=0.260;4.000;6.000;0;%20load15=0.750;3.000;4.000;0;
Bitte prüfen Sie die Parameter view_type
, gadget_url
und gadget_opts
des Service-Objekts in der Formatbeschreibung der Map-Konfiguration.
Hier eine Beispiel-Definition in Ihrer Map-Datei:
define service { host_name=localhost service_description=root-volume x=50 y=50 view_type=gadget gadget_url=std_bar.php // name of the file in share/userfiles/gadgets/ // gadget_url=[http://localhost/nagvis/userfiles/gadgets/std_bar.php] // valid as well // gadget_scale=200 // default is 100 (percent) // gadget_opts=columns=3 label=1 // gadget dependent }
Mit Hilfe des Codes in gadgets_core.php werden zwei Arrays gefüllt. $aPerfdata enthält die Performance-Daten. $aOpts enthält die Optionen, die in gadget_opts gesetzt werden.
Das Einfachste ist, einen Blick auf std_speedometer zu werfen und die Kernbestandteile von dort anzupassen.
Sie sollten einen Beispiel-Performance-Daten-String in den Gadget-Code einfügen, indem Sie die Variable $sDummyPerfdata nutzen. Dies erlaubt es, das Gadget mit Dummy-Daten in der WUI anzuzeigen. Es ist viel einfacher, die Maps zu erstellen, wenn die Gadgets dort angezeigt werden. Wichtig: die Variable muss gesetzt werden, bevor gadgets_core.php über den include-Befehl geladen wird.
Ein zweites Beispiel finden Sie in std_speedometer2.php. Im Gegensatz zu std_speedometer unterstützt es auch check_multi-Ausgaben. Verschiedene Optionen beeinflussen das Verhalten des Gadgets:
Parameter | Beispielwert | Beschreibung |
---|---|---|
label | 1 | 1 = Anzeige von Host-Name / Service-Beschreibung in der linken oberen Ecke des Graphen; 0 = Informationen nicht anzeigen (Default) |
current | 1 | 1 = Anzeige des aktuellen Performance-Daten-Wertes (Default); 0 = Informationen nicht anzeigen |
columns | 5 | Graphen können in Spalten angezeigt werden. Die Zahl der Zeilen wird anhand der maximalen Anzahl von Performance-Daten-Elementen ermittelt. Default ist 3 |
string | pct | Das Performance-Daten-Label muss die Zeichenkette enthalten, damit der Graph angezeigt wird. Im Falle von check_multi-Ausgaben wird nur der letzte Teil untersucht. Default ist eine leere Zeichenkette |
NagVis 1.5 std_speedometer2-Gadget im normalen, warnenden und kritischen Zustand
Ein drittes Beispiel basiert auf einer Idee auf Nagvis Exchange. Performance-Daten werden als horizontaler Balken dargestellt. Das letzte Viertel des Graphs wechselt auf gelb oder rot, wenn die Performance-Daten WARNING oder CRITICAL andeuten. Der Status ist nicht der Zustand des Service! Das liegt daran, dass die Daten ggf. mehrere Datenreihen enthalten. In vielen Fällen sind nicht alle Datenreihen eines Service WARNING oder CRITICAL, so dass Sie sonst falsche Alarme bekommen würden (neu in 1.5.7 oder git neuer als 2010.12.12).
Parameter | Beispielwert | Beschreibung |
---|---|---|
label | 1 | 1 = Anzeige von Host-Name / Service-Beschreibung im letzten Viertel des Graphen (Default); 0 = Informationen nicht anzeigen |
current | 1 | 1 = Anzeigen der aktuellen Performance-Daten (Default); 0 = Informationen nicht anzeigen |
columns | 5 | Graphen können in Spalten angezeigt werden. Die Zahl der Zeilen wird anhand der maximalen Anzahl von Performance-Daten-Elementen ermittelt. Default ist 3 |
string | pct | Das Performance-Daten-Label muss die Zeichenkette enthalten, damit der Graph angezeigt wird. Im Falle von check_multi-Ausgaben wird nur der letzte Teil untersucht. Default ist eine leere Zeichenkette |
threshold | value | Legt fest, ob die WARNING- und CRITICAL-Schwellwerte in Prozent (Default) oder als Zahlenwert angezeigt werden |
NagVis 1.5 std_bar-Gadget im normalen, warnenden und kritischen Zustand
Anmerkung: Dieses Gadget benutzt einen TrueType-Font, dessen Position und Name hartkodiert ist (Variablen $fontDir und $fontName). Wird die Datei nicht gefunden, dann wird ein eingebauter Font benutzt. Der Wert von $fontDir wechselt zwischen den Distributionen. Falls der Font nicht korrekt skaliert, dann prüfen Sie bitte die Einstellung (sie ist korrekt für OpenSuSE, andere Einstellungen sind auskommentiert).
[1] Die Verzeichnisstruktur hat sich zwischen NagVis 1.4.x und NagVis 1.5 geändert. Gadgets wurden innagvis/nagvis/gadgets
abgelegt und werden nun in share/userfiles/gadgets
gespeichert.
Gadgets von NagVis Exchange benutzen möglicherweise die alte Struktur, so dass Sie die Dateien ggf. an die neue Stelle kopieren müssen (z.B. cp -pr <Quelle>/nagvis/nagvis/gadgets/<Gadget> <Ziel>/share/userfiles/gadgets/
).
nagvis-nagvis-1.9.47/docs/de_DE/geomap.html 0000664 0000000 0000000 00000016061 15014016017 0020415 0 ustar 00root root 0000000 0000000
Die NagVis-Geomap-Map-Source wurde in NagVis 1.7 eingeführt. Sie wurde entwickelt, um ohne viel Arbeit sauber gerenderte und skalierte Übersichts-Maps zu erhalten.
Die Geomap rendert verschiedene Hosts auf einer von Open Street Map als Hintergrundbild zur Verfügung gestellten Karte.
Für die aktuelle Geomap benötigen Sie lediglich eine CSV-Datei, die NagVis die Hosts und die Geo-Koordinaten für die zu platzierenden Objekte angibt.
Es ist keine spezielle Software auf dem NagVis-Host erforderlich. Allerdings gibt es eine besondere Anforderung.
Um dieses Feature nutzen zu können benötigt NagVis Zugriff auf den Host geomap.nagvis.org
via port 80.
NagVis benutzt eine simple HTTP-basierte API, um das Map-Image und die Koordinaten dieses Images zu erhalten.
In den meisten Fällen hat der NagVis-Host keinen direkten Internet-Zugriff. Sie können die http_proxy
Option im [global]
-Abschnitt Ihrer NagVis-Hauptkonfigurationsdatei (nagvis.ini.php) verwenden, um NagVis anzuweisen,
einen Proxy für solche Anfragen zu benutzen. Die meisten Proxies erfordern eine Authentifizierung, um den Zugang zum
Internet zu kontrollieren. Mit der Option http_proxy_auth
können die Zugangsdaten gesetzt werden.
NagVis wird mit einer Demo-Geomap namens "demo-geomap" ausgeliefert. Wenn Ihr NagVis korrekt konfiguriert ist, sollten Sie eine Karte von Deutschland mit zwei Knoten sehen. Ein Knoten zeigt den Host "ham-srv1" in Hamburg. Der andere Knoten "muc-srv1" steht in München.
Die Geomap wird definiert mit Hilfe der Map-Konfigurationsdatei "demo-geomap.cfg". Der Inhalt sieht ungefähr so aus:
global { sources=geomap alias=Demo: 4 Geomap parent_map=demo-overview iconset=std_medium backend_id=demo # Geomap Parameters source_type=csv source_file=demo-locations width=800 height=600 }
Die Zeile sources=geomap
bewirkt, dass die geomap-Source benutzt werden soll, um die Map-Konfiguration zu ändern.
Die Zeile source_type=csv
weist den geomap-Code an, die CSV-Datei zu lesen,
die in source_file=demo-locations
angegeben und im Verzeichnis etc/geomap
abgelegt ist, um mit einer Liste
von Hosts und Koordinaten eine Geomap zu füllen.
Die Datei demo-locations.csv
enthält die folgenden zwei Zeilen:
ham-srv1;Hamburg Server 1;53.556866;9.994622 muc-srv1;Munich Server1;48.1448353;11.5580067
Jede Zeile definiert einen Host, der zur Map hinzugefügt werden soll. Die Spalten werden durch ;
-Zeichen
getrennt. Die ersten Spalte enthält den Host-Namen, die zweite einen optionalen Alias, die dritte die LAT-Koordinate
(Breitengrad) und die vierte die LONG-Koordinate (Längengrad).
(Ab Git-Version vom 21.03.2013): Zeilen, die mit den üblichen Kommentarzeichen beginnen
(;
, #
oder //
), werden als Kommentar behandelt.
: Es ist auch möglich, source_type=backend
zu setzen, um das per backend_id
eingestellte Backend für die Ermittlung der anzuzeigenden Hosts und ihrer
Koordinaten zu nutzen. Das ist nur möglich, wenn das livestatus-Backend genutzt wird. Es holt alle Hosts, bei denen die
benutzerdefinierten Objektvariablen _LAT
und _LONG
konfiguriert sind. Es ist möglich, die ermittelten
Hosts durch Angabe der Option filter_group
auf die Mitgliedschaft der angegebenen Host-Gruppe einzugrenzen.
Die Geomap-Source benutzt Anzeigeparameter zur Konfiguration. Für Einzelheiten werfen Sie einen Blick auf den "Ansicht ändern"-Dialog, der im Header-Menü über "Aktionen -> Ansicht ändern" geöffnet werden kann.
Die Anzeigeparameter können auch als Map-Konfigurationsattribute im global-Abschnitt der Maps angegeben werden.
Parameter | Default | Beschreibung |
---|---|---|
geomap_type | mapnik | Definiert den Render-Modus der Geomap. Gültige Werte sind: osmarender, mapnik oder cycle. |
geomap_zoom | Konfiguriert den Zoom-Faktor der Geomap während der Map-Abfragen. Werfen Sie einen Blick auf die OSM-Zoom-Dokumentation für weitere Details. | |
geomap_border | 0.25 | Der Rand, der auf jeder Seite der Geomap hinzugefügt werden soll. Dieser Wert wird einfach zu den berechneten min/max Geo-Koordinaten addiert. |
source_type | csv | Der Typ der Data-Source, die genutzt wird, um die Geomap-Objekte zu ermitteln. Kann csv oder
backend sein. |
source_file | Der Name der CSV-Datei, die als Quelle für das Rendering der Geomap genutzt werden soll. Das wird nur genutzt, wenn
source_type auf csv gesetzt ist. |
|
width | Definiert die Breite der Geomap in Pixeln. Die maximale Größe ist begrenzt durch den benutzten Web-Service. geomap.nagvis.org unterstützt bis zu 50 "Kacheln", was ein Auflösind bis zu 1920x1080 ermöglichen sollte. Bitte kontaktieren Sie uns, falls Sie mehr benötigen sollten. | |
height | Definiert die Höhe der Geomap in Pixeln. Die maximale Größe ist begrenzt durch den benutzten Web-Service. geomap.nagvis.org unterstützt bis zu 50 "Kacheln", was ein Auflösind bis zu 1920x1080 ermöglichen sollte. Bitte kontaktieren Sie uns, falls Sie mehr benötigen sollten. |
share/userfiles/templates/pages/
relativ zum NagVis-Root-Verzeichnis abgelegt.
Die Template sind wie folgt benannt: *.header.html
.Die folgenden Makros sind in den Header-Menüs verfügbar:
Makro | Beschreibung |
---|---|
{currentMap} (war [current_map]) | Name der aktuellen Map (z.B. demo,demo2) |
{currentMapAlias} (war [current_map_alias]) | Alias der aktuellen Map |
{currentLanguage} (war [current_language]) | Zeichenkette, die die aktuell eingestellte Sprache enthält (z.B. de_DE). Dies wird für den Verweis auf die Dokumentation benötigt. |
{$currentUser} | Name des aktuellen Benutzers. |
{$mod} | Das aktuelle Modul (Map, AutoMap, Overview, Welcome, ...). |
{$act} | Die aktuelle Aktion (view, edit, ...). |
{$bRotation} | Ist "true" wenn gerade eine Rotation betrachtet wird, sonst "false".. |
{$permittedOverview} | Ist "true", wenn der Benutzer für die Übersichtsseite berechtigt ist, sonst "false".. |
{$permittedEdit} | Ist "true", wenn der Benutzer die aktuelle Map editieren darf, sonst "false".. |
{$permittedEditAnyMap} | Ist "true",wenn der Benutzer mindestens eine Map editieren darf, sonst "false".. |
{$permittedChangePassword} | Ist "true", wenn der Benutzer berechtigt ist, sein eigenes Passwort zu ändern, sonst "false".. |
{$permittedEditMainCfg} | Ist "true", wenn der Benutzer berechtigt ist, die Hauptkonfigurationsdatei zu ändern, sonst "false".. |
{$permittedManageBackgrounds} | Ist "true", wenn der Benutzer berechtigt ist, Hintergründe zu verwalten, sonst "false".. |
{$permittedManageMaps} | Ist "true", wenn der Benutzer berechtigt ist, Maps zu verwalten, sonst "false".. |
{$permittedManageShapes} | Ist "true", wenn der Benutzer berechtigt ist, Shapes zu verwalten, sonst "false".. |
{$permittedUserMgmt} | Ist "true", wenn der Benutzer berechtigt ist, Benutzerkonten zu verwalten, sonst "false".. |
{$permittedRoleMgmt} | Ist "true", wenn der Benutzer berechtigt ist, Benutzerrollen zu verwalten, sonst "false".. |
{$permittedLogout} | Ist "true", wenn der Benutzer berechtigt ist, sich abzumelden, sonst "false".. |
{$supportedChangePassword} | Ist "true", wenn das aktuelle Authentifizierungsmodul das Ändern von Passwörtern unterstützt, sich abzumelden, sonst "false".. |
{foreach $maps map} {$map.mapName} {/foreach} |
Eine Liste aller Maps, die in NagVis definiert sind. Der Code zwischen {foreach $maps map} und {/foreach}
wird für jede Map ausgeführt. Ein Beispiel finden Sie in share/userfiles/templates/pages/default.header.html .
Innerhalb der BEGIN/END-Tags sind die folgenden Makros verfügbar: * {$map.mapName} (war [map_name]): Name der Map * {$map.mapAlias} (war [map_alias]): Alias der Map * {$map.permittedEdit}: Ist der Benutzer zur Änderung dieser Map berechtigt? |
{foreach $langs lang} {$lang.language} {/foreach} |
Eine Liste aller Sprachen, die für die Benutzer verfügbar sind. Der Code zwischen {foreach $langs lang} und {/foreach} wird für jede Sprache ausgeführt. Ein Beispiel finden Sie in share/userfiles/templates/pages/default.header.html .Innerhalb der BEGIN/END-Tags sind die folgenden Makros verfügbar: * {$lang.language}: Interner Name der Sprache * {$lang.classUnderline}: Unterstreichen der Sprache * {$lang.langLanguageLocated}: Gefundener Name der Sprache. |
{if $viewType == 'Map' || $viewType == 'Automap'} | Um in den Templates flexibler zu sein, haben wir eine Art von "if"-Statement hinzugefügt. Es kann wie in PHP benutzt werden. Ein Beispiel finden Sie in share/userfiles/templates/pages/default.header.html .. |
{$pathBase} (war [html_base]) | URL zur HTML-Basis (/nagvis) |
{$pathImages} (war [html_images]) | URL zu den HTML-Images (/nagvis/images) |
{$pathHeaderJs} | Pfad zur Header-spezifischen JavaScript-Datei |
{$pathTemplates} (war [html_templates]) | Pfad zu den Header-Templates (/nagvis/userfiles/templates) |
{$pathTemplateImages} (war [html_template_images]) | Pfad zu den Header-Template-Images (/nagvis/userfiles/images/templates) |
{$langOpen} (war [lang_select_map]) | Label für das Öffnen neuer Ansichten |
{$langEditMap} (war [lang_edit_map]) | Label zum Editieren einer Map |
{$langNeedHelp} (war [lang_need_help]) | Label für Hilfe-Auswahl |
{$langOnlineDoc} (war [lang_online_doc]) | Label für den Link zur Online-Dokumentation |
{$langForum} (war [lang_forum]) | Label für den Link zum NagVis-Forum |
{$langSupportInfo} (war [lang_support_info]) | Label für den Link zu Support-Informationen |
{$langOverview} (war [lang_overview]) | Label für Überblick |
{$langInstance} (war [lang_instance]) | Label für den Instanznamen |
{$langRotationStart} (war [lang_rotation_start]) | Label zum Starten der Map-Rotation |
{$langRotationStop} (war [lang_rotation_stop]) | Label zum Stoppen der Map-Rotation |
{$langSearch} | Label für das Suchen von Objekten auf der Map. |
{$langToggleGrid} | Label für das De/Aktivieren des Rasters. |
{$langActions} | Label für die Auswahl verfügbarer Aktionen. |
{$langUser} | Label für den Benutzer. |
{$langLoggedIn} | Label für "Logged in as". |
{$langChangePassword} | Label für das Ändern des Benutzer-Passworts. |
{$langUserMgmt} | Label für die Verwaltung der Benutzer. |
{$langManageRoles} | Label für die Verwaltung der Rollen. |
{$langLogout} | Label für das Abmelden des Benutzers. |
{$langChooseLanguage} | Label für die Auswahl der Benutzer-Sprache. |
share/userfiles/templates/
relativ zum NagVis-Root-Verzeichnis zu finden.
Die Templates sind wie folgt benannt: *.hover.html
Die folgenden Makros sind in allen Objekttypen verfügbar:
Makro | Beschreibung |
---|---|
Allgemeines | |
[obj_type] | Art des Objekts (host, service, hostgroup, ...) |
[obj_name] | Name des Objekts (hostname, hostgroupname, servicegroupname, mapname, ...) |
[obj_alias] | Alias des Objekts (wenn kein Alias definiert ist, ist es identisch zu [obj_name]) |
[obj_display_name] | Anzeigename des Objekts |
[obj_state] | Zustand des Objekts (OK,WARNING,CRITICAL,...) |
[obj_summary_state] | Gesamtzustand des Objekts und aller abhängigen Objekte (OK,WARNING,CRITICAL,...) |
[obj_acknowledged] | wenn der Status bestätigt ist, wird das Makro durch "(Acknowledged)" ersetzt |
[obj_summary_acknowledged] | wenn der Gesamtzustand bestätigt ist, wird das Makro durch "(Acknowledged)" ersetzt |
[obj_in_downtime] | wenn das Objekt gerade in einer Ausfallzeit ist, wird das Makro durch "(In Downtime)" ersetzt |
[obj_summary_in_downtime] | wenn das Objekt gerade in einer Ausfallzeit ist, wird das Makro durch "(In Downtime)" ersetzt |
[obj_output] | Ausgabe für dieses Objekt |
[obj_summary_output] | Gesamtausgabe des Objekts |
Sprach-Makros | |
[lang_name] | Label für den Objektnamen |
[lang_child_name] | Label für Child-Objektnamen |
[lang_alias] | Label für den Objektalias |
[lang_address] | Label für die Objektadresse |
[lang_state] | Label für den Objektzustand |
[lang_obj_type] | Label für die Objektart |
[lang_summary_state] | Label für den Gesamtzustand |
[lang_output] | Label für die Objektausgabe |
[lang_summary_output] | Label für die Gesamtausgabe |
[lang_overview] | Label für Überblick |
[lang_instance] | Label für die Instanz-Zeichenkette |
[lang_next_check] | Label für den nächsten Check des Objekts |
[lang_last_check] | Label für den letzten Check des Objekts |
[lang_current_attempt] | Label für den aktuellen Versuch |
[lang_last_state_change] | Label für den letzten Zustandswechsel |
[lang_state_duration] | Label für die Dauer des Zustands |
[lang_service_description] | Label für die Service-Beschreibung |
[lang_notes] | Label für die Objekt-Anmerkungen |
Pfade | |
[html_base] | URL zur HTML-Basis (/nagios/nagvis) |
[html_templates] | Pfad zu Hover-Templates (nagvis/nagvis/etc/templates/hover) |
[html_template_images] | Pfad zu Hover-Template-Images (nagvis/nagvis/images/templates/hover) |
<!-- BEGIN host -->.+?<!-- END host -->
Makro | Beschreibung |
---|---|
[obj_backendid] | die Backend-id des Backend-Objekts (backend_<*>) |
[obj_backend_instancename] | der NDO-Instanzname des Backend-Objekts |
Makro | Beschreibung |
---|---|
[obj_address] | Die Adresse des Host-Objekts. |
[obj_last_check] | Datum und Uhrzeit des letzten Checks dieses Objekts; Angabe im definierten Format. |
[obj_next_check] | Datum und Uhrzeit des nächsten Checks dieses Objekts; Angabe im definierten Format. |
[obj_state_type] | der aktuelle Zustandstyp (HARD/SOFT) |
[obj_current_check_attempt] | die aktuelle Zahl der Check-Versuche |
[obj_max_check_attempts] | die Zahl der max. Check-Versuche |
[obj_last_state_change] | Datum und Uhrzeit des letzten Zustandswechsels; Angabe im definierten Format. |
[obj_last_hard_state_change] | Datum und Uhrzeit des letzten HARD-Zustandswechsels; Angabe im definierten Format. |
[obj_state_duration] | die Dauer des aktuellen Zustands |
[obj_notes] | die Anmerkungen für die Host- oder Service-Objekte |
Makro | Beschreibung |
---|---|
[service_description] | Service-Beschreibung in Nagios |
[pnp_hostname] | Hostname PNP (Leerzeichen ersetzt durch Unterstrich) |
[pnp_service_description] | Service-Beschreibung für PNP (Leerzeichen ersetzt durch Unterstrich) |
Makro | Beschreibung |
---|---|
[pnp_hostname] | Hostname PNP (Leerzeichen ersetzt durch Unterstrich) |
<!-- BEGIN servicegroup_child --><!-- END servicegroup_child -->
.
Makro | Beschreibung |
---|---|
[lang_child_name1] | Label des Hostnamens des abh. Service |
[obj_name1] | Hostname des abh. Service |
Seit 1.6b2 ist es möglich, NagVis in den local/
-Pfad von OMD-Sites zu
kopieren. Bitte beachten Sie: Dies wird lediglich zu Testzwecken empfohlen,
z.B. wenn Sie brandneue Features von neuen NagVis-Versionen testen möchten, die noch nicht in
OMD enthalten sind. Wir empfehlen nicht, dies in produktiven Umgebungen zu
tun, es sei denn, Sie wissen wirklich was Sie tun!
In den meisten Fällen erfolgt dies durch ausführen von
su - <sitename>
Holen Sie sich das aktuelle Paket Die letzte Ausgabe finden Sie unter nagvis.org.
Entpacken Sie das Archiv an eine temporäre Stelle (z.B. /tmp) und wechseln Sie in dieses Verzeichnis
tar xvzf nagvis-1.8*.tar.gz /tmp cd /tmp/nagvis-1.8*
Der OMD-Site-Installer befindet sich im root-Verzeichnis des NagVis-Pakets. Der Installer muss ausführbar gemacht werden, bevor Sie ihn benutzen können.
chmod +x omd_install.sh
Nun können Sie das Installer-Skript ausführen.
./omd_install.sh
Bestätigen Sie die Frage mit y
und warten Sie, bis das Skript endet.
Das sollte schnell passieren.
Sie können die Sourcen nach der Installation entfernen.
rm -rf /tmp/nagvis-1.8*
Nun sollten Sie die neue Version benutzen können, indem Sie in Ihrem Browser die folgende URL eingeben
http://<hostname>/<sitename>/nagvisnagvis-nagvis-1.9.47/docs/de_DE/installation_instructions.html 0000664 0000000 0000000 00000016040 15014016017 0024467 0 ustar 00root root 0000000 0000000
tar xvzf nagvis-1.8.x.tar.gz
/usr/local/nagvis
die beste Wahl. mv nagvis-1.8.x /usr/local/nagvisSie sollten mindestens die folgenden Dateien und Verzeichnisse unter dem nagvis-Verzeichnis sehen
ls -l /usr/local/nagvis etc LICENSE README share varVerschieben Sie KEINE Dateien oder Verzeichnisse innerhalb des NagVis-Verzeichnisses (Sie können das tun, aber in diesem Fall müssen Sie einige Parameter und Werte in der Hauptkonfigurationsdatei anpassen/hinzufügen wenn Sie nichts verändern, sollte es sofort funktionieren)
cd /usr/local/nagvisEine Beispiel-Hauptkonfigurationsdatei finden Sie als
etc/nagvis.ini.php-sample
.
Wenn Sie Einstellungen verändern möchten, kopieren Sie dieses Beispiel nach etc/nagvis.ini.php
:cp etc/nagvis.ini.php-sample etc/nagvis.ini.phpNun können Sie dieses Datei mit Ihrem bevorzugten Texteditor ändern ich benutze vi:
vi etc/nagvis.ini.phpDie meisten Zeilen in der frisch kopierten
nagvis.ini.php
sind auskommentiert (beginnen mit einem Semikolon). Wenn Sie verschiedene Einstellungen setzen möchten, dann entfernen Sie das Kommentarzeichen und
ändern Sie den Wert. Seit NagVis 1.5 ist es notwendig, den Web-Server zu konfigurieren, um NagVis zu nutzen.
Sie finden eine Beispiel-Konfigurationsdatei in etc/apache2-nagvis.conf-sample
.
Kopieren Sie einfach die Datei in das conf.d
-Verzeichnis Ihres Web-Servers.
Dies ist z.B. /etc/apache2/conf.d
.
cp etc/apache2-nagvis.conf-sample /etc/apache2/conf.d/apache2-nagvis.confNun müssen Sie die Datei öffnen und auf Ihre Anforderungen anpassen. Es ist wichtig, die Makros
@NAGVIS_WEB@
und @NAGVIS_PATH@
durch die korrekten Werte zu ersetzen.@NAGVIS_WEB@
durch /nagvis
und @NAGVIS_PATH@
durch /usr/local/nagvis/share
ersetzen.
wwwrun
). Wenn Sie nicht wissen, mit welchem Benutzer der Webserver läuft, dann werfen Sie einen Blick in die Webserver-Konfiguration. Im Falle von Apache können Sie dies mit dem folgenden Befehl tun:grep -e 'USER' /etc/apache2/envvarsSuSE/RedHat/Debian (SLES, OpenSuSE, Fedora)
grep -e '^User' /etc/apache2/*.confWenn Ihre Konfigurationsdatei an anderer Stelle liegt, dann passen Sie den obigen Befehl an.
chown wwwrun:www /usr/local/nagvis -R chmod 664 /usr/local/nagvis/etc/nagvis.ini.php chmod 775 /usr/local/nagvis/etc/maps chmod 664 /usr/local/nagvis/etc/maps/* chmod 775 /usr/local/nagvis/etc/automaps chmod 664 /usr/local/nagvis/etc/automaps/* chmod 775 /usr/local/nagvis/share/userfiles/images/maps chmod 664 /usr/local/nagvis/share/userfiles/images/maps/* chmod 775 /usr/local/nagvis/var chmod 664 /usr/local/nagvis/var/* chmod 775 /usr/local/nagvis/var/tmpl/cache chmod 664 /usr/local/nagvis/var/tmpl/cache/*Es ist möglich, restriktivere Berechtigungen für die Dateien zu setzen, aber für die meisten Setups sollten die Beispiele ausreichen. Verändern Sie die Werte nur dann, wenn Sie wissen, was Sie tun!
Es gibt zwei Wege, NagVis zu konfigurieren. Der erste ist die web-basierte Konfiguration mit Hilfe des NagVis-Frontends (http://<nagiosserver>/<Pfad-zu-NagVis>/
). Schauen Sie sich die Optionen des Header-Menüs an. Zum Editieren von Map-Objekten müssen Sie das Objekt entsperren, das Sie bearbeiten möchten.
Beim zweiten Weg bearbeiten Sie direkt die Konfigurationsdateien mit dem Text-Editor Ihrer Wahl. Die Map-Konfigurationsdateien befinden sich in etc/maps/
.
Gültige Formate und Werte finden Sie unter Map Config Format Description.
http://<nagiosserver>/<Pfad-zu-NagVis>/frontend/nagvis-js/?mod=Map&show=<mapname>(z.B. http://localhost/frontend/nagvis-js/?mod=Map&show=deutschland)
Seit NagVis 1.4 gibt es einen neuen Installer. Dieser Installer wurde erstellt, um die Installation oder Aktualisierung zu vereinfachen. Der Installer ist ein bash-Script, das alle benötigten Informationen zur Installation oder Aktualisierung von NagVis abfragt. Sie können auch alle Optionen über Kommandozeilenparameter steuern.
Holen Sie sich NagVis. Die neueste Version finden Sie unter nagvis.org.
Entpacken Sie das Archiv in ein beliebiges Verzeichnis (z.B. /tmp) und wechseln Sie in dieses Verzeichnis
tar xvzf nagvis-1.8*.tar.gz /tmp cd /tmp/nagvis-1.8*
Den Installer finden Sie im Hauptverzeichnis des NagVis-Package. Der Installer muss ausführbar gemacht werden, bevor Sie ihn nutzen können.
chmod +x install.sh
Sie können nun den Installer aufrufen:
./install.sh
Wenn Sie Icinga verwenden, sollten Sie "-s icinga" hinzufügen.
./install.sh -s icinga
Wenn Sie den Anweisungen des Installers folgen, sollten alle benötigen Dateien an die richtigen Stellen kopiert werden.
Bitte beachten Sie, dass die Konfigurationsdatei nagvis.ini.pnp
angepasst werden muss.
Bei Problemen informieren Sie uns bitte.
Sie können die Sourcen nach der Installation entfernen.
rm -rf /tmp/nagvis-1.8*
Für Details zu den Kommandozeilenparametern rufen Sie den Installer mit der Option "-h" auf.
nagvis-nagvis-1.9.47/docs/de_DE/lines_weathermap_style.html 0000664 0000000 0000000 00000010521 15014016017 0023707 0 ustar 00root root 0000000 0000000Als Standard kann NagVis nur die normalen Zustände in roten, gelben und grünen Linien darstellen. Wollten Sie schon immer schöne wetterkartenähnliche Linien in NagVis anzeigen?
Seit NagVis 1.5 ist es möglich, solche wetterkartenähnliche Linien zu zeichnen, die mehr als drei Farben haben können, um so z.B. die aktuelle Auslastung des Netzwerk-Interfaces darzustellen. Es gibt beispielsweise eine Palette von sieben unterschiedlichen Farben. Werfen Sie einen Blick auf das Bild - schön, oder?
Die Wetterkarten-Linientypen bieten aktuell zwei Typen von Linien:
---%--><--%----
: Pfeile mit Prozentangaben in der Mitte der Linie---%+BW--><--%+BW---
: Pfeile mit Prozentangaben in der Mitte der Linie und zusätzliche Label, die die aktuelle Bandbreitennutzung anzeigen.Die neuen Linien zielen auf Bandbreitenvisualisierung. Da NagVis die Performance-Daten untersuchen muss, um die richtige Farbe für die Linie zu ermitteln, gibt es spezielle Anforderungen an den Aufbau der Performance-Daten. Es gibt ein Bandbreitenmess-Plugin für Nagios, das bereits die richtigen Performance-Daten-Informationen liefert. Sie erhalten es auf Nagios Exchange.
Um Wetterkarten-Linientypen in NagVis anzulegen, benötigt man Services, die die richtigen Performance-Daten an Nagios liefern. Wenn Sie das haben, dann platzieren Sie einfach ein Linienobjekt auf der Map und wählen Sie den richtigen Linientyp. Nun werfen Sie einen Blick auf Ihre Map - es sollte bereits funktionieren.
Sie möchten vielleicht eine Legende, die Ihnen die Bedeutung der verschiedenen Farben anzeigt. Kein Problem. Fügen Sie ein Shape zu Ihrer Map hinzu und wählen Sie das "demo_traffic_load_legend"-Shape, das mit dem NagVis-Basis-Package ausgeliefert wird.
Die Wetterkartenlinien erfordern kein spezielles Nagios-Plugin. Lediglich die Performance-Daten müssen einem der beiden folgenden Formate entsprechen:
inUsage=21103.42%;85;98 outUsage=226363.55%;85;98 inBandwidth=105.52MBs
outBandwidth=212.22MBs
.in=7196.50566429;;;0;1250000.0 inucast=11.6273564992;;;; innucast=0.017617206817;;;; indisc=0.0;;;; inerr=0.0;0.01;0.1;; out=4044.9635368;;;0;1250000.0 outucast=12.1734899105;;;; outnucast=0.0;;;; outdisc=0.0;;;; outerr=0.0;0.01;0.1;; outqlen=0;;;;
.
Danke an gjfrater für die Implementierung dieser Linien!
nagvis-nagvis-1.9.47/docs/de_DE/map_config_format_description.html 0000664 0000000 0000000 00000223614 15014016017 0025226 0 ustar 00root root 0000000 0000000Das NagVis-Konfigurationsdateiformat ist sehr ähnlich zu dem Format, das von Nagios(TM) benutzt wird.
Konfigurationsanweisungen beginnen mit dem Schlüsselwort "define" gefolgt von einem Typfeld und einer öffnenden geschweiften Klammer ({). Jede folgende Zeile definiert Variablen-Werte-Paare, getrennt durch ein Gleichheitszeichen ( = ), bis zu einer schließenden geschweiften Klammer (}).
Hashes (#) werden benutzt, um Kommentare zu markieren. Beachten Sie, dass eine Kommentarzeile mit einem Hash-Zeichen beginnen MUSS, alle anderen Zeichen (auch "Whitespaces") sind ungültig!
define global { map_image=lan.png }
Wert | Default | Beschreibung |
---|---|---|
map_image | Das Bild, das als Hintergrund der NagVis-Map angezeigt werden soll (z.B. eine Visio (TM)-Zeichnung). Der Wert kann auch "none" oder leer sein für kein Hintergrundbild Es ist auch mölich URLs anzugeben. Diese mssen zwischen eckige Klammern [ ] gesetzt werden. |
|
alias | Map-Name | Der Alias ist das Label für jede Map. Wenn definiert, wird es überall im NagVis-Frontend und WUI angezeigt |
backend_id | vererbt (nagvis.ini.php) | Die in der Hauptkonfigurationsdatei definierte Backend-ID, die angibt, wo NagVis nach Objektzuständen suchen soll. Wenn dieser Parameter nicht angegeben wird, wird das in der Hauptkonfigurationsdatei unter "defaultbackend" angegebene Backend benutzt. |
background_color | vererbt (nagvis.ini.php) | Hintergrundfarbe dieser Map. Falls dieser Wert nicht gesetzt wird, wird die Hintergrundfarbe aus der Hauptkonfigurationsdatei genommen. |
context_menu | vererbt (nagvis.ini.php) | Aktivieren/deaktivieren des Kontext-Menüs auf Ihren Map-Objekten. |
context_template | vererbt (nagvis.ini.php) | Default Context-Template, das auf dieser Map benutzt werden soll |
event_background | vererbt (nagvis.ini.php) | Aktivieren/deaktivieren der sich ändernden Hintergrundfarbe bei Statusänderungen (die konfigurierte Farbe wird angezeigt, wenn der Gesamtstatus PENDING, OK oder UP ist). |
event_highlight | vererbt (nagvis.ini.php) | Aktivieren/deaktivieren der Hervorhebung des sich ändernden Objekts durch eine blinkende Umrandung. |
event_highlight_duration | vererbt (nagvis.ini.php) | Setzen der Hervorhebungsdauer in Millisekunden |
event_highlight_interval | vererbt (nagvis.ini.php) | Setzen des Hervorhebungsinterall in Millisekunden |
event_log | vererbt (nagvis.ini.php) | Aktivieren/deaktivieren des Eventlogs im neuen JavaScript-Backend. Das Eventlog protokolliert wichtige Aktionen und Informationen. |
event_log_level | vererbt (nagvis.ini.php) | Loglevel des Eventlogs (verfügbar: debug, info, warning, critical). |
event_log_height | vererbt (nagvis.ini.php) | Höhe des JavaScript-Eventlogs in Pixeln. |
event_log_hidden | vererbt (nagvis.ini.php) | Verstecken/zeigen des JavaScript-Eventlogs während des Map-Ladens. |
event_scroll | vererbt (nagvis.ini.php) | Aktivieren/deaktivieren des Fokussierens auf das Icon, das den Zustand verändert hat, wenn dieses außerhalb des sichtbaren Bereichs ist. |
event_sound | vererbt (nagvis.ini.php) | Aktivieren/deaktivieren von Sound-Signalen bei Statusänderungen. |
exclude_members | Es ist möglich, member-Objekte komplett auszuschließen, während die Objektinformationen vom Backend geholt werden. Die gefilterten Elemente werden nirgendwo in diesem Objekt auftauchen. Details zur Filter-Syntax finden Sie bei der exclude regex-Definition. (Neu in 1.6b4) |
|
exclude_member_states | Es ist möglich, ein oder mehrere member-Zustände während der Ermittlung des Gesamtzustands von Objekten auszuschließen. Die gefilterten Elemente werden in der member-Liste auftauchen, aber nicht für Gesamtstatusberechnungen benutzt. Details zur Filter-Syntax finden Sie bei der exclude regex-Definition. (Neu in 1.6b4) |
|
grid_color | vererbt (nagvis.ini.php) | Die Farbe der Rasterlinien |
grid_show | vererbt (nagvis.ini.php) | Aktivieren/deaktivieren von Rasterlinien zur Ausrichtung von Objekten im WUI. Objekte werden an der linken, oberen Ecke ausgerichtet |
grid_steps | vererbt (nagvis.ini.php) | Abstand der Rasterlinien |
header_menu | vererbt (nagvis.ini.php) | aktivieren/deaktivieren des Header-Menüs |
header_template | vererbt (nagvis.ini.php) | header template für diese Map |
hover_childs_limit | vererbt (nagvis.ini.php) | max. Anzahl von Child-Objekten |
hover_childs_order | vererbt (nagvis.ini.php) | Reihenfolge von Child-Objekten ("asc"=aufsteigend, "desc"=absteigend) |
hover_childs_show | vererbt (nagvis.ini.php) | Anzeigen von Child-Objekten in Hover-Menüs |
hover_childs_sort | vererbt (nagvis.ini.php) | Sortierreihenfolge von Child-Objekten ("s"=Status, "a"=Alphabet) |
hover_delay | vererbt (nagvis.ini.php) | Verzögerung der Anzeige des Hover-Menus in Sekunden |
hover_menu | vererbt (nagvis.ini.php) | aktivieren/deaktivieren von Hover-Menüs |
hover_template | vererbt (nagvis.ini.php) | Default hover template für diese Map |
iconset | vererbt (nagvis.ini.php) | Iconset, das als Standard für alle auf der Map platzierten Objekte benutzt werden soll. Kann für jedes Objekt überschrieben werden. Im Beispiel wird "std_small" benutzt, was bedeutet, dass ein OK-Zustand das Icon "std_small_ok.png", benutzt, ein CRITICAL-Zustand "std_small_critical.png" usw. |
in_maintenance | 0 | aktiviert/deaktiviert den Wartungsmodus. Wenn eine Map im Wartungsmodus ist, wird statt der Map lediglich ein Hinweis angezeigt |
label_show | 0 | Labelanzeige für die Map-Objekte aktivieren/deaktivieren |
label_x | -20 | x-Position der Label in Pixeln (mit Vorzeichen +/- relativ zur linken, oberen Ecke der Icons, sonst absolute Position) |
label_y | +20 | y-Position der Label in Pixeln (mit Vorzeichen +/- relativ zur linken, oberen Ecke der Icons, sonst absolute Position) |
label_width | auto | Default-Breite der Label in Pixeln |
label_background | transparent | Default-Hintergrundfarbe der Label. Die Farbe sollte als Hexcode angegeben werden, kann aber auch "transparent" sein. |
label_border | #000000 | Default-Rahmenfarbe der Label. Die Farbe sollte als Hexcode angegeben werden, kann aber auch "transparent" sein. |
label_style | #000000 | Benutzerdefiniertes Aussehen des Label-Textes im Format von HTML-Style-Attributen, z.B. font-family:sans;font-weight:bold; . |
line_type | Gibt den Linientyp an, wenn view_type=line. Gültige Werte sind: "11" für Linien mit einem Pfeil am Linienende. "10" für Linien mit zwei Pfeilen, die in der Linienmitte aufeinander zeigen. "12" für Linien ohne Pfeil(e). |
|
line_width | 3 | Dies definiert die Linienbreite in px, wenn dieses Objekt als Linie angezeigt wird. |
line_weather_colors | 10:#8c00ff,25:#2020ff,40:#00c0ff,55:#00f000,70:#f0f000,85:#ffc000,100:#ff0000 | Dies definiert die Farben von Wetterkarten-Farben in den unterschiedlichen Prozentstufen. Über 10% wird z.B. #8c00ff als Farbe benutzt. |
only_hard_states | vererbt (nagvis.ini.php) | Gibt an, ob Soft-Zustände ignoriert werden sollen. Default ist 0. |
parent_map | Die Eltern-Map dieser Karte. Die Option wird nur bei den Menü-Visualisierungen des Header-Menüs und der Sidebar benutzt | |
recognize_services | vererbt (nagvis.ini.php) | Definiert, ob die Services des Hosts den angezeigten Status beeinflussen. Wenn auf "1" gesetzt, wird ein Service im Status CRITICAL auch den HOST als CRITICAL anzeigen. Wenn auf "0" gesetzt, wird nur der Host-Zustand (UP oder DOWN) angezeigt und der Status der Services ignoriert. Ist dieser Wert nicht in der Konfiguration angegeben, wird er auf 1 gesetzt. |
show_in_lists | vererbt (nagvis.ini.php) | Map-Anzeige in Listenformat (Dropdowns, Indexseite, ...) |
show_in_multisite | vererbt (nagvis.ini.php) | Zeigen der Maps im Multisite-Snapin |
stylesheet | vererbt (nagvis.ini.php) | Dateiname des benutzerdefinierten Stylesheets zur Verwendung in den Maps. Die Datei muss im share/nagvis/style-Verzeichnis abgelegt sein. |
url_target | _self | Ziel des Icon-Links, diese Option passt <a target=""> an (_self ist das gleiche Fenster) |
define host { host_name=localhost x=100 y=200 }
Wert | Default | Beschreibung |
---|---|---|
object_id | Eindeutiger Bezeichner des Objekts auf der aktuellen Map. Jedes Objekt der Map benötigt eine object_id. Die object_id besteht aus alphanumerischen Zeichen beliebiger Länge. Wenn keine object_id angegeben ist, wird NagVis für das Objekt eine erzeugen | |
host_name | Name des Hosts wie in Nagios definiert | |
x | X-Koordinate | |
y | Y-Koordinate | |
backend_id | vererbt (global) | Die in der Hauptkonfigurationsdatei definierte Backend-ID, die angibt, wo NagVis nach Objektzuständen suchen soll. Wenn dieser Parameter nicht angegeben wird, wird das in der Hauptkonfigurationsdatei unter "defaultbackend" angegebene Backend benutzt. |
context_menu | vererbt (nagvis.ini.php) | Aktivieren/deaktivieren des Kontext-Menüs auf Ihren Map-Objekten. |
context_template | vererbt (nagvis.ini.php) | Default Context-Template, das auf dieser Map benutzt werden soll |
exclude_members | Es ist möglich, member-Objekte komplett auszuschließen, während die Objektinformationen vom Backend geholt werden. Die gefilterten Elemente werden nirgendwo in diesem Objekt auftauchen. Details zur Filter-Syntax finden Sie bei der exclude regex-Definition. (Neu in 1.6b4) |
|
exclude_member_states | Es ist möglich, ein oder mehrere member-Zustände während der Ermittlung des Gesamtzustands von Objekten auszuschließen. Die gefilterten Elemente werden in der member-Liste auftauchen, aber nicht für Gesamtstatusberechnungen benutzt. Details zur Filter-Syntax finden Sie bei der exclude regex-Definition. (Neu in 1.6b4) |
|
hover_menu | vererbt (nagvis.ini.php) | aktivieren/deaktivieren von Hover-Menüs |
hover_delay | vererbt (nagvis.ini.php) | Verzögerung der Anzeige des Hover-Menus in Sekunden |
hover_template | vererbt (nagvis.ini.php) | Default hover template für diese Map |
hover_url | URL, der im Hover-Menu statt der Standard-Informationen angezeigt werden soll. Verfügbare Makros: [host_name]: Dieses Makro steht für den Objektnamen. |
|
hover_childs_show | vererbt (nagvis.ini.php) | Anzeigen von Child-Objekten in Hover-Menüs |
hover_childs_sort | vererbt (nagvis.ini.php) | Sortierreihenfolge von Child-Objekten ("s"=Status, "a"=Alphabet) |
hover_childs_order | vererbt (nagvis.ini.php) | Reihenfolge von Child-Objekten ("asc"=aufsteigend, "desc"=absteigend) |
hover_childs_limit | vererbt (nagvis.ini.php) | max. Anzahl von Child-Objekten |
iconset | vererbt (global) | Spezielles Iconset. Wird vom global-Paragraph vererbt, falls es hier nicht angegeben wird. |
label_show | vererbt (global) | Labelanzeige für die Map-Objekte aktivieren/deaktivieren |
label_text | [name] | Text des Labels. Verfügbare Makros: [name], [output] |
label_x | vererbt (global) | x-Position der Label in Pixeln (mit Vorzeichen +/- relativ zur linken, oberen Ecke der Icons, sonst absolute Position) |
label_y | vererbt (global) | y-Position der Label in Pixeln (mit Vorzeichen +/- relativ zur linken, oberen Ecke der Icons, sonst absolute Position) |
label_width | vererbt (global) | Breite des Labels in Pixeln |
label_background | vererbt (global) | Hintergrundfarbe des Labels. Die Farbe sollte als Hexcode angegeben werden, kann aber auch "transparent" sein. |
label_border | vererbt (global) | Rahmenfarbe des Labels. Die Farbe sollte als Hexcode angegeben werden, kann aber auch "transparent" sein. |
label_style | vererbt (global) | benutzerdefiniertes Aussehen des Label-Textes im Stil von HTML-Attributen, z.B. font-family:sans;font-weight:bold; |
line_type | vererbt (global) | Gibt den Typ der Linie an, wenn view_type=line ist. Gültige Werte sind "11" für Linien mit einem Pfeil an jedem Ende "10" für Linien mit zwei Pfeilen in der Mitte der Linie, die aufeinander zeigen "12" für Linien ohne Pfeile |
line_width | vererbt (global) | Dies definiert die Breite der Linie, wenn dieses Objekt als Linie angezeigt wird. |
only_hard_states | vererbt (global) | Gibt an, ob Soft-Zustände ignoriert werden sollen. Default ist 0. |
recognize_services | vererbt (global) | Definiert, ob die Services des Hosts den angezeigten Status beeinflussen. Wenn auf "1" gesetzt, wird ein Service im Status CRITICAL auch den HOST als CRITICAL anzeigen. Wenn auf "0" gesetzt, wird nur der Host-Zustand (UP oder DOWN) angezeigt und der Status der Services ignoriert. Ist dieser Wert nicht in der Konfiguration angegeben, wird er auf 1 gesetzt. |
url | URL, auf den das Icon verweisen soll. Default ist ein Verweis auf die Nagios-CGIs. Die Makros [host_name], [htmlcgi] und [htmlbase] sind verfügbar. Der Wert kann leer sein, um den Link zu deaktivieren. |
|
url_target | _self | Ziel des Icon-Links, diese Option passt <a target=""> an (_self ist das gleiche Fenster). Das Makro [name] ist verfügbar. |
use | Kommaseparierte Liste von zu benutzenden Objekt-Templates. Details siehe template | |
view_type | icon | Diese Option definiert das Aussehen dieses Objekts. Mögliche Werte sind: "icon" oder "line". Vor NagVis 1.4 konnten Sie das Aussehen eines Objekts durch die Option line_type ändern. Seit NagVis 1.4 müssen Sie die Option view_type benutzen, um Icons als Linien anzuzeigen. |
z | 1 | Die z-Option definiert die Reihenfolge, in der die Icons aufeinander gestapelt werden. Das Icon mit dem höchsten Wert wird auf der Spitze dargestellt. Das Hintergrundbild hat den Wert 0, so dass gültige Werte 1 oder größer sein müssen. Hinweis: Um Konflikte mit der Header-Navigation zu verhindern, sollte dieser Wert unter 100 bleiben. |
define service { host_name=localhost service_description=ping iconset=std_big x=100 y=200 }
Wert | Default | Beschreibung |
---|---|---|
object_id | Eindeutiger Bezeichner des Objekts auf der aktuellen Map. Jedes Objekt der Map benötigt eine object_id. Die object_id besteht aus alphanumerischen Zeichen beliebiger Länge. Wenn keine object_id angegeben ist, wird NagVis für das Objekt eine erzeugen | |
host_name | Name des Hosts wie in Nagios definiert | |
service_description | Name des Service wie in Nagios definiert | |
x | X-Koordinate | |
y | Y-Koordinate | |
backend_id | vererbt (global) | Die in der Hauptkonfigurationsdatei definierte Backend-ID, die angibt, wo NagVis nach Objektzuständen suchen soll. Wenn dieser Parameter nicht angegeben wird, wird das in der Hauptkonfigurationsdatei unter "defaultbackend" angegebene Backend benutzt. |
context_menu | vererbt (nagvis.ini.php) | Aktivieren/deaktivieren des Kontext-Menüs auf Ihren Map-Objekten. |
context_template | vererbt (nagvis.ini.php) | Default Context-Template, das auf dieser Map benutzt werden soll |
exclude_members | Es ist möglich, member-Objekte komplett auszuschließen, während die Objektinformationen vom Backend geholt werden. Die gefilterten Elemente werden nirgendwo in diesem Objekt auftauchen. Details zur Filter-Syntax finden Sie bei der exclude regex-Definition. (Neu in 1.6b4) |
|
exclude_member_states | Es ist möglich, ein oder mehrere member-Zustände während der Ermittlung des Gesamtzustands von Objekten auszuschließen. Die gefilterten Elemente werden in der member-Liste auftauchen, aber nicht für Gesamtstatusberechnungen benutzt. Details zur Filter-Syntax finden Sie bei der exclude regex-Definition. (Neu in 1.6b4) |
|
gadget_url | Der Wert kann ein Gadget-Script im Gadget-Verzeichnis (nagvis/gadgets ) sein, z.B. "std_speedometer.php" oder eine in Klammern gesetzte komplette URI auf ein Gadget-Script, z.B. "[http://127.0.0.1/nagvis/gadgets/std_speedometer.php]". Details zu Gadgets finden Sie hier. Diese Option wird nur erkannt, wenn view_type="gadget" gesetzt ist. |
|
gadget_scale | 100 | Die Größe des Gadgets. Default ist 100 (Prozent). Die Gadgets sollten in der Lage sein, abhängig von diesem Parameter zu skalieren |
gadget_opts | Optionale Gadget-spezifische Parameter. Die Inhalte können für jedes Gadget frei definiert werden. Der Wert wird als GET-Parameter "opts" verarbeitet. Wir empfehlen, ein var/val-Format zu nutzen: key1=val1,key2=val2. Dadurch können Sie diese Zeichenkette im Gadget leicht in ein Array aufteilen. | hover_menu | vererbt (nagvis.ini.php) | aktivieren/deaktivieren von Hover-Menüs |
hover_template | vererbt (global) | Hover template für dieses Objekt |
hover_delay | vererbt (nagvis.ini.php) | Verzögerung der Anzeige des Hover-Menus in Sekunden |
hover_url | URL, der im Hover-Menu statt der Standard-Informationen angezeigt werden soll. Verfügbare Makros: [host_name]: Dieses Makro steht für den Objektnamen. [service_description]: Dieses Makro steht für die Service-Beschreibung und wird nur in Service-Objekten ersetzt. |
|
hover_childs_show | vererbt (nagvis.ini.php) | Anzeigen von Child-Objekten in Hover-Menüs |
hover_childs_sort | vererbt (nagvis.ini.php) | Sortierreihenfolge von Child-Objekten ("s"=Status, "a"=Alphabet) |
hover_childs_order | vererbt (nagvis.ini.php) | Reihenfolge von Child-Objekten ("asc"=aufsteigend, "desc"=absteigend) |
hover_childs_limit | vererbt (nagvis.ini.php) | max. Anzahl von Child-Objekten |
iconset | vererbt (global) | Spezielles Iconset. Wird vom global-Paragraph vererbt, falls es hier nicht angegeben wird |
label_show | vererbt (global) | Labelanzeige für die Map-Objekte aktivieren/deaktivieren |
label_text | [name][service_description] | Text des Labels. Verfügbare Makros: [name], [service_description], [output] |
label_x | vererbt (global) | x-Position der Label in Pixeln (mit Vorzeichen +/- relativ zur linken, oberen Ecke der Icons, sonst absolute Position) |
label_y | vererbt (global) | y-Position der Label in Pixeln (mit Vorzeichen +/- relativ zur linken, oberen Ecke der Icons, sonst absolute Position) |
label_width | vererbt (global) | Breite des Labels in Pixeln |
label_background | vererbt (global) | Hintergrundfarbe des Labels. Die Farbe sollte als Hexcode angegeben werden, kann aber auch "transparent" sein. |
label_border | vererbt (global) | Rahmenfarbe des Labels. Die Farbe sollte als Hexcode angegeben werden, kann aber auch "transparent" sein. |
label_style | vererbt (global) | benutzerdefiniertes Aussehen des Label-Textes im Stil von HTML-Attributen, z.B. font-family:sans;font-weight:bold; |
line_cut | 0.5 | Linien mit zwei Teilen haben den Schnitt in der Mitte der Linie. Dies entspricht einem "line_cut"-Wert von "0.5". Es ist möglich, den Schnitt durch Veränderung des Wertes zu verschieben. Gültige Werte sind 0.0 bis 1.0. |
line_label_pos_in | 0.5 | Bei Wetterkarten-Linien sind die Bezeichnungen normalerweise in der Mitte der Linie. Dies entspricht einem Wert von "0.5". Es ist möglich, die Platzierung durch diesen Werte zu verschieben. Gültige Werte liegen zwischen 0.0 to 1.0. |
line_label_pos_out | 0.5 | Bei Wetterkarten-Linien sind die Bezeichnungen normalerweise in der Mitte der Linie. Dies entspricht einem Wert von "0.5". Es ist möglich, die Platzierung durch diesen Werte zu verschieben. Gültige Werte liegen zwischen 0.0 to 1.0. |
line_label_y_offset | 2 | Diese Option definiert den Abstand der Bezeichnungen zur Linie beim Rendern von Wetterkarten-Linien, die Prozent- und absolute Bandbreitendaten anzeigen. |
line_weather_colors | vererbt (global) | Dies definiert die Farben von Wetterkarten-Farben in den unterschiedlichen Prozentstufen. Über 10% wird z.B. #8c00ff als Farbe benutzt. |
line_type | vererbt (global) | Gibt den Typ der Linie an, wenn view_type=line ist. Gültige Werte sind "11" für Linien mit einem Pfeil an jedem Ende "10" für Linien mit zwei Pfeilen in der Mitte der Linie, die aufeinander zeigen "12" für Linien ohne Pfeile |
line_width | vererbt (global) | Dies definiert die Breite der Linie, wenn dieses Objekt als Linie angezeigt wird. |
only_hard_states | vererbt (global) | Gibt an, ob Soft-Zustände ignoriert werden sollen. Default ist 0. |
url | URL, auf den das Icon verweisen soll. Default ist ein Verweis auf die Nagios-CGIs. Verfügbare Makros: [host_name], [service_description], [htmlcgi] und [htmlbase]. Der Wert kann leer sein, um den Link zu deaktivieren. | |
url_target | _self | Ziel des Icon-Links, diese Option passt <a target=""> an (_self ist das gleiche Fenster). Verfügbare Makros: [name], [service_description] |
use | Kommaseparierte Liste von zu benutzenden Objekt-Templates. Details siehe template | |
view_type | icon | Diese Option definiert das Aussehen dieses Objekts. Mögliche Werte sind: "icon" oder "line". Vor NagVis 1.4 konnten Sie das Aussehen eines Objekts durch die Option line_type ändern. Seit NagVis 1.4 müssen Sie die Option view_type benutzen, um Icons als Linien anzuzeigen. |
z | 1 | Die z-Option definiert die Reihenfolge, in der die Icons aufeinander gestapelt werden. Das Icon mit dem höchsten Wert wird auf der Spitze dargestellt. Das Hintergrundbild hat den Wert 0, so dass gültige Werte 1 oder größer sein müssen. Hinweis: Um Konflikte mit der Header-Navigation zu verhindern, sollte dieser Wert unter 100 bleiben. |
define hostgroup { hostgroup_name=servers x=100 y=200 }
Wert | Default | Beschreibung |
---|---|---|
object_id | Eindeutiger Bezeichner des Objekts auf der aktuellen Map. Jedes Objekt der Map benötigt eine object_id. Die object_id besteht aus alphanumerischen Zeichen beliebiger Länge. Wenn keine object_id angegeben ist, wird NagVis für das Objekt eine erzeugen | |
hostgroup_name | Name der Hostgroup wie in Nagios definiert | |
x | X-Koordinate | |
y | Y-Koordinate | |
backend_id | vererbt (global) | Die in der Hauptkonfigurationsdatei definierte Backend-ID, die angibt, wo NagVis nach Objektzuständen suchen soll. Wenn dieser Parameter nicht angegeben wird, wird das in der Hauptkonfigurationsdatei unter "defaultbackend" angegebene Backend benutzt. |
context_menu | vererbt (nagvis.ini.php) | Aktivieren/deaktivieren des Kontext-Menüs auf Ihren Map-Objekten. |
context_template | vererbt (nagvis.ini.php) | Default Context-Template, das auf dieser Map benutzt werden soll |
exclude_members | Es ist möglich, member-Objekte komplett auszuschließen, während die Objektinformationen vom Backend geholt werden. Die gefilterten Elemente werden nirgendwo in diesem Objekt auftauchen. Details zur Filter-Syntax finden Sie bei der exclude regex-Definition. (Neu in 1.6b4) |
|
exclude_member_states | Es ist möglich, ein oder mehrere member-Zustände während der Ermittlung des Gesamtzustands von Objekten auszuschließen. Die gefilterten Elemente werden in der member-Liste auftauchen, aber nicht für Gesamtstatusberechnungen benutzt. Details zur Filter-Syntax finden Sie bei der exclude regex-Definition. (Neu in 1.6b4) |
|
hover_menu | vererbt (nagvis.ini.php) | aktivieren/deaktivieren von Hover-Menüs |
hover_template | vererbt (global) | Hover template für dieses Objekt |
hover_delay | vererbt (nagvis.ini.php) | Verzögerung der Anzeige des Hover-Menus in Sekunden |
hover_url | URL, der im Hover-Menu statt der Standard-Informationen angezeigt werden soll. Verfügbare Makros: [hostgroup_name]: Dieses Makro steht für den Objektnamen. |
|
hover_childs_show | vererbt (nagvis.ini.php) | Anzeigen von Child-Objekten in Hover-Menüs |
hover_childs_sort | vererbt (nagvis.ini.php) | Sortierreihenfolge von Child-Objekten ("s"=Status, "a"=Alphabet) |
hover_childs_order | vererbt (nagvis.ini.php) | Reihenfolge von Child-Objekten ("asc"=aufsteigend, "desc"=absteigend) |
hover_childs_limit | vererbt (nagvis.ini.php) | max. Anzahl von Child-Objekten |
iconset | vererbt (global) | Spezielles Iconset. Wird vom global-Paragraph vererbt, falls es hier nicht angegeben wird |
label_show | vererbt (global) | Labelanzeige für die Map-Objekte aktivieren/deaktivieren |
label_text | [name] | Text des Labels, verfügbare Makros: [name] und [output] |
label_x | vererbt (global) | x-Position der Label in Pixeln (mit Vorzeichen +/- relativ zur linken, oberen Ecke der Icons, sonst absolute Position) |
label_y | vererbt (global) | y-Position der Label in Pixeln (mit Vorzeichen +/- relativ zur linken, oberen Ecke der Icons, sonst absolute Position) |
label_width | vererbt (global) | Breite des Labels in Pixeln |
label_background | vererbt (global) | Hintergrundfarbe des Labels. Die Farbe sollte als Hexcode angegeben werden, kann aber auch "transparent" sein. |
label_border | vererbt (global) | Rahmenfarbe des Labels. Die Farbe sollte als Hexcode angegeben werden, kann aber auch "transparent" sein. |
label_style | vererbt (global) | Benutzerdefiniertes Aussehen des Label-Textes im Format von HTML-Style-Attributen, z.B. font-family:sans;font-weight:bold; . |
line_type | vererbt (global) | Gibt den Typ der Linie an, wenn view_type=line ist. Gültige Werte sind "11" für Linien mit einem Pfeil an jedem Ende "10" für Linien mit zwei Pfeilen in der Mitte der Linie, die aufeinander zeigen "12" für Linien ohne Pfeile |
line_width | vererbt (global) | Dies definiert die Breite der Linie, wenn dieses Objekt als Linie angezeigt wird. |
recognize_services | vererbt (global) | Definiert, ob die Services des Hosts den angezeigten Status beeinflussen. Wenn auf "1" gesetzt, wird ein Service im Status CRITICAL auch den HOST als CRITICAL anzeigen. Wenn auf "0" gesetzt, wird nur der Host-Zustand (UP oder DOWN) angezeigt und der Status der Services ignoriert. Ist dieser Wert nicht in der Konfiguration angegeben, wird er auf 1 gesetzt. |
url | URL, auf den das Icon verweisen soll. Default ist ein Verweis auf die Nagios-CGIs. Die Makros [hostgroup_name], [htmlcgi] und [htmlbase] sind verfügbar. Der Wert kann leer sein, um den Link zu deaktivieren. | |
url_target | _self | Ziel des Icon-Links, diese Option passt <a target=""> an (_self ist das gleiche Fenster). Verfügbares Makro: [name] |
use | Kommaseparierte Liste von zu benutzenden Objekt-Templates. Details siehe template | |
view_type | icon | Diese Option definiert das Aussehen dieses Objekts. Mögliche Werte sind: "icon" oder "line". Vor NagVis 1.4 konnten Sie das Aussehen eines Objekts durch die Option line_type ändern. Seit NagVis 1.4 müssen Sie die Option view_type benutzen, um Icons als Linien anzuzeigen. |
z | 1 | Die z-Option definiert die Reihenfolge, in der die Icons aufeinander gestapelt werden. Das Icon mit dem höchsten Wert wird auf der Spitze dargestellt. Das Hintergrundbild hat den Wert 0, so dass gültige Werte 1 oder größer sein müssen. Hinweis: Um Konflikte mit der Header-Navigation zu verhindern, sollte dieser Wert unter 100 bleiben. |
define servicegroup { servicegroup_name=servicegroup1 x=100 y=200 }
Wert | Default | Beschreibung |
---|---|---|
object_id | Eindeutiger Bezeichner des Objekts auf der aktuellen Map. Jedes Objekt der Map benötigt eine object_id. Die object_id besteht aus alphanumerischen Zeichen beliebiger Länge. Wenn keine object_id angegeben ist, wird NagVis für das Objekt eine erzeugen | |
servicegroup_name | Name der Servicegroup wie in Nagios definiert. | |
x | X-Koordinate | |
y | Y-Koordinate | |
backend_id | vererbt (global) | Die in der Hauptkonfigurationsdatei definierte Backend-ID, die angibt, wo NagVis nach Objektzuständen suchen soll. Wenn dieser Parameter nicht angegeben wird, wird das in der Hauptkonfigurationsdatei unter "defaultbackend" angegebene Backend benutzt. |
context_menu | vererbt (nagvis.ini.php) | Aktivieren/deaktivieren des Kontext-Menüs auf Ihren Map-Objekten. |
context_template | vererbt (nagvis.ini.php) | Default Context-Template, das auf dieser Map benutzt werden soll |
exclude_members | Es ist möglich, member-Objekte komplett auszuschließen, während die Objektinformationen vom Backend geholt werden. Die gefilterten Elemente werden nirgendwo in diesem Objekt auftauchen. Details zur Filter-Syntax finden Sie bei der exclude regex-Definition. (Neu in 1.6b4) |
|
exclude_member_states | Es ist möglich, ein oder mehrere member-Zustände während der Ermittlung des Gesamtzustands von Objekten auszuschließen. Die gefilterten Elemente werden in der member-Liste auftauchen, aber nicht für Gesamtstatusberechnungen benutzt. Details zur Filter-Syntax finden Sie bei der exclude regex-Definition. (Neu in 1.6b4) |
|
hover_menu | vererbt (nagvis.ini.php) | aktivieren/deaktivieren von Hover-Menüs |
hover_url | URL, der im Hover-Menu statt der Standard-Informationen angezeigt werden soll. Verfügbare Makros: [servicegroup_name]: Dieses Makro steht für den Objektnamen. |
|
hover_template | vererbt (global) | Hover template für dieses Objekt |
hover_delay | vererbt (nagvis.ini.php) | Verzögerung der Anzeige des Hover-Menus in Sekunden |
hover_childs_show | vererbt (nagvis.ini.php) | Anzeigen von Child-Objekten in Hover-Menüs |
hover_childs_sort | vererbt (nagvis.ini.php) | Sortierreihenfolge von Child-Objekten ("s"=Status, "a"=Alphabet) |
hover_childs_order | vererbt (nagvis.ini.php) | Reihenfolge von Child-Objekten ("asc"=aufsteigend, "desc"=absteigend) |
hover_childs_limit | vererbt (nagvis.ini.php) | max. Anzahl von Child-Objekten |
iconset | vererbt (global) | Spezielles Iconset. Wird vom global-Paragraph vererbt, falls es hier nicht angegeben wird |
label_show | vererbt (global) | Labelanzeige für die Map-Objekte aktivieren/deaktivieren |
label_text | [name] | Text des Labels, verfügbare Makros: [name] und [output] |
label_x | vererbt (global) | x-Position der Label in Pixeln (mit Vorzeichen +/- relativ zur linken, oberen Ecke der Icons, sonst absolute Position) |
label_y | vererbt (global) | y-Position der Label in Pixeln (mit Vorzeichen +/- relativ zur linken, oberen Ecke der Icons, sonst absolute Position) |
label_width | vererbt (global) | Breite des Labels in Pixeln |
label_background | vererbt (global) | Hintergrundfarbe des Labels. Die Farbe sollte als Hexcode angegeben werden, kann aber auch "transparent" sein. |
label_border | vererbt (global) | Rahmenfarbe des Labels. Die Farbe sollte als Hexcode angegeben werden, kann aber auch "transparent" sein. |
label_style | vererbt (global) | Benutzerdefiniertes Aussehen des Label-Textes im Format von HTML-Style-Attributen, z.B. font-family:sans;font-weight:bold; . |
line_type | vererbt (global) | Gibt den Typ der Linie an, wenn view_type=line ist. Gültige Werte sind "11" für Linien mit einem Pfeil an jedem Ende "10" für Linien mit zwei Pfeilen in der Mitte der Linie, die aufeinander zeigen "12" für Linien ohne Pfeile |
line_width | vererbt (global) | Dies definiert die Breite der Linie, wenn dieses Objekt als Linie angezeigt wird. |
only_hard_states | vererbt (global) | Gibt an, ob Soft-Zustände ignoriert werden sollen. Default ist 0. |
url | URL, auf den das Icon verweisen soll. Default ist ein Verweis auf die Nagios-CGIs. Verfügbare Makros: [servicegroup_name], [htmlcgi] und [htmlbase]. Der Wert kann leer sein, um den Link zu deaktivieren. | |
url_target | _self | Ziel des Icon-Links, diese Option passt <a target=""> an (_self ist das gleiche Fenster). Verfügbare Makros: [name]. |
use | Kommaseparierte Liste von zu benutzenden Objekt-Templates. Details siehe template | |
view_type | icon | Diese Option definiert das Aussehen dieses Objekts. Mögliche Werte sind: "icon" oder "line". Vor NagVis 1.4 konnten Sie das Aussehen eines Objekts durch die Option line_type ändern. Seit NagVis 1.4 müssen Sie die Option view_type benutzen, um Icons als Linien anzuzeigen. |
z | 1 | Die z-Option definiert die Reihenfolge, in der die Icons aufeinander gestapelt werden. Das Icon mit dem höchsten Wert wird auf der Spitze dargestellt. Das Hintergrundbild hat den Wert 0, so dass gültige Werte 1 oder größer sein müssen. Hinweis: Um Konflikte mit der Header-Navigation zu verhindern, sollte dieser Wert unter 100 bleiben. |
define map { map_name=webserver x=77 y=156 }
Wert | Default | Beschreibung |
---|---|---|
object_id | Eindeutiger Bezeichner des Objekts auf der aktuellen Map. Jedes Objekt der Map benötigt eine object_id. Die object_id besteht aus alphanumerischen Zeichen beliebiger Länge. Wenn keine object_id angegeben ist, wird NagVis für das Objekt eine erzeugen | |
map_name | Name der Map-Konfigurationsdatei (ohne .cfg-Erweiterung) | |
x | X-Koordinate | |
y | Y-Koordinate | |
context_menu | vererbt (nagvis.ini.php) | Aktivieren/deaktivieren des Kontext-Menüs auf Ihren Map-Objekten. |
context_template | vererbt (nagvis.ini.php) | Default Context-Template, das auf dieser Map benutzt werden soll |
exclude_members | Es ist möglich, member-Objekte komplett auszuschließen, während die Objektinformationen vom Backend geholt werden. Die gefilterten Elemente werden nirgendwo in diesem Objekt auftauchen. Details zur Filter-Syntax finden Sie bei der exclude regex-Definition. (Neu in 1.6b4) |
|
exclude_member_states | Es ist möglich, ein oder mehrere member-Zustände während der Ermittlung des Gesamtzustands von Objekten auszuschließen. Die gefilterten Elemente werden in der member-Liste auftauchen, aber nicht für Gesamtstatusberechnungen benutzt. Details zur Filter-Syntax finden Sie bei der exclude regex-Definition. (Neu in 1.6b4) |
|
hover_menu | vererbt (nagvis.ini.php) | aktivieren/deaktivieren von Hover-Menüs |
hover_url | URL, der im Hover-Menu statt der Standard-Informationen angezeigt werden soll. Verfügbare Makros: [map_name]: Dieses Makro steht für den Objektnamen. |
|
hover_template | vererbt (global) | Hover template für dieses Objekt |
hover_delay | vererbt (nagvis.ini.php) | Verzögerung der Anzeige des Hover-Menus in Sekunden |
hover_childs_show | vererbt (nagvis.ini.php) | Anzeigen von Child-Objekten in Hover-Menüs |
hover_childs_sort | vererbt (nagvis.ini.php) | Sortierreihenfolge von Child-Objekten ("s"=Status, "a"=Alphabet) |
hover_childs_order | vererbt (nagvis.ini.php) | Reihenfolge von Child-Objekten ("asc"=aufsteigend, "desc"=absteigend) |
hover_childs_limit | vererbt (nagvis.ini.php) | max. Anzahl von Child-Objekten |
iconset | vererbt (global) | Spezielles Iconset. Wird vom global-Paragraph vererbt, falls es hier nicht angegeben wird |
label_show | vererbt (global) | Labelanzeige für die Map-Objekte aktivieren/deaktivieren |
label_text | [name] | Text des Labels, verfügbare Makros: [name] und [output] |
label_x | vererbt (global) | x-Position der Label in Pixeln (mit Vorzeichen +/- relativ zur linken, oberen Ecke der Icons, sonst absolute Position) |
label_y | vererbt (global) | y-Position der Label in Pixeln (mit Vorzeichen +/- relativ zur linken, oberen Ecke der Icons, sonst absolute Position) |
label_width | vererbt (global) | Breite des Labels in Pixeln |
label_background | vererbt (global) | Hintergrundfarbe des Labels. Die Farbe sollte als Hexcode angegeben werden, kann aber auch "transparent" sein. |
label_border | vererbt (global) | Rahmenfarbe des Labels. Die Farbe sollte als Hexcode angegeben werden, kann aber auch "transparent" sein. |
label_style | vererbt (global) | Benutzerdefiniertes Aussehen des Label-Textes im Format von HTML-Style-Attributen, z.B. font-family:sans;font-weight:bold; . |
line_type | vererbt (global) | Gibt den Typ der Linie an, wenn view_type=line ist. Gültige Werte sind "11" für Linien mit einem Pfeil an jedem Ende "10" für Linien mit zwei Pfeilen in der Mitte der Linie, die aufeinander zeigen "12" für Linien ohne Pfeile |
line_width | vererbt (global) | Dies definiert die Breite der Linie, wenn dieses Objekt als Linie angezeigt wird. |
only_hard_states | vererbt (global) | Gibt an, ob Soft-Zustände ignoriert werden sollen. Default ist 0. |
url | URL, auf den das Icon verweisen soll. Default ist kein Verweis. Verfügbare Makros: [map_name], [htmlcgi] und [htmlbase]. Der Wert kann leer sein, um den Link zu deaktivieren. | |
url_target | _self | Ziel des Icon-Links, diese Option passt <a target=""> an (_self ist das gleiche Fenster). Verfügbare Makros: [name]. |
use | Kommaseparierte Liste von zu benutzenden Objekt-Templates. Details siehe template | |
view_type | icon | Diese Option definiert das Aussehen dieses Objekts. Mögliche Werte sind: "icon" oder "line". Vor NagVis 1.4 konnten Sie das Aussehen eines Objekts durch die Option line_type ändern. Seit NagVis 1.4 müssen Sie die Option view_type benutzen, um Icons als Linien anzuzeigen. |
z | 1 | Die z-Option definiert die Reihenfolge, in der die Icons aufeinander gestapelt werden. Das Icon mit dem höchsten Wert wird auf der Spitze dargestellt. Das Hintergrundbild hat den Wert 0, so dass gültige Werte 1 oder größer sein müssen. Hinweis: Um Konflikte mit der Header-Navigation zu verhindern, sollte dieser Wert unter 100 bleiben. |
define textbox { text="This is an informational text which can be placed anywhere on the map, HTML can also be used for formatting purposes" x=200 y=100 w=200 }
Wert | Default | Beschreibung |
---|---|---|
object_id | Eindeutiger Bezeichner des Objekts auf der aktuellen Map. Jedes Objekt der Map benötigt eine object_id. Die object_id besteht aus alphanumerischen Zeichen beliebiger Länge. Wenn keine object_id angegeben ist, wird NagVis für das Objekt eine erzeugen | |
text | Ihr eigener Text, HTML ist möglich. Es gibt die Makros [refresh_counter]: zeigt die Zeit bis zur nächsten Aktualisierung/Rotation [worker_last_run]: zeigt die Zeit des letzten "Worker-Runs" |
|
x | X-Koordinate | |
y | Y-Koordinate | |
w | auto | Breite der Textbox in px (Pixeln). "auto" bedeutet automatische Skalierung |
h | auto | Höhe der Textbox in px (Pixeln). "auto" bedeutet automatische Skalierung |
background_color | #C0C0C0 | Hintergrundfarbe der Textbox. Die Farbe sollte als Hexcode angegeben werden, kann aber auch "transparent" sein. |
border_color | #000000 | Rahmenfarbe der Textbox. Die Farbe sollte als Hexcode angegeben werden, kann aber auch "transparent" sein. |
style | #000000 | Benutzerdefiniertes Aussehen des Textes im Format von HTML-Style-Attributen, z.B. font-family:sans;font-weight:bold; . |
use | Kommaseparierte Liste von zu benutzenden Objekt-Templates. Details siehe template | |
z | 1 | Die z-Option definiert die Reihenfolge, in der die Icons aufeinander gestapelt werden. Das Icon mit dem höchsten Wert wird an der Spitze dargestellt. Das Hintergrundbild hat den Wert 0, so dass gültige Werte 1 oder größer sein müssen. Hinweis: Um Konflikte mit der Header-Navigation zu verhindern, sollte dieser Wert unter 100 bleiben. |
define shape { icon="test" x=200 y=100 }
Wert | Default | Beschreibung |
---|---|---|
object_id | Eindeutiger Bezeichner des Objekts auf der aktuellen Map. Jedes Objekt der Map benötigt eine object_id. Die object_id besteht aus alphanumerischen Zeichen beliebiger Länge. Wenn keine object_id angegeben ist, wird NagVis für das Objekt eine erzeugen | |
Icon | Dateiname des Shapes. Shapes müssen im shape-Verzeichnis abgelegt werden (Default: nagvis/images/shapes ) |
|
x | X-Koordinate | |
y | Y-Koordinate | |
enable_refresh | 0 | Diese Option aktiviert das Shape für regelmäßige Aktualisierungen im Frontent. Dies wird nur für dynamische Shapes benötigt, die sich gelegentlich ändern. |
hover_menu | 0 | Aktivieren/Deaktivieren von Hover-Menüs |
hover_url | URL, der beim Schweben über dem Bild anzuzeigen ist. Normalerweise gibt es keine Aktion während des Schwebens. | |
hover_delay | vererbt (nagvis.ini.php) | Verzögerung der Anzeige des Hover-Menus in Sekunden |
url | URL, auf den das Icon verweisen soll. Normalerweise gibt es keinen Verweis. | |
url_target | _self | Ziel des Icon-Links, diese Option passt <a target=""> an (_self ist das gleiche Fenster) |
use | Kommaseparierte Liste von zu benutzenden Objekt-Templates. Details siehe template | |
z | 1 | Die z-Option definiert die Reihenfolge, in der die Icons aufeinander gestapelt werden. Das Icon mit dem höchsten Wert wird auf der Spitze dargestellt. Das Hintergrundbild hat den Wert 0, so dass gültige Werte 1 oder größer sein müssen. Hinweis: Um Konflikte mit der Header-Navigation zu verhindern, sollte dieser Wert unter 100 bleiben. |
define line { line_type=1 x=200 y=100 }
Wert | Default | Beschreibung |
---|---|---|
object_id | Eindeutiger Bezeichner des Objekts auf der aktuellen Map. Jedes Objekt der Map benötigt eine object_id. Die object_id besteht aus alphanumerischen Zeichen beliebiger Länge. Wenn keine object_id angegeben ist, wird NagVis für das Objekt eine erzeugen | |
line_type | Gibt den Typ der Linie an, wenn view_type=line ist. Gültige Werte sind "11" für Linien mit einem Pfeil an jedem Ende "10" für Linien mit zwei Pfeilen in der Mitte der Linie, die aufeinander zeigen "12" für Linien ohne Pfeile |
|
x | X-Koordinate | |
y | Y-Koordinate | |
hover_menu | 0 | Aktivieren/Deaktivieren von Hover-Menüs |
hover_url | URL, der beim Schweben über dem Bild anzuzeigen ist. Normalerweise gibt es keine Aktion während des Schwebens. | |
hover_delay | vererbt (nagvis.ini.php) | Verzögerung der Anzeige des Hover-Menus in Sekunden |
line_color | #ffffff | Die Füllfarbe der Linie, kann auch "transparent" sein. |
line_color_border | #000000 | Die Randfarbe der Linie, kann auch "transparent" sein. |
line_width | vererbt (global) | Dies definiert die Breite der Linie, wenn dieses Objekt als Linie angezeigt wird. |
url | URL, auf den das Icon verweisen soll. Normalerweise gibt es keinen Verweis. | |
url_target | _self | Ziel des Icon-Links, diese Option passt <a target=""> an (_self ist das gleiche Fenster) |
use | Kommaseparierte Liste von zu benutzenden Objekt-Templates. Details siehe template | |
z | 1 | Die z-Option definiert die Reihenfolge, in der die Icons aufeinander gestapelt werden. Das Icon mit dem höchsten Wert wird auf der Spitze dargestellt. Das Hintergrundbild hat den Wert 0, so dass gültige Werte 1 oder größer sein müssen. Hinweis: Um Konflikte mit der Header-Navigation zu verhindern, sollte dieser Wert unter 100 bleiben. |
template
.
Mit diesem Objekt haben Sie die Möglichkeit, alle optionalen Werte in einem Objekt zu definieren, das für viele andere gilt.
Sie können alle Attribute auf die Werte setzen, die Sie benötigen und diese mit dem use
-Attribut an andere Objekte vererben. define template { name=generic-template }
Wert | Default | Beschreibung |
---|---|---|
name | Template-Name (einfache Zeichenkette ohne Leerzeichen muss in der Map eindeutig sein) | |
... | Alle Werte, die in den Objekten verfügbar sind, die dieses Template erben |
Die verschiedenen Ansichten in NagVis heißen "maps". Der klassische und gebräuchlichste Typ der NagVis-Maps sind die statischen Maps. Das bedeutet, dass man mit Hilfe des Web-basierten Konfigurations-Editors oder eines Text-Editors eine Map-Konfiguration erstellt.
Ab NagVis 1.7 gibt es eine neue Erweiterung der Map-Konfiguration. Sie basiert weiterhin auf dem statischen Map-Konfigurations-Ansatz, aber nun ist es möglich, diese statischen Konfigurationsteile mit dynamischen und programmierbaren Mechanismen zu erweitern.
Die neue Möglichkeit wurde "map sources" benannt. Jede Map kann eine oder mehreren Map-Sources nutzen. Jede dieser Sources kann die gesamte Map-Konfiguration löschen, ersetzen oder verändern.
Ein Map-Source besteht aus verschiedenen PHP-Funktionen mit einem standardisierten Satz von Parametern. Die Funktionen sind komplett frei in dem, was sie tun. Eine Source kann z.B. CSV-Datei mit Objekten und Koordinaten lesen, sich mit Datenbanken verbinden, um Informationen zu holen, oder Daten von externen Diensten lesen. Der Entwickler entscheidet.
Textdateien mit PHP-Code müssen im Verzeichnis share/server/core/sources
relativ zum NagVis-Basis-Verzeichnis stehen.
In OMD werden die Site-spezifischen Dateien im Verzeichnis local/share/nagvis/htdocs/server/core/sources
relativ zum
Site-Basisverzeichnis abgelegt.
Es gibt keine 1:1-Relation zwischen den Dateien und den Sources selbst. Eine Datei kann eine, mehrere oder gar keine Source enthalten (z.B. um Funktionen zu definieren, die von mehreren Sources benutzt werden).
Eine Map-Source besteht aus zwei PHP-Funktionen, die die folgenden Spezifikationen erfüllen müssen:
Funktionsnamenmuster | Parameter |
---|---|
process_<source-name> Dies ist die tatsäliche Verarbeitungsfunktion. Sie kann die aktive Map-Konfiguration ersetzen. Der Return-Code der Funktion wird im Moment nicht genutzt. |
$MAPCFG - das GlobalMapCfg-PHP-Objekt |
$map_name - der Name der Map als Zeichenkette |
|
&$map_config - Referenz des Map-Konfigurations-Arrays. Dieses Array muss modifiziert werden, um die Map-Konfiguration
zu ändern.
|
|
changed_<source-name> Diese Funktion wird genutzt, um der Verarbeitung der Map-Konfigurationen mitzuteilen, ob sie erneut geladen werden muss oder nicht. Die Funktion muss "true" zurückliefern, damit NagVis die Konfiguration erneut verarbeitet. Das bedeutet auch, dass die process_* für alle konfigurierten Sources ausgeführt wird. |
$MAPCFG - das GlobalMapCfg-PHP-Objekt |
$compare_time - der Unix-Zeitstempel der aktuell zwischengespeicherten Map-Konfiguration.
|
Während eine Map-Konfiguration geladen wird, prüft NagVis, ob diese bereits analysiert und zwischengespeichert wurde. Ist das der Fall und der Cache ist aktuell, dann kann NagVis diese Daten viel schneller verarbeiten als wenn die Daten erst analysiert und geprüft werden müssten.
Im Allgemeinen vergleicht NagVis die Zeitstempel der verwendeten Konfigurationsdateien (Haupt- und Map-Konfigurationsdateien) mit dem Map-Konfigurations-Cache, um diese Entscheidung zu treffen.
Wenn Map-Sources verwendet werden, muss jede Source dem Map-Konfigurationsverarbeitungs-Code mitteilen, ob die Map-Konfiguration erneut geladen werden muss oder der Map-Konfigurations-Cache benutzt werden kann. Dies erfolgt durch die changed_*-Funktion jeder Source. Wenn diese Funktion "true" zurückliefert, wird NagVis die Map-Konfiguration erneut laden.
Die Map-Konfiguration zu laden bedeutet, dass NagVis die Map-Konfigurationsdatei analysiert, um das Array der Map-Objekte zu füllen. Dann werden diese Daten geprüft, um fehlerhafte Konfigurationen zu verhindern. Danach werden alle konfigurierten Map-Sources verarbeitet, um diesen die Möglichkeit zu geben, die Map-Konfiguration zu verändern.
Jede Map-Source kann Anzeigeparameter und Konfigurationsvariablen definieren, die in den Maps verfügbar sind, die diese Sourcen verwenden. Dies ist eine Beispieldefinition der Geomap-Map-Source:
// options to be modifiable by the user(url) global $viewParams; $viewParams = array( 'geomap' => array( 'zoom', 'geomap_type', 'source_file', ) ); // Config variables to be registered for this source global $configVars; $configVars = array( 'geomap_type' => array( 'must' => false, 'default' => 'osmarender', 'match' => '/^(osmarender|mapnik|cycle)$/i', 'field_type' => 'dropdown', 'list' => 'list_geomap_types', ), 'source_file' => array( 'must' => false, 'default' => '', 'match' => MATCH_STRING_EMPTY, 'field_type' => 'dropdown', 'list' => 'list_geomap_source_files', ), 'zoom' => array( 'must' => false, 'default' => '', 'match' => MATCH_INTEGER_EMPTY, ), );
Diese Definitionen führen zu a) drei neuen Map-Konfigurationsoptionen im global-Abschnitt der Map und b) zur Verfügbarkeit der Variablen in den URLs der Maps, die diese Source verwenden.
Seit der Implementierung der Map-Sources können sogar reguläre Maps ohne konfigurierte Sources mit Hilfe einiger Standard- Anzeigeparameter verändert werden. Einige der Parameter sind nicht komplett neu, sondern sie wurden lediglich zu Anzeigeparametern. umkodiert. Hier ist die Liste der allgemeinen Anzeigeparameter:
Parameter | Beschreibung |
---|---|
backend_id | Ändert das zu verwendende Standard-Backend der aktuellen Map. Einzelheiten finden Sie in der Beschreibung der Option in der Map-Konfiguration. |
iconset | Überschreibt das iconset, das im global-Abschnitt der Map konfiguriert ist. Einzelheiten finden Sie in der Beschreibung der Option Map-Konfiguration. |
width | Kann benutzt werden, um die Breite der Map-Anzeige zu ändern. Wird zurzeit nicht von regulären Maps verwendet. Diese Option wird nur von einigen Map-Sources benutzt. |
height | Kann benutzt werden, um die Höhe der Map-Anzeige zu ändern. Wird zurzeit nicht von regulären Maps verwendet. Diese Option wird nur von einigen Map-Sources benutzt. |
header_menu | Überschreibt die header_menu-Einstellung im global-Abschnitt der Map. Einzelheiten finden Sie in der Beschreibung der Option in der Map-Konfiguration. |
hover_menu | Überschreibt die hover_menu-Einstellung im global-Abschnitt der Map. Einzelheiten finden Sie in der Beschreibung der Option in der Map-Konfiguration. |
context_menu | Überschreibt die context_menu-Einstellung im global-Abschnitt der Map. Einzelheiten finden Sie in der Beschreibung der Option in der Map-Konfiguration. |
Im Moment sind zwei Map-Sources für NagVis verfügbar. Beschreibungen zu den geomap- und den automap-Sources finden Sie auf den jeweils Dokumentationsseiten.
;
) werden benutzt, um Kommentare zu markieren.
Abschnitte und Variablen mit einem vorangestellten Semikolon werden als Kommentare angesehen und von NagVis nicht erkannt.
Bei einer neuen NagVis-Installation gibt es keine Datei mit einer Default-Konfiguration.
Standardwerte sind im PHP-Code enthalten.
Konfigurationseinstellungen in der Datei etc/nagvis.ini.php
übersteuern diese Standardwerte. etc/nagvis.ini.php-sample
mit Beispiel-Konfigurationswerten. Alle Werte sind auskommentiert. Wert | Default | Beschreibung | |
---|---|---|---|
audit_log | 0 | Aktivieren/deaktiviern der Protokollierung von sicherheitsrelevanten Benutzeraktionen in NagVis. Benutzeran- und abmeldungen werden z.B. in var/nagvis-audit.log protokolliert. | |
authmodule | CoreAuthModSQLite | Definiert das zu benutzende Authentifizierungsmodul. Per Default benutzt NagVis das eingebaute SQLite-Authentifizierungsmodul. Bei der Auslieferung ist kein anderes Authentifizierungsmodul verfügbar. Es ist möglich, andere Authentifizierungsmodule hinzuzufügen, um andere Authentifizierungsmechanismen zu unterstützen. | |
authorisationmodule | CoreAuthorisationModSQLite | Definiert das zu benutzende Autorisierungsmodul. Per Default benutzt NagVis das eingebaute SQLite-Autorisierungsmodul. Bei der Auslieferung ist kein anderes Autorisierungsmodul verfügbar. Es ist möglich, andere Autorisierungsmodule hinzuzufügen, um andere Autorisierungsmechanismen zu unterstützen. | |
dateformat | Y-m-d H:i:s | Das in NagVis benutzte Format für Datum- und Zeit. Verfügbare Optionen wie bei der date()-Funktion von php | |
language | en_US | Wählen Sie die Sprache, die in NagVis benutzt werden soll. de_DE (Deutsch), en_US (Englisch), fr_FR (Französisch) und pt_BR (brasilianisches Portugiesisch; ab 1.4.4) sind als Standard verfügbar). Seit 1.4 müssen Sie die Sprache in einem anderen Format angeben. ("de_DE" statt "german") |
|
language_available | de_DE,en_US,es_ES,fr_FR,pt_BR | Sie möchten Ihren Benutzern vielleicht eine Auswahl an verschiedenen Sprachen anbieten. Sie können das Verhalten kontrollieren, ohne die Sprachdateien aus Ihrer NagVis-Installation zu löschen. Wenn dieser Wert nicht gefüllt ist, werden alle vorkonfigurierten Sprachen angeboten. Wenn Sie eine weitere Sprache hinzufügen möchten, dann müssen Sie den Wert hier eintragen | |
language_detection | user,session,browser,config | Dies kontrolliert, wie NagVis die Sprache des Benutzers ermitteln soll. NagVis kennt mehrere Mechanismen zur Erkennung der Sprache: - user: explizit vom Benutzer eingestellte Sprache - session: wenn der Benutzer eine Sprache wählt, dann wird diese in der Session gespeichert - browser: NagVis versucht, die Sprache mit Hilfe des Browser-Agenten zu ermitteln - config: die Default-Sprache der Installation Die Reihenfolge der Optionen bestimmt die Reihenfolge, in der NagVis die verschiedenen Mechanismen benutzt |
|
logonmodule | LogonMixed | Definiert das zu benutzende Logon-Modul. Per Default benutzt NagVis das Mixed-Auth-Modul, das dem Benutzernamen vertraut, der per REMOTE_USER oder dem HTML-Logon-Dialog zur Abfrage von Authentifizierungsinformationen übergeben wurde, falls REMOTE_USER nicht gesetzt ist.
Bei der Auslieferung sind die folgenden Module verfügbar: LogonMixed: Das gemischte Logon-Modul benutzt das LogonEnv-Modul als Standard und das LogonDialog-Modul als Ausweichlösung, falls LogonEnv keinen Benutzernamen zurückliefert. Das sollte den Anforderungen in den meisten Umgebungen genügen. LogonDialog: Dies ist ein HTML-Anmeldedialog, um die Authentifizierungsinformationen abzufragen. LogonEnv: Es ist möglich, einen vollständig zu "trauendem" Authentifizierungsmechanismus wie in den Vorgängerversionen von NagVis zu realisieren. Auf diese Weise wird der Benutzer nicht wirklich authentifiziert.
NagVis vertraut dem gelieferten Benutzernamen implizit. NagVis benutzt die konfigurierte Umgebungsvariable, um den Benutzer zu identifizieren. Sie können Ihrem Webserver verschiedene Authentifizierungsmechanismen hinzufügen, angefangen mit der Basic-Authentifizierung, die von Nagios genutzt wird (.htaccess) bis hin zu Single-Sign-On-Umgebungen. LogonMultisite: Dieses Modul benutzt die Authentifizierung von auth_*-Cookies, die von Checkmk-Multisite geliefert werden, wenn die Cookie-basierte Authentifizierung verwendet wird. Es ist möglich, eigene Logon-Module hinzuzufügen, um andere Dialoge zu bedienen. |
|
logonenvvar | REMOTE_USER | Definiert die Umgebungsvariable, die für das Holen des authentifizierten Benutzers aus der Webserver-Umgebung benutzt werden soll. Diese Option wird nur für die Logon-Module LogonEnv und LogonMixed verwendet. | |
logonenvcreateuser | 1 | Veranlasst das LogonEnv/LogonMixedModul, ein Benutzerkonto für jeden unbekannten Benutzer anzulegen, der die NagVis-Seite öffnet. Diese Option wird nur für die Logon-Module LogonEnv und LogonMixed verwendet. | |
logonenvcreaterole | Guests | Veranlasst das LogonEnv/LogonMixedModul, die Benutzerkonten mit der angegebenen Rolle anzulegen. Diese Option wird nur für die Logon-Module LogonEnv und LogonMixed verwendet. | |
logon_multisite_htpasswd | Der Pfad zur htpasswd-Datei, die von Multisite benutzt wird (wird nur vom LogonMultisite-Modul verwendet). | ||
logon_multisite_secret | Der Pfad zur auth-secret-Datei, die von Multisite benutzt wird (wird nur vom LogonMultisite-Modul verwendet). | ||
logon_multisite_createuser | 1 | Gleich wie die "logonenvcreateuser"-Option (wird nur vom LogonMultisite-Modul verwendet). | |
logon_multisite_createrole | Guest | Gleich wie die "logonenvcreaterole"-Option (wird nur vom LogonMultisite-Modul verwendet). | |
only_permitted_objects | 0 | Aktiviert/Deaktiviert den Zugang nur zu erlaubten Monitoring-Objekten. Dies ist nützlich wenn man den Zugriff auf Statusinformationen durch NagVis UND durch den Authorisierungmechanismus der Monitoring-Software (z.B. Nagios) beschränken möchte. Deaktiviert: Der Zugriff auf Statusinformationen wird nur von NagVis beschränkt. Jeder NagVis-Benutzer, der Zugriff auf eine Map hat kann die Statusinformationen aller Objekte auf dieser Map sehen. Falls er die Erlaubnis hat Objekte zu der Map hinzuzufügen kann er ALLE Monitoring-Objekte hinzufügen und wird dabei nicht durch das NagVis-Rechtesystem eingeschränkt. Aktiviert: Jeder Benutzer in NagVis kann nur die Statusinformationen sehen für deren Objekte er auch eine Kontaktdefinition in der Monitoring-Software hat. Das bedeutet, dass er Statusinformationen nur dann sehen kann, wenn er Zugriff auf eine Map hat UND wenn er die Erlaubnis des Monitoring-Systems hat. Das gleiche gilt für das Hinzufügen von Objekten zu einer Map. |
|
refreshtime | 60 | Aktualisierungsintervall in Maps bzw. laden der nächsten Map bei Map-Rotation | |
sesscookiedomain | automatisch ermittelt | Vielleicht möchten Sie festlegen, für welche Domain NagVis das Session-Cookie speichern soll. Per Default versucht NagVis, den Wert mit Hilfe der Web-Server-Umgebungsvariablen selbst zu ermitteln. Dies sollte in den meisten Umgebungen funktionieren, könnte sich aber z.B. durch URL-Rewriting ändern. | |
sesscookiepath | automatisch ermittelt | Vielleicht möchten Sie den Pfad festlegen, für den NagVis das Session-Cookie speichern soll. Per Default versucht NagVis, den Wert mit Hilfe der paths/htmlbase-Variablen selbst zu ermitteln. Dies sollte in den meisten Umgebungen funktionieren, könnte sich aber z.B. durch URL-Rewriting ändern. | |
sesscookieduration | 86400 | Lebensdauer des Cookies in Sekunden. Der Standardwert ist auf 24 Stunden eingestellt. Das NagVis-Session-Cookie wird bei jedem Seitenaufruf erneuert. Wenn eine Session länger als die eingestellte Zeit untätig ist, wird sie ungültig. | |
startmodule | overview | Das anzuzeigende Startmodul, wenn vom Benutzer keins angegeben wird. | |
startaction | view | Die Default-Aktion, wenn vom Benutzer keine angegeben wird. | |
startshow | Der startshow-Parameter wird zur Zeit nur von einigen Views benutzt. Er wird von den Map- und AutoMap-Modulen verwendet. |
Wert | Default | Beschreibung |
---|---|---|
base | /usr/local/nagvis/share/ | absoluter physikalischer NagVis-Pfad |
htmlbase | /nagvis | absoluter html-NagVis-Pfad |
htmlcgi | /nagvis/cgi-bin | absoluter html-NagVis-cgi-Pfad |
Wert | Default | Beschreibung |
---|---|---|
backend | live_1 | Default-Backend (ID des Backends - kopieren Sie den Text, der für <backend-id> steht, nach [backend_<backend-id>] ) |
backgroundcolor | transparent | Default-Hintergrundfarbe für Maps |
contextmenu | 0 | Aktivieren/Deaktivieren des Kontextmenüs auf Ihren Map-Objekten. |
contexttemplate | default | Default context template. |
eventbackground | 0 | aktivieren (1) bzw. deaktivieren (0) des Wechselns der Hintergrundfarbe bei Statusänderungen (die konfigurierte Farbe wird gezeigt, wenn der Gesamtstatus PENDING, OK oder UP ist) |
eventhighlight | 1 | aktivieren (1) bzw. deaktivieren (0) der Hervorhebung von Statusänderungen durch Hinzufügen einer blinkenden Umrandung |
eventhighlightduration | 10000 | Dauer der Hervorhebung in Millisekunden |
eventhighlightinterval | 500 | Intervall der Hervorhebung in Millisekunden |
eventlog | 0 | aktivieren (1) bzw. deaktivieren (0) des Ereignisprotokolls im neuen JavaScript-Frontend. Das Ereignisprotokoll enthält wichtige Aktionen und Informationen |
eventlogevents | 24 | Anzahl von Ereignissen im Ereignisprotokoll-Rückblick |
eventloglevel | info | Loglevel des Ereignisprotokolls (verfügbar: debug, info, warning, critical) |
eventheight | 100 | Höhe des JavaScript-Eventlogs in Pixeln |
eventhidden | 1 | Verstecken/Zeigen des Eventlogs während des Map-Ladens |
eventscroll | 1 | aktivieren (1) bzw. deaktivieren (0) des Bewegens zu dem Icon, das den Status verändert hat, falls das Icon nicht im sichtbaren Bereich liegt |
eventsound | 1 | aktivieren (1) bzw. deaktivieren (0) von Sound-Signalen bei Statusänderungen |
headermenu | 1 | aktivieren (1) bzw. deaktivieren (0) des Headermenüs |
headertemplate | default | Default header template |
hoverchildslimit | 10 | max. Anzahl von Child-Objekten |
hoverchildsorder | asc | Reihenfolge von Child-Objekten ("asc"=aufsteigend, "desc"=absteigend) |
hoverchildsshow | 1 | Anzeigen von Child-Objekten in Hover-Menüs |
hoverchildssort | a | Sortierreihenfolge von Child-Objekten ("s"=Status, "a"=Alphabet) |
hoverdelay | 0 | Verzögerung des Hover-Menü-Auftretens (in Sekunden) |
hovermenu | 1 | aktivieren/deaktivieren von Hover-Menüs |
hovertemplate | default | Default hover template |
icons | std_medium | Default-Iconset |
onlyhardstates | 0 | nur Hard-Zustände benutzen (keine Soft-Zustände) |
recognizeservices | 1 | Service-Zustände in Host/Hostgroup-Objekten erkennen |
showinlists | 1 | Anzeigen von Maps in Listen (Dropdowns, Index-Seite, ...) |
showinmultisite | 1 | Anzeigen der Maps im Multisite-Snapin |
stylesheet | Dateiname des benutzerdefinierten Stylesheets, das in den Maps verwendet werden soll. Die Datei muss im share/nagvis/styles-Verzeichnis abgelegt werden. | |
urltarget | _self | Ziel des Icon-Links, diese Option passt <a target=""> an (_self ist das gleiche Fenster) |
hosturl | [htmlcgi]/status.cgi?host=[host_name] | Die Default-URL, die bei einem Links-Klicks des Benutzers auf ein Host-Objekt benutzt wird. Verfügbare Makros: [htmlcgi], [htmlbase], [host_name], [backend_id] |
hostgroupurl | [htmlcgi]/status.cgi?hostgroup=[hostgroup_name] | Die Default-URL, die bei einem Links-Klicks des Benutzers auf ein Hostgruppen-Objekt benutzt wird. Verfügbare Makros: [htmlcgi], [htmlbase], [hostgroup_name], [backend_id] |
serviceurl | [htmlcgi]/extinfo.cgi?type=2&host=[host_name]&service=[service_description] | Die Default-URL, die bei einem Links-Klicks des Benutzers auf ein Service-Objekt benutzt wird. Verfügbare Makros: [htmlcgi], [htmlbase], [host_name], [service_description], [backend_id] |
servicegroupurl | [htmlcgi]/status.cgi?servicegroup=[servicegroup_name] | Die Default-URL, die bei einem Links-Klicks des Benutzers auf ein Servicegruppen-Objekt benutzt wird. Verfügbare Makros: [htmlcgi], [htmlbase], [servicegroup_name], [backend_id] |
mapurl | [htmlbase]/index.php?mod=Map&act=view&show=[map_name] | Die Default-URL, die bei einem Links-Klicks des Benutzers auf ein Map-Objekt benutzt wird. Verfügbare Makros: [htmlcgi], [htmlbase], [map_name] |
view_template | default | In den verschiedenen Views zu benutzendes Template. |
Wert | Default | Beschreibung |
---|---|---|
backgroundcolor | #ffffff | Default-Hintergrundfarbe für die Übersichtsseite |
4 | Maps pro Zeile in Map-Listen. (veraltet ab 1.8) | |
headermenu | 1 | aktivieren (1) bzw. deaktivieren (0) des Headermenüs |
headertemplate | default | Default header template |
showautomaps | 1 | aktivieren/deaktivieren der Anzeige von Automaps |
showmaps | 1 | aktivieren/deaktivieren der Anzeige von Maps |
showmapthumbs | 1 | aktivieren/deaktivieren der Anzeige von Map-Thumbnails |
showrotations | 1 | aktivieren/deaktivieren der Anzeige von definierten Rotationen |
Wert | Default | Beschreibung |
---|---|---|
defaultparams | &childLayers=2 | Dies sind die Parameter für die Automap-Ansichten und Links in den Listen (Map-Indexseite, Dropdown-Menüs in den Headern) |
defaultroot | localhost | Default-Wert für das Root-Objekt. Details finden Sie in der Automap-Dokumentation |
graphvizpath | /usr/local/bin | wenn die graphviz-Binaries (dot,neato,twopi,...) nicht über PATH gefunden werden können, muss der Pfad hier gesetzt werden |
showinlists | 1 | aktivieren/deaktivieren der Automap in Map-Listen (Map-Indexseite, Dropdown-Menüs in den Headern) |
Wert | Default | Beschreibung |
---|---|---|
25 | In diesem Intervall wird die Map von der WUI gesichert (veraltet ab 1.6). | |
grid_color | #f7f7f7 | Die Farbe der Rasterlinien. |
grid_show | 0 | Aktivieren (1) bzw. deaktivieren (0) eines Rasters, um die Ausrichtung von Objekten im WUI zu vereinfachen. Objekte werden an der linken, oberen Ecke ausgerichtet. |
grid_steps | 32 | Größe des Rasters in Pixeln. |
1 | Aktivieren (1) bzw. deaktivieren (0) des Header-Menüs im WUI (veraltet ab 1.6). | |
default | zu benutzendes Standard-Header-Template im WUI (veraltet ab 1.5). | |
maplocktime | 5 | Zeit in Minuten, die eine Map von einem editierenden Benutzer blockiert wird. |
Wert | Default | Beschreibung |
---|---|---|
interval | 5 | Das Intervall in Sekunden, in dem der Worker auf zu aktualisierende Objekte prüft. |
requestmaxlength | 1900 | Die maximale Länge von HTTP-Requests während Ajax-HTTP-Requests. Einige Intrusion Detection/Prevention-Systeme haben ein Problem mit zu langen Queries. |
requestmaxparams | 0 | Die maximale Anzahl von Parametern in Ajax-HTTP-Requests. Einige Intrusion Detection/Prevention-Systeme haben Probleme mit zu vielen Parametern im URL. 0 = keine Begrenzung. |
updateobjectstates | 15 | Die Aufbewahrungszeit in Sekunden für die Zustände im Frontend. Die Statusinformationen werden nach Ablauf dieser Zeit im folgenden Worker-Intervall aufgefrischt. |
[backend_<backend-id>]
benannt. In dem Beispiel ist live_1
die backend_id
. [backend_live_1] backendtype="mklivestatus" htmlcgi="/nagios/cgi-bin" ; the following options depend on the selected backendtype, in this case it is MKLivestatus socket="unix:/usr/local/nagios/var/rw/live
Wert | Default | Beschreibung | |
---|---|---|---|
backendtype | mklivestatus | Art des Backends - MUSS gesetzt werden | |
statushost | Der "statushost" kann genutzt werden, um lästige Timeouts zu vermeiden, wenn ein Backend nicht erreichbar ist. Dies ist nur sinnvoll in Multi-Backend-Umgebungen. Es funktioniert wie folgt: Die Annahme ist, dass es ein "lokales" Backend gibt, das den Host des "entfernten" Backends überwacht. Wenn der entfernte Backend-Host als "UP" gemeldet wird, dann wird das Backend ganz normal abgefragt. Wenn der entfernte Backend-Host als "DOWN" oder "UNREACHABLE" gemeldet wird, dann wird NagVis solange keine Verbindung dorthin versuchen, bis der Backend-Host wieder verfügbar ist. Der "statushost" muss im folgenden Format angegeben werdent: "<backend_id>:<hostname>" -> e.g. "live_2:nagios" Der Host muss in einem anderen Backend sein als der aktuelle, damit es funktioniert. |
||
htmlcgi | /nagios/cgi-bin | Pfad zum cgi-bin-Verzeichnis dieses Backends (wichtig bei mehreren Backends) | |
custom_1 | Erste benutzerdefinierte Variable, die in den Context- und Hover-Menüs verfügbar ist. Mit dieser Option können verschiedene benutzerdefinierte URLs zu den Context-/Hover-Menüs hinzugefügt werden, die jeweils vom Backend abhängig sind. Das ist u.a. nutzbar, wenn Links auf verschiedene Nagios-Instanzen hinzugefügt werden sollen. | ||
custom_2 | Zweite benutzerdefinierte Variable (s.o). | ||
custom_3 | Dritte benutzerdefinierte Variable (s.o). |
Die Backend-spezifischen Optionen finden Sie in der Backend-Dokumentation.
[rotation_demo] maps="demo,demo2" interval=15
Wert | Default | Beschreibung |
---|---|---|
interval | 15 | Map-Rotationsintervall in Sekunden |
maps |
kommaseparierte Liste von Maps in diesem Pool, die zu rotieren sind. Sie können auch externe URLs durch [ ] klammern (z.B. maps="demo1,[http://localhost/test.php]". Die URL muss von dem Server erreichbar sein, auf dem NagVis läuft. Sie können Label im folgenden Format hinzufügen: <label>:<map> und <label>:<[url]>. Die Label werden in der Rotationsliste angezeigt. Es ist außerdem möglich, Automaps zu Rotationen hinzuzufügen. Setzen Sie einfach ein "@"-Zeichen vor den Name der Automap, um sie der Rotation hinzuzufügen. |
Optionen, die die Behandlung und das Aussehen der verschiedenen Zustände in der NagVis-Installation beeinflussen.
Diese Einstellungen definieren das Verhalten der Zustandsbehandlung. Hauptsächlich ist es möglich zu konfigurieren, welcher Zustand einen anderen "überdeckt". Ein kritischer Zustand (5) wird eine Warnung (4) überdecken, ein bestätigter kritischer Zustand (2) wird nicht eine Warnung (4) überdecken.
Wert | Default |
---|---|
unreachable | 8 |
unreachable_ack | 5 |
unreachable_downtime | >5 |
down | 7 |
down_ack | 5 |
down_downtime | 5 |
critical | 7 |
critical_ack | 5 |
critical_downtime | 5 |
warning | 6 |
warning_ack | 4 |
warning_downtime | 4 |
unknown | 3 |
unknown_ack | 2 |
unknown_downtime | 2 |
error | 3 |
error_ack | 2 |
error_downtime | 2 |
ok | 1 |
up | 1 |
unchecked | 0 |
pending | 0 |
Diese Einstellungen definieren das Verhalten der Zustände im Frontend.
Value | Default |
---|---|
unreachable_bgcolor | #F1811B |
unreachable_color | #F1811B |
unreachable_ack_bgcolor | |
unreachable_downtime_bgcolor | |
unreachable_sound | std_unreachable.mp3 |
down_bgcolor | #FF0000 |
down_color | #FF0000 |
down_ack_bgcolor | |
down_downtime_bgcolor | |
down_sound | std_down.mp3 |
critical_bgcolor | #FF0000 |
critical_color | #FF0000 |
critical_ack_bgcolor | |
critical_downtime_bgcolor | |
critical_sound | std_critical.mp3 |
warning_bgcolor | #FFFF00 |
warning_color | #FFFF00 |
warning_ack_bgcolor | |
warning_downtime_bgcolor | |
warning_sound | std_warning.mp3 |
unknown_bgcolor | #FFCC66 |
unknown_color | #FFCC66 |
unknown_ack_bgcolor | |
unknown_downtime_bgcolor | |
unknown_sound | |
error_bgcolor | #0000FF |
error_color | #0000FF |
error_ack_bgcolor | |
error_downtime_bgcolor | |
error_sound | |
ok_bgcolor | #00FF00 |
ok_color | #00FF00 |
ok | |
up_bgcolor | #00FF00 |
up_color | #00FF00 |
up_sound | |
unchecked_bgcolor | #C0C0C0 |
unchecked_color | #C0C0C0 |
unchecked_sound | |
pending_bgcolor | #C0C0C0 |
pending_color | #C0C0C0 |
pending_sound |
Sie benötigen ein installiertes, konfiguriertes und lauffähiges Nagios/Icinga, damit NagVis funktioniert. Nagios bekommen Sie auf der offiziellen Nagios Homepage, Schnellstart-Installationsanleitungen finden Sie u.a. hier. Neben verfügbaren Paketen/Downloads finden Sie weitere Informationen auf der offiziellen Icinga-Homepage, die aktuelle Dokumentation hier.
Seit NagVis 1.5 ist MKLivestatus das Default-Backend, weil es viel schneller, leichtgewichtiger und stabiler als NDO ist. Außerdem ist es einfacher zu handhaben und zu installieren. Sie benötigen keine Datenbank für MKLivestatus.
MKLivestatus ist ein Eventbroker-Modul für Nagios, das einen Unix-Socket versorgt, mit dem sich Addons wie NagVis verbinden können, um aktuelle Statusinformationen abzufragen.
MKLivestatus bekommen Sie auf der offiziellen MKLivestatus-Homepage.
Neben dem PHP-Basis-Paket benötigen Sie noch die folgenden Module. Die Namen sind teilweise abhängig von der Distribution:
php -m
zeigt die eingebauten Module.
Die Backends verbinden sich mit externen Datenquellen und benötigen oftmals spezielle Module. Hier ist eine Liste für verschiedene Backends.
mklivestatusDie Automap basiert auf GraphViz. Sie brauchen es, wenn Sie das Automap-Feature nutzen möchten. Wir empfehlen GraphViz >= 2.14 für die Automap (ältere Versionen (mit niedrigeren Versionsnummern) haben Probleme mit Truecolor-Rendering).
GraphViz ist in einigen Distributionen enthalten. Wenn Sie kein vorgefertigtes Paket benutzen können, bekommen Sie GraphViz auf der offiziellen GraphViz-Homepage, und können es selbst kompilieren.
Sie benötigen weitere Packages wie gd, libpng, freetyp, ... aber wenn Sie Graphviz kompiliert/installiert haben, sollte es funktionieren.
nagvis-nagvis-1.9.47/docs/de_DE/toc.html 0000664 0000000 0000000 00000012616 15014016017 0017734 0 ustar 00root root 0000000 0000000Achtung: Diese Informationen sind nicht aktuell
Wichtigste Regel: machen Sie immer ein Backup, bevor Sie eine existierende Installation aktualisieren.Von NagVis 1.4x nach 1.5x wurde eine Menge an der Verzeichnisstruktur geändert. Das mitgelieferte Installations-Script kann NagVis 1.4x/1.5x auf das letzte 1.6x-Release aktualisieren. Daher wird empfohlen, dieses Script (install.sh
) zur Aktualisierung zu nutzen.
Die Berechtigungskonfiguration hat sich in NagVis 1.5 geändert. Deshalb entfernt das Installationsscript die Direktiven allowed_for_config und allowed_users aus den Map-Konfigurationsdateien. Die Berechtigungen werden nicht automatisch in die Berechtigungsdatenbank geladen, sondern in die nagvis/etc/auth-backup-Datei geschrieben. Mit diesen Informationen können Sie die Berechtigungen für die Maps im neuen rollenbasierten Berechtigungssystem vergeben.
Es ist auch möglich, den Update von 1.4x auf 1.6x manuell durchzuführen, aber das wurde bisher weder getestet noch dokumentiert.
Generell sollte es so funktionieren wie oben beschrieben (also kopieren der eigenen Dateien an die neuen Stellen und anpassen der nagvis.ini.php, nicht kopieren).
Wenn Sie also die Installation selbst erledigen möchten, dann werden Sie etwas probieren müssen. Bitte leiten Sie dann Ihre Erfahrungen an uns weiter, damit wir diese Dokumentation erweitern können.
URL | Beschreibung | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
NagVis Frontend | |||||||||||
index.php | Dies ist eine Weiterleitung zu nagvis/index.php (NagVis-Frontend) | ||||||||||
nagvis/frontend/nagvis-js/index.php | Dies ist der Map-Index, die Hauptseite von NagVis. Auf der Hauptseite sind alle Maps aufgeführt, für die der Benutzer berechtigt ist. Sie können eine Map ausschließen, indem Sie die show_in_lists-Option auf 0 setzen. | ||||||||||
nagvis/frontend/nagvis-js/index.php?mod=Map&show=<name> | Dies ist die klassische Map-Ansicht. In diesem Modus wird die angegebene Map angezeigt und mit Hilfe von Ajax-Aufrufen an den NagVis-Core aktualisiert. Die folgenden Parameter sind verfügbar:
|
||||||||||
nagvis/frontend/nagvis-js/index.php?info | Dies ist eine Seite mit Support-Informationen, die Sie mitliefern können, wenn Sie Probleme mit NagVis haben. | ||||||||||
Rotationen | |||||||||||
nagvis/frontend/nagvis-js/index.php?Rotation=<name> | Dies ist der Map-Rotationsmodus. In diesem Modus wird die erste angegebene Map angezeigt (Rotation muss in der Hauptkonfigurationsdatei definiert werden). Nach einem definierten Intervall wird die nächste angegebene Map geladen usf. |
Wenn Sie Probleme bei der Nutzung dieser Informationen haben, kontaktieren Sie uns unter www.nagvis.org.
Copyright © 2008-2016 NagVis Project
nagvis-nagvis-1.9.47/docs/en_US/ 0000775 0000000 0000000 00000000000 15014016017 0016324 5 ustar 00root root 0000000 0000000 nagvis-nagvis-1.9.47/docs/en_US/about.html 0000664 0000000 0000000 00000010615 15014016017 0020327 0 ustar 00root root 0000000 0000000NagVis is a visualization addon for the well known network management system Nagios® (and Icinga which is a fork of Nagios).
NagVis can be used to visualize Nagios data, e.g. to display IT processes like a mail system or a network infrastructure. Using data supplied by a backend it will update objects placed on maps in certain intervals to reflect the current state. These maps allow to arrange the objects to display them in different layouts:
In general NagVis is a presentation tool for the information which is gathered by Nagios and transferred using backends.
The supported backends are:
You can place all objects from Nagios (Host, Services, Hostgroups, Servicegroups) on so called maps. Each map can be configured through its own configuration file. You can edit the configuration files directly by using your favourite text editor or the web configuration mechanisms. Furthermore you can add some special NagVis objects to the maps. These objects are shapes, textboxes and reference objects for other maps.
Each of the objects on your maps can be configured to fit your needs. For example there are links to the Nagios frontend on each object which represents
a Nagios object. You can easily customize these links.
There is a hover menu which is enabled by default. The hover menu displays detailed information
for each object. Hover menus can easily be modified by changing the templates for them. You can also disable the hover menu.
By default the state of the objects is displayed using icons on the map. You can change these icons by adding iconsets from the NagVis
homepage or create your own. The state of the objects can also be displayed as lines or as gadgets.
Apart from the normal maps there is an automap. The objects are places automatically starting from the root host you specified. Depending on the value of the directice "filter_by_state" it will show all objects or only the ones in a non-OK state (including the way from the root object).
To be able to use the automap you have to define the parents directives in your Nagios host objects.
Starting with NagVis 1.5 you can define more than one automap.
NagVis is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License version 2 as published by the Free Software Foundation.
NagVis is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
nagvis-nagvis-1.9.47/docs/en_US/after_installation.html 0000664 0000000 0000000 00000011024 15014016017 0023072 0 ustar 00root root 0000000 0000000NagVis contains several demo maps on initial installation. There is also a rotation defined to give you an example of the features of NagVis. Certainly Nagvis has a lot more features than we can show you with this demo configurations. So you should read the documentation and be creative.
If you are familiar with NagVis you can delete these demonstration maps and rotation without problems.
NagVis is based on several configuration files. The main configuration file stores the basic and global configuration options.
The map specific configuration options are stored in map configuration files located in etc/maps
.
A special type of maps are the automaps. Take a look at the automap configuration documentation for details.
The whole NagVis configuration can be changed using the web based configuration dialogs.
By default NagVis uses an internal user and permission database (SQLite) for handling authentication and authorisation. Nagvis uses a role based permission system. After installation there are two default users defined:
The following roles with these permissions are available:
These default users and roles should be sufficient for the beginning. You may delete these users and roles but please be aware not to delete the last administrative user.
During installation
Please be sure that you have a current PHP version, that all required modules are installed for NagVis and the backend you want to use and that GraphViz is already there. Some PHP modules might already be included in the base package (please use "php -m" to check).
Please check install.log
for errors.
After installation
Please check the Apache logs for "permission denied" messages. It is most likely that SElinux is active. Please disable it (setenforce 0) or allow NagVis to access the files.
Please check the Apache logs for "memory limit exceeded" messages. It is most likely that the memory settings in php.ini have to be increased. Please restart your WebServer afterwards.
Please take a look at the doc section of the official website (namely "FAQ" and "Often reported errors") as well. If this doesn't help then read on.
HELP
You might seek help at the official NagVis website or use the monitoring portal which offers a board for NagVis questions.
In any case please provide at LEAST information about
grep "^[^;|^$]" <config file>
(if you have a configuration related issue). Replace "<config file>" by the name of the config file which might be in errorIn the versions prior to 1.5 NagVis didn't care much about the authentication and authorisation. In most environments NagVis used the basic authentication provided by Nagios. This was a side effect of that NagVis was placed in the nagios/share
directory.
In NagVis 1.5 the default installation directory has been moved to an own base directory. With this step a new Authentication and Authorisation mechanism has been created. The main focus of this concept is to be modular and flexible.
The AA has been splitted up in three module bases: LogonDialogs, Authentication, Authorisation. All modules can be changed without affecting the others.
By default NagVis uses a mixed logon information request mode for logging on users and a SQLite database for storing users, passwords and permissions. Therefor NagVis uses the LogonMixed module which uses LogonEnv and LogonDialog in the background. The LogonMixed module tries to gather the logon user name from the webserver environment. This means NagVis trusts the webserver authentication if one is used. And if there is none it displays the LogonDialog for interactive login using the HTML logon dialog.
On delivery there are only the above authentication and authorisation modules available. Having such a modular structure it should be easy to create LDAP, MySQL, file based authentication and authorisation mechanism.
nagvis-nagvis-1.9.47/docs/en_US/auth_modules.html 0000664 0000000 0000000 00000000000 15014016017 0021671 0 ustar 00root root 0000000 0000000 nagvis-nagvis-1.9.47/docs/en_US/auth_old_style.html 0000664 0000000 0000000 00000003237 15014016017 0022236 0 ustar 00root root 0000000 0000000In the versions prior to 1.5 NagVis didn't care much about the authentication
and authorisation. In most environments NagVis used the basic authentication
provided by Nagios. This was a side effect of that NagVis was placed in the
nagios/share
directory.
In NagVis 1.5 the default installation directory has been moved to an own base directory. With this step a new Authentication and Authorisation mechanism has been created. The main focus of this concept is to be modular and flexible.
If you really like to use the basic authentication provided by Nagios you may use the LogonMixed (default) or LogonEnv module to set up a trusted authentication. The only difference is that the LogonMixed falls back to the HTML form LogonDialog when no user is given by the webserver while LogonEnv simply shows an access denied message.
To enable this simply set the following options in the
[global]
section of the NagVis main configuration file:
logonmodule="LogonEnv" logonenvvar="REMOTE_USER" logonenvcreateuser="1"
These lines advise NagVis to use the LogonEnv module which reads the authenticated user from an environment variable. The second parameter tells the LogonEnv module which variable to use for reading the users name. The third option tells the LogonEnv module to create unknown users in the NagVis AA database.
nagvis-nagvis-1.9.47/docs/en_US/authorisation_groups.html 0000664 0000000 0000000 00000004516 15014016017 0023510 0 ustar 00root root 0000000 0000000NagVis uses an own user, role and permission management in current versions. However, since the authorisation is modularized, it is possible to use alernative authorisation modules.
Since NagVis 1.8b1 there is a new auhthorisation module shipped with NagVis named CoreAuthorisationModGroups. It makes use of the contact groups defined in your monitoring core and a mapping table, which is NagVis specific, to gather the permissions of the users within NagVis. Please note that this new feature can only be used when using the livestatus backend.
To use this module each user which should get access to NagVis has to have a contact with a matching name defined in your monitoring core. You also need to assign at least one contact group to this contact.
When you have defined your contacts, contact groups and the memberships within your core, you can start creating the mapping table which maps the contact group names to NagVis permissions.
The mapping table is configured using a JSON construct within the file nagvis/etc/perms.db. This JSON contruct is an object which uses the contact group names as keys which each refer to a nested object which contains the permissions assigned to each member of this group.
Here you can see the contents of the example configuration:
{ "admins": { "admin": 1 }, "first_level_support": { "view": [ "*" ] }, "power_users": { "view": [ "*" ], "edit": [ "*" ] }, "oracle_admins": { "view": [ "oracle_servers" ], "edit": [ "oracle_servers" ] } }
In the example above all members of the contact group "admins" get full access to NagVis including all permissions. The contact group named "first_level_support" gets view access to all maps defined in NagVis. The contact group named "power_users" gets view and edit permissions to all maps. The contact group named "oracle_admins" is allowed to view and edit the map named "oracle_servers".
nagvis-nagvis-1.9.47/docs/en_US/authorisation_modules.html 0000664 0000000 0000000 00000000000 15014016017 0023621 0 ustar 00root root 0000000 0000000 nagvis-nagvis-1.9.47/docs/en_US/authorisation_roles_perms.html 0000664 0000000 0000000 00000011436 15014016017 0024522 0 ustar 00root root 0000000 0000000Since release 1.5 NagVis contains a very detailed permission management. It is a role based concept where users can be assigned to one or several roles while the roles have permissions assigned.
The permissions of the different roles of a user are summarised and control the actions the user is able to perform.
In a fresh installation there are four roles defined:
These default roles should be sufficient in the beginning. You may delete these users and roles but please be aware NOT to delete the last administrative user and role.
It is possible to create new roles for customising the permissions of users and groups of users.
For example it is easy to create a role for all SAP administrators which then can only access the SAP related maps.
The permissions are hardcoded in NagVis. A single permission consists of three elements:
Each of those three elements can be set by a dedicated name or alternatively by a wildcard "*" which then matches all modules, actions or objects.
Here is a list of all available permissions in NagVis:
Module | Action | Object | Description |
---|---|---|---|
* | * | * | Grants full access to NagVis. No other permissions are needed. |
Auth | logout | * | Allows a user to logout from NagVis. |
AutoMap | add | * | Create a new automap. |
AutoMap | delete | * | Delete all automaps. |
AutoMap | edit | * | Edit all automaps. |
AutoMap | view | * | View all automaps. |
AutoMap | delete | <Name> | Delete a specific automap. |
AutoMap | edit | <Name> | Edit a specific automap. |
AutoMap | view | <Name> | View a specific automap. |
ChangePassword | change | * | Allows a user to change one's own password. |
General | * | * | |
MainCfg | edit | * | |
Map | add | * | |
Map | delete | * | |
Map | edit | * | |
Map | view | * | |
Map | delete | <Name> | Delete a specific map. |
Map | edit | <Name> | Edit a specific map. |
Map | view | <Name> | View a specific map. |
Overview | view | * | |
RoleMgmt | manage | * | |
Rotation | view | * | |
Rotation | view | <Name> | View a specific rotation. |
Search | view | * | Search objects on maps and automaps. |
UserMgmt | manage | * |
Parameter | Default | Description |
---|---|---|
show | The name of the automap. Since NagVis 1.5 different automap configuration files can be defined. The automap to view needs to be set here. | |
backend_id | default backend | The backend-id of the backend to fetch the objects from. For details see the [backend_*] section in the Main Configuration |
root | see root object definition | This is the name of the root object. It is not essential to set the host here. There are some more ways to tell the root object. For details see the root object definition chapter on this page. |
child_layers | 2 | Maximum layers of child hosts to be displayed. |
parent_layers | 0 | Maximum layers of parent hosts to be displayed. |
render_mode | undirected | Set the render mode of the map. For details see available render modes |
width | 1024 | width of the automap in pixels |
height | 786 | height of the automap in pixels |
ignore_hosts | none | comma separated list of hosts (including children) not to display |
filter_by_state | 0 | Set to 1 to enable the "problem automap" mode. When it is set to 1 it will exclude all branches which have only OK/UP hosts. This will result in a "problem automap" which only shows up a tree where each branch has at least one problem. |
filter_by_id | Exclude specified object_ids, is mostly used internal (new in 1.7) | |
filter_group | none | Provide a hostgroup name. Only hosts in this hostgroup will be shown on the map. |
search | none | Search for a map object on map load. Matching objects will be highlighted. |
rankdir | LR | Configure direction of directed automaps, can be set to TB (Top/Bottom) and LR (Left/Right) (new in 1.7) |
rotation | none | Rotate in the given rotation pool when the map is a step in the pool. |
header_menu | none | Enable/Disable the header menu. To be specified as integer (1/0). Overrides the configuration. |
hover_menu | none | Enable/Disable the hover menus. To be specified as integer (1/0). Overrides the configuration. |
context_menu | none | Enable/Disable the context menus. To be specified as integer (1/0). Overrides the configuration. |
margin | 50 | Sets the free area on the border of the automap graph. Has to be specified in pixels. |
overlap | true | Configure collision handling of objects (take a look at the graphviz docs for explanations of the values) (new in 1.7) |
root
.defaultroot
option can be set in the [automap]
section.Mode | Example image |
---|---|
directed | ![]() |
undirected | ![]() |
radial | |
circular | |
undirected2 |
Since NagVis 1.5 it is possible to export the current automap view as a classic NagVis map. Exporting automaps to classic maps you get the advantages of both worlds.
You can start with the automap to get all the object positioned on your maps using the automap render modes. Once you finished the rendering you can export the automap including the generated background image to a regular map using the "Export to map" which can be found in the "Actions" submenu in your header menu.
Using the exported map you can add design elements as you like and customize your layout according to your needs.
A map can be exported multiple times to the same target map but it will overwrite all changes you made to the target map before. You can only overwrite maps you have edit permissions on.
A classic map can not be turned into an automap.
The URLs of the host objects are used for identifying the host objects during automap rendering. Especially the "host=" parameter is important. When this parameter is missing in the host URLs the object positions can not be gathered.
By default this information should not be of interest to you. But when you customize the host URLs in your NagVis installation it is important to know that your custom URL needs to have the "host=" parameter set to the hostname of the object to be able to use the hosts on the automap.
nagvis-nagvis-1.9.47/docs/en_US/automap_config_format.html 0000664 0000000 0000000 00000025207 15014016017 0023563 0 ustar 00root root 0000000 0000000The NagVis automap configuration format is equal to the map configuration format with small differences in the available parameters.
The first definition in every config file should be of the special type "global". Options which are defined at this paragraph are valid for the whole map and are getting inherited to other types defined later.
Example with all options which have to be set:
define global { map_image=lan.png }
Value | Default | Description |
---|---|---|
alias | map_name | The alias is the label for each map. If it is defined it is shown everywhere in NagVis frontend. |
backend_id | inherited (nagvis.ini.php) | Backend-ID defined in Main Configuration file where NagVis should search for the object states. If this parameter is not given, the Backend defined as "defaultbackend" at the Main Configuration file is used. |
background_color | inherited (nagvis.ini.php) | Background colour of this map. If this is not set backgroundcolor from Main Configuration file is taken. |
context_menu | inherited (nagvis.ini.php) | Enable/Disable the context menu on your map objects. |
context_template | inherited (nagvis.ini.php) | Default context template to be used on this map |
inherited (nagvis.ini.php) | &childLayers=2 . Valid options can be found here. |
|
event_background | inherited (nagvis.ini.php) | Enable/Disable changing background colour on state changes (Configured colour is shown when summary state is PENDING, OK or UP). |
event_highlight | inherited (nagvis.ini.php) | Enable/Disable highlighting of the state changing object by adding a flashing border. |
event_highlight_duration | inherited (nagvis.ini.php) | Set the highlight duration in milliseconds |
event_highlight_interval | inherited (nagvis.ini.php) | Set the highlight interval in milliseconds |
event_log | inherited (nagvis.ini.php) | Enable/Disable the eventlog in the new javascript frontend. The eventlog keeps track of important actions and information. |
event_log_level | inherited (nagvis.ini.php) | Loglevel of the eventlog (Available: debug, info, warning, critical). |
event_log_height | inherited (nagvis.ini.php) | Height of the javascript eventlog in px |
event_log_hidden | inherited (nagvis.ini.php) | Hide/Show the eventlog on map loading |
event_scroll | inherited (nagvis.ini.php) | Enable/Disable scrolling to the icon which changed the state when the icon is out of the visible scope. |
event_sound | inherited (nagvis.ini.php) | Enable/Disable sound signals on state changes. |
header_menu | inherited (nagvis.ini.php) | Enable/Disable the header menu |
header_template | inherited (nagvis.ini.php) | header template to be used on ths map |
hover_menu | inherited (nagvis.ini.php) | Enable/Disable the hover menu |
hover_delay | inherited (nagvis.ini.php) | Delay of hover menu appearance in seconds |
hover_template | inherited (nagvis.ini.php) | Default hover template to be used on this map |
hover_childs_show | inherited (nagvis.ini.php) | Enable/Disable displaying child objects |
hover_childs_limit | inherited (nagvis.ini.php) | Number of maximum children to be displayed. Set to -1 to disable the limit. |
hover_childs_order | inherited (nagvis.ini.php) | Order direction of child objects |
hover_childs_sort | inherited (nagvis.ini.php) | Sort method of child objects |
iconset | inherited (nagvis.ini.php) | Iconset to use as default for all objects placed on the map. Can be overwritten on a per object base. In the example "std_small" is used which means an OK state will be displayed using "std_small_ok.png", a CRITICAL state will be displayed by using "std_small_critical.png" and so on. |
in_maintenance | 0 | Enable/Disable the maintenance mode of this map. If a map is in maintenance mode only a message gets displayed instead of the map. |
label_show | 0 | Enable/Disable labels for the maps objects |
label_x | -20 | Default x-position of the labels in px (with prefix + or - relative to the upper left corner of the icons, otherwise absolute position) |
label_y | +20 | Default y-position of the labels in px (with prefix + or - relative to the upper left corner of the icons, otherwise absolute position) |
label_width | auto | Default width of the labels in px |
label_background | transparent | Default background colour of the labels. The colour should be given in hexcode. Can also be "transparent". |
label_border | #000000 | Default border colour of the labels. The colour should be given in hexcode. Can also be "transparent". |
label_style | Custom styling for the label text. To be given like HTML style attribute contents. E.g. font-family:sans;font-weight:bold; |
|
line_type | Specifies the type of line when view_type=line. Valid values are: "11" for lines with one arrow at the end of a line. "10" for lines with two arrows pointing to each other in the middle of the line. "12" for plain lines without arrow. |
|
line_width | 3 | This defines the width of the line in px when this object is being displayed as line. |
only_hard_states | inherited (nagvis.ini.php) | Sets whether soft states should be ignored. Default setting is 0. |
recognize_services | inherited (nagvis.ini.php) | Sets whether the states of the services on hosts, hostgroup objects should be recognised. If this is not given in the config it's set to 1. |
show_in_lists | inherited (nagvis.ini.php) | Show the maps in lists (dropdowns, index page, ...) |
stylesheet | inherited (nagvis.ini.php) | Filename of the custom stylesheet to use on the maps (The file needs to be located in the share/nagvis/styles directory) |
url_target | _self | Target of the Icon link, this option adapts <a target=""> (_self is same window) |
The Checkmk Business Intelligence (BI) Backend is used to connect NagVis directly with the aggregations configured within Checkmk BI.
Checkmk BI offers a webservice which is called by HTTP GET requests and responds with JSON objects.
This backend is a special one compared to the other backends which handle Nagios status information 1:1. This backend only handles Checkmk BI aggregations as dedicated object.
The backend only provides information for objects of the type aggr
, which
has been introduced to represent aggregation objects.
The aggregations objects link (left click on icon) are automatically set by the mkbi
backend to point to the Checkmk Web-GUI, except when the url
parameter
of the aggr object is configured to point to another map
(e.g. [htmlbase]/index.php?mod=Map&act=view&show=bi-webshop-details
).
You can use the following parameters to configure the Checkmk BI backend:
Value | Default | Description |
---|---|---|
base_url | http://localhost/[site_id]/check_mk/ | The full base URL to the view.py script which is part of Checkmk.
It serves the AJAX-API which the backend connects to. This URL must be reachable
from the host NagVis is running on. |
site_internal_auth | 0 | Use the so called site internal authentication introduced with Checkmk 2.4. The site internal secret is automatically derived from the Checkmk sites environment. |
auth_user | User to use for authentication when accessing the base_url . It
has to be created within Checkmk as "automation" user in order to
configure a backend which is allowed to retrieve Checkmk BI states.
Used for the automation authentication together with auth_secret or auth_secret_file.
This was the authentication mechanism until Checkmk 2.3.
|
|
auth_secret | The authentication secret configured within Checkmk for the given user. | |
auth_secret_file | Read the authentication secret configured within Checkmk for the given user from this path. | |
verify_peer | 1 | New in 1.9.34: Whether to verify the certificate the HTTPS server is providing. |
ca_path | New in 1.9.34: Location of Certificate Authority file on local filesystem which should be used with the verify_peer context option to authenticate the identity of the remote peer. | |
timeout | 5 | New in 1.9b11: This option controls the request timeout of the HTTP requests to Checkmk BI. |
There are also some general backend parameters. You can read about them in main configuration format description.
nagvis-nagvis-1.9.47/docs/en_US/backend_mklivestatus.html 0000664 0000000 0000000 00000010177 15014016017 0023422 0 ustar 00root root 0000000 0000000MKLivestatus is a very simple and smart Nagios eventbroker module. Livestatus is concepted and tuned to reduce disk, memory and cpu load caused by live-data processing on the Nagios system. Just as NDO, Livestatus makes use of the Nagios Event Broker API and loads a binary module into the Nagios process. But other than the NDO, Livestatus does not actively write out data e.g. to the disk. Instead, it opens a socket for external applications to connect to and fetches the current status information from Nagios. For details about the new data access provider take a look at the official documentation.
Since the first NagVis 1.5 release the mklivestatus backend is included on delivery. It performs much better than all other existing backends and comes with less overhead than other backends. No additional database is needed to make this backend work.
Value | Default | Description |
---|---|---|
socket | unix:/usr/local/nagios/var/rw/live | The socket to connect to can be a local unix socket or a tcp socket. You have to define the type at the beginning of the string. Set "unix:" for unix sockets or "tcp:" for tcp sockets. New in 1.9.16:Since Checkmk 1.6.0 it is possible to encrypt the Livestatus channel using TLS. To connnect to such a channel use "tcp-tls:". In case of the unix socket you need to specify the path of the livestatus unix socket to connect to. When using a tcp socket you have to enter a host address and a tcp port using the following scheme: <host>:<port>. The host address can be an IP address or an FQDN. |
timeout | 5 | New in 1.6.4: This option controls the connect timeout of the livestatus socket. This is just a fallback. To prevent timeouts when accessing remote sites you really should configure a statushost for the backend. For details take a look at the general backend parameters documented in the backend section of the main configuration format description. |
verify_tls_peer | 1 | New in 1.9.16: Only relevant when you connect to a Livestatus TLS encrypted socket. This can be used to turn off the peer certificate verification. In case it is enabled, you will have to set the verify_tls_ca_path option. |
verify_tls_ca_path | New in 1.9.16: Configure an absolute path that points to a CA chain file which is then used to verify the certificate of the Livestatus TLS server. You can, for example in Checkmk sites, point it to the, "Trusted certificate authorities file of Checkmk (/omd/sites/[site-id]/var/ssl/ca-certificates.crt) to use the same trust configuration in NagVis and Checkmk. |
There are also some general parameters. You can read about them in main configuration format description.
nagvis-nagvis-1.9.47/docs/en_US/backend_nagiosbp.html 0000664 0000000 0000000 00000006633 15014016017 0022473 0 ustar 00root root 0000000 0000000The NagiosBP backend is used to connect NagVis directly with the Nagios Business Process addons which are used to build business process aggregations out of Nagios status information.
NagiosBP offers a webservice which is called by HTTP GET requests and responds with JSON objects. The documentation for this JSON API can be found here.
This backend is a special one compared to the other backends which handle Nagios status information 1:1. This backend mainly handles business processes but also Nagios service state information. As result of this fact the backend needs to perform some sort of translation to create Nagios-like objects from the business processes.
During design of this backend it turned out that the business processes should be mapped to servicegroup objects. Out of this decision we have two results:
Another special property of the NagiosBP backend is the fact that NagVis has not to calculate the summary (aggregated) states using its own algorithms. Instead of this the NagiosBP backend sets the states/outputs of the NagiosBP servicegroups using the state information provided by NagiosBP.
The servicegroup links (left click on icon) are automatically set by the NagiosBP
backend to point to the NagiosBP GUI, except when the url
parameter
of the servicegroup is configured to point to another map
(e.g. [htmlbase]/index.php?mod=Map&act=view&show=bp-webshop-details
).
You can use the following parameters to configure the NagiosBP backend:
Value | Default | Description |
---|---|---|
base_url | http://localhost/nagios/cgi-bin/nagios-bp.cgi | The full URL to the nagios-bp.cgi script which is part of NagiosBP.
It serves the AJAX-API which the backend connects to. This URL must be reachable
from the host NagVis is running on. |
auth_user | Optional user to use for using as basic auth user to access the base_url . |
|
auth_pass | Optional password to use for using as basic auth password to access the base_url . |
There are also some general backend parameters. You can read about them in main configuration format description.
nagvis-nagvis-1.9.47/docs/en_US/backend_ndomy.html 0000664 0000000 0000000 00000004446 15014016017 0022017 0 ustar 00root root 0000000 0000000The ndo2db MySQL backend, in short ndomy backend, is used to fetch Nagios information like status and configuration data via a MySQL database. The Nagios addon called ndoutils stores all information which are present in a running Nagios in a MySQL database. This database is being queried by the NagVis ndomy backend.
You can use the following parameters to configure an ndomy backend:
Value | Default | Description |
---|---|---|
dbhost | localhost | Hostname of the NDO Database |
dbport | 3306 | Port of the NDO Database |
dbname | db_nagios | Name of the NDO Database |
dbuser | root | Username for Database Access (only needs read permissions) |
dbpass | root | Password for Database Access (only needs read permissions) |
dbprefix | nagios_ | Prefix of the tables in NDO Database (like defined in ndo2db.cfg) |
dbinstancename | default | Name of the Nagios instance in NDO Database (like defined in ndomod.cfg) |
maxtimewithoutupdate | 180 | Maximum delay in seconds after last update in NDO. NagVis will report Nagios is not running if the delay is reached |
There are also some general parameters. You can read about them in main configuration format description.
Note: The above should be possible with the IDOUtils of Icinga as well so replace "NDO", "ndo2db.cfg", and "ndomod.cfg" with "IDO", ido2db.cfg", and "idomod.cfg", respectively.
nagvis-nagvis-1.9.47/docs/en_US/backend_pgsql.html 0000664 0000000 0000000 00000003731 15014016017 0022013 0 ustar 00root root 0000000 0000000The PostgreSQL backend, in short pgsl backend, is used to fetch Nagios information like status and configuration data via a PostgreSQL database as may be used by e.g. Icinga 2.
You can use the following parameters to configure a pgsql backend:
Value | Default | Description |
---|---|---|
dbhost | localhost | Hostname of the PostgreSQL Database |
dbport | 3306 | Port of the PostgreSQL Database |
dbname | db_nagios | Name of the PostgreSQL Database |
dbuser | root | Username for Database Access (only needs read permissions) |
dbpass | root | Password for Database Access (only needs read permissions) |
dbprefix | nagios_ | Prefix of the tables in the PostgreSQL Database |
dbinstancename | default | Name of the Nagios instance in the PostgreSQL Database |
maxtimewithoutupdate | 180 | Maximum delay in seconds after last update in the PostgreSQL database. NagVis will report Nagios is not running if the delay is reached |
There are also some general parameters. You can read about them in main configuration format description.
nagvis-nagvis-1.9.47/docs/en_US/backends.html 0000664 0000000 0000000 00000004142 15014016017 0020765 0 ustar 00root root 0000000 0000000The NagVis code is separated into several layers. One of these layers is the "data layer". The data layer is used to handle requests for information from third party sources like the socket of MKLivestatus. We call this layer "backend" in general. There are some components inside NagVis to manage these backends which act as the glue between the single backends and the other layers.
At the moment there are a few backends delivered with the NagVis core packages: the most important ones are the mklivestatus and ndomy backends. All backend configuration parameters are described in detail on their own pages.
The ndomy backend has been the default backend from NagVis 1.0 to NagVis 1.5. It fetches Nagios information from the NDO MySQL database. Since NagVis 1.5 the default backend has been switched to MKLivestatus backend.
In NagVis 1.9, the pgsql backend has been added to fetch the Nagios information from a PostgreSQL database as used by e.g. Icinga 2.
The backends are defined in the main configuration file. See main configuration format description on how to define backends.
nagvis-nagvis-1.9.47/docs/en_US/changelog.html 0000664 0000000 0000000 00000000635 15014016017 0021145 0 ustar 00root root 0000000 0000000The current changelogs are linked from the NagVis download page.
nagvis-nagvis-1.9.47/docs/en_US/context_templates.html 0000664 0000000 0000000 00000014505 15014016017 0022761 0 ustar 00root root 0000000 0000000Context templates are html files with some macros in them. These files can be used as context menus (right click menus) for the objects on the maps.
The context templates are located in share/userfiles/templates/
relative to the nagvis root directory. The templates are named like this: <name>.context.html
. It is possible to add a css file to the template, the name has to be: <name>.context.css
.
There are some so called macros available in context menus of all object types and some which are only available for some special objects. All standard macros are listed below.
The following macros are available in hover menus of all object types:
Macro | Description |
---|---|
General | |
[obj_id] | ID of object in JavaScript. Needed to locate the object specific parts e.g. to schedule a manual update of the state information. |
[type] | Type of the object |
[name] | Name of the object (Hostname, Hostgroupname, Servicegroupname, Mapname,...) |
[backend_id] | Represents the backend_id of the used backend for this object. |
[custom_1] | Represents the first custom macro which can be defined per backend. Might be useful to set backend individual URLs. |
[custom_2] | Second custom macro. Same as above. |
[custom_3] | Third custom macro. Same as above. |
[map_name] | Name of the current map/automap. |
Language macros | |
[lang_refresh_status] | Label for refreshing the status of the object in frontend. |
[lang_schedule_downtime] | Label for scheduling a downtime in Nagios. |
[lang_reschedule_next_check] | Label for re-scheduling the next check of the object in Nagios. |
[lang_connect_by_ssh] | Label for connecting a host by ssh. |
Paths | |
[html_base] | Absolute URL to HTML-Base (Default: /nagvis) |
[html_cgi] | Absolute URL to the Nagios CGIs. Using object specific value. Depends on the used backend. If no backend specific value set the default value will be used. (Default: /nagios/cgi-bin) |
[html_templates] | Path to context templates directory (Default: /nagvis/userfiles/templates) |
[html_template_images] | Path to context template images directory (Default: /nagvis/userfiles/images/templates) |
There are macros for context templates of a specified type. These macros should be surrounded by section macros. The section macros define that the included code will be removed if the hover template is not parsed for this type.
For example a section macro for host macros looks like this:
<!-- BEGIN host -->.+?<!-- END host -->
Below you can find a full list of the special macros.
Macro | Description |
---|---|
[address] | Address of the host configured in Nagios |
[pnp_hostname] | Hostname with replaced blanks for links to PNP |
Macro | Description |
---|---|
[service_description] | Service description in Nagios |
[pnp_service_description] | Service description with replaced blanks for links to PNP |
<!-- BEGIN hostgroup -->
and <!-- BEGIN servicegroup -->
exist to make special template code for hostgroup and servicegroup context menus possible. Both don't bring any
special object specific macros with them.
There are some other special section macros. For example to show parts of the template only for line objects:
<!-- BEGIN line -->This is only shown on line objects<!-- BEGIN servicegroup -->
Section | Description |
---|---|
line | Only show this for line objects. |
stateful | Only show this for stateful objects. |
not_automap | Only show this for non automap views (regular maps). |
locked | Only show for locked objects. |
unlocked | Only show for unlocked objects. |
permitted_edit | Only show when the user is able to edit the map. |
permitted_perform | Only show when the user is able to perform actions. |
action_* | Only show when this action is registered for this object. |
The NagVis Dynamic Map source was introducted in NagVis 1.8. It has been created to make it easier to create schematic maps which contain equal kinds of objects.
For example if you like to have one single map which contains several host objects, maybe all hosts
which name starts with srv-
. Without the dynamic maps you would always have to add a host
object to your map if you add a new host to your monitoring and also remove it if some of those hosts
is being removed.
Using the dynamic maps you can now compute your rule definitions once and every time the monitoring configuration changes, the map checks itselfs if some host needs to be added, removed or repositioned.
Please Note: This feature is only available when you are using the livestatus backend (at the moment).You could simply create a new map in the NagVis user interface, configure it to use the source
dynmap
and then change all the dynmap_*
options to fit your needs.
An alternative way is to create the map configuration by hand. Browse to the map config directory
and create a new file, for example named test-dynmap.cfg
.
Now add the necessary options to the map configuration file you just created:
global { sources=dynmap alias=Test Dynmap iconset=std_medium backend_id=demo # Dynmap Parameters dynmap_object_types=host dynmap_object_filter=Filter: name ~ srv-.*\n }
The sources=dynmap
line tells the map to use the dynmap source for altering the
map configuration.
The dynmap_object_types=host
line tells the dynmap source to gather objects of the
type host to be shown on the map.
The dynmap_object_filter=Filter: name ~ srv-.*\n
line contains one or several livestatus
filter definitions to be used to filter the map objects.
The dynmap uses the following map configuration attributes in the global section of the maps.
Parameter | Default | Description |
---|---|---|
dynmap_object_types | The type of objects to be shown on this map, either host, service, hostgroup or servicegroup. | |
dynmap_object_filter | One or several livestatus filter definitions, seperated by "\n". | |
dynmap_init_x | 20 | The left px coordinate of the object grid. |
dynmap_init_y | 700 | The top px coordinate of the object grid |
dynmap_offset_x | 30 | The offset in pixel to seperate the objects of a row horizontally. |
dynmap_offset_y | 30 | The offset in pixel to seperate the lines of objects with. |
dynmap_per_row | 30 | Objects to add in the grid per row. The Y offset is applied once a row reaches this number. |
dynmap_sort | Sort method to use. Can be a for alphabetically order (default), s to
sort objects by state or k to keep the order of the backend. |
|
dynmap_order | asc | Order of the objects (Available: asc/desc) |
Please note: This document still contains valid information, however today, since version 1.7.6, it is possible to configure custom actions in the main configuration.
NagVis 1.4 introduces a powerful new feature called context menus. The
context menus basically are right-click menus on the status icons. You can
customize these menus by simply editing some template files. The template
files are simple html files including some macros which are replaced during
render time in NagVis.
The context menus give you the ability to improve your administrative workflow with the monitoring information dramatically. Imagine you have a NagVis map as the primary user interface to gather status information about your systems and even as a base to control your systems. Imagine you can view status information from NagVis and simply connect to the problematic systems by ssh or via terminal session by just two clicks. It is also possible to store some default recover jobs in scripts or anything else.
Take a look at this guide to get some ideas of the power of this new feature.
This is a quick how-to to add a "connect by ssh" option to the NagVis hosts context menu. Most of the changes have to be made on the client browsers to get it handle ssh connections. In this guide I am using the firefox on Ubuntu. It is no problem to get this work on other systems like Windows.
cd /usr/local/nagvis cp share/userfiles/templates/default.context.html share/userfiles/templates/default-ssh.context.htmlNow add a line to the host specific macro section like follows
<li><a href="ssh://[address]">[lang_connect_by_ssh]</a></li>The template is finished.
context_menu=true context_template=default-sshYou can set this option in the global section of a map, in a host object or even a template which is used in a host object.
about:config
in your firefox. Add some new options:
Name: network.protocol-handler.app.ssh Type: String Value: /usr/local/bin/ssh-connect-handler
Name: network.protocol-handler.expose.ssh Type: Boolean Value: true
Name: network.protocol-handler.external.ssh Type: Boolean Value: true
Name: network.protocol-handler.warn-external.ssh Type: Boolean Value: false
If you are using Firefox 3.5 or above you only need to set the following options:
String: network.protocol-handler.app.ssh = /usr/local/bin/ssh-connect-handler Boolean: network.protocol-handler.expose.ssh = false
/usr/local/bin/ssh-connect-handler
.
#!/bin/bash xterm -e ssh ${1#ssh:\/\/*}You need to make this script executable.
chmod +x /usr/local/bin/ssh-connect-handler
If you need explicit root login and like to use root login this might be a better script for you:
#!/bin/bash # # /usr/local/bin/ssh-connect-handler gnome-terminal --geometry=78x10 -e "ssh root@${1#ssh:\/\/*}"
ssh://<test-host>
in your browser address bar and press enter.
If an xterm with the ssh session opens everything is ok here.
With this knowledge you are ready to configure NagVis to be the core of your daily administrative and monitoring tasks. Be creative now!
We like you to give us some feedback on this feature and how you use it.
nagvis-nagvis-1.9.47/docs/en_US/extending/iconsets.html 0000664 0000000 0000000 00000020732 15014016017 0023032 0 ustar 00root root 0000000 0000000Your boss is coming in and telling you that a technician needs a map with more than 250 hosts clearly laid out. You think: “Hey, that’s not possible, with a full description for every host!” The font in the background image is not the problem, but the std_small-iconset from NagVis is too big for such a request.
Build your own iconset.
A complete iconset consists of a number of files. These files are png, svg, gif or jpg images which are named like this:
Filename | Description |
---|---|
<set>_critical.png | Critical state |
<set>_critical_ack.png | Acknowledged critical state |
<set>_critical_dt.png | Critical state in downtime |
<set>_critical_stale.png | Stale critical state |
<set>_down.png | Down state (Host) |
<set>_down_ack.png | Acknowledged down state |
<set>_down_dt.png | Down state in downtime |
<set>_down_stale.png | Stale down state |
<set>_error.png | Error while fetching status |
<set>_ok.png | OK state |
<set>_ok_dt.png | OK state in downtime |
<set>_ok_stale.png | Stale ok state |
<set>_pending.png | PENDING state |
<set>_unchecked.png | Unchecked service (pending) |
<set>_unknown.png | Unknown state |
<set>_unknown_ack.png | Acknowledged unknown state |
<set>_unknown_dt.png | Unknown state in downtime |
<set>_unknown_stale.png | Stale unknown state |
<set>_unreachable.png | Unreachable state (Host) |
<set>_unreachable_ack.png | Acknowledged unreachable state |
<set>_unreachable_dt.png | Unreachable state in downtime |
<set>_unreachable_stale.png | Stale unreachable state |
<set>_up.png | Up state (Host) |
<set>_up_dt.png | Up state in downtime |
<set>_up_stale.png | Stale up state |
<set>_warning.png | Warning state |
<set>_warning_ack.png | Acknowledged warning state |
<set>_warning_dt.png | Warning state in downtime |
<set>_warning_stale.png | Stale warning state |
<set>_ok.png
image to list the iconsets,
means there has to be at least a <set>_ok.png
image to have a
choosable iconset.
Almost every graphic art software has the ability to build PNG-files. In this example Photoshop is used to create a smaller version of the std_small iconset called std_mini.
Iconset | Icon size | icon map |
---|---|---|
std_small | 16×16 pixel |
|
mini | 9×9 pixel | ![]() |
To implement the set in your NagVis installation, copy all files to
the iconset folder (share/userfiles/images/iconsets
).
Open one of your maps and add a new host-icon. You should now be able to select std_mini as iconset.
Since NagVis 1.4 the language format has been changed from xml files to gettext language files. The old xml files were much overhead and consumed a lot of runtime to get parsed.
The main benefit of gettext is much better performance. For details about gettext see the official gettext page.
The language files are stored in the language specific subdirectories of nagvis/includes/locale
directory.
The english language file is en_US/LC_MESSAGES/nagvis.mo
.
The files with .po extension are the sources which have to be compiled to .mo files.
By default the following languages are supported in the current NagVis versions:
Your language is not supported by NagVis? No problem! You can easily build your own language file.
If you built a new language file or fixed sth. in existing language files you're welcome to submit the file to us so we can implement it in the next NagVis release or publish it on Nagvis.org.
There is support for replacing given strings with some other values.
An example for a macro is the string [USER]
. This string will be replaced before displaying in NagVis when the language entry supports it.
Default Macros are sth. like HTML-Tags which don't have to be defined by the user. At the moment the following default macros are supported:
Macro | Replaced by |
---|---|
[i] | <i> |
[/i] | </i> |
[b] | <b> |
[/b] | </b> |
Special chars like ä,ö,ü,",',... have to be set as HTML-entities (e.g. )
nagvis-nagvis-1.9.47/docs/en_US/extending/shapes.html 0000664 0000000 0000000 00000002132 15014016017 0022460 0 ustar 00root root 0000000 0000000Since NagVis 1.x you can add "stateless Icons" to your maps, we call them shapes. These icons are completely like the other icons, they just have no state.
A shape is nothing else than a simple image. We recommend to use PNG as format for the shapes.
Almost every graphic art software has the ability to build PNG-files.
The shapes are placed in nagvis/images/shapes
. Just copy them to this directory, then you can use them in your maps.
Open one of your maps and add a new shape-icon. You should now be able to select your own shapes.
nagvis-nagvis-1.9.47/docs/en_US/extending/templates.html 0000664 0000000 0000000 00000003750 15014016017 0023202 0 ustar 00root root 0000000 0000000Since NagVis 1.1x you can add templates to customize the look of header- and hover-menus. You can get some of these templates at the NagVis template download page.
Please note: The directory structure changed between the NagVis version several times. So there may be compatibility problems between the versions.
Unpack the NagVis template in a path of your choice.
tar xvzf NagVis-Template-<name>-<version>.tar.gz
Merge the NagVis-Template directory tree with your NagVis Folder (default /usr/local/nagvis/share/userfiles/templates).
cp -r nagvis /usr/local/nagvis/share/userfiles/templates
Now you should be able to use the new template in NagVis. You only have to configure the maps or objects to use the template.
You can set the header template in the main configuration of NagVis or in the global section of the map configuration. For details see map configuration format description.
You can set the hover template in the main configuration for all your maps, in the global section of a map for all the objects on this map or in each object for having a custom hover menu for special objects. For details see map configuration format description.
nagvis-nagvis-1.9.47/docs/en_US/gadgets.html 0000664 0000000 0000000 00000023750 15014016017 0020637 0 ustar 00root root 0000000 0000000Gadgets are small programs which generate images or HTML code from information which
is provided by NagVis. The main idea is to provide the performance data
of Nagios to these programs for visualizing it as nice graphs or fancy
speedometers, thermometers etc.
share/userfiles/gadgets/
contains some examples, others can be found at Nagvis Exchange[1].
The gadgets can be written in any language which can be interpreted by your webserver. Some options can be PHP, Perl,...
Gadgets are only supported for service objects. An object can be turned into a gadget by setting view_type="gadget" and a valid gadget_url.
NagVis supports gadgets since version 1.4.[1]
Since NagVis 1.6 the gadgets can not only render images. As new option the gadgets can render HTML code which might also contain javascript or any kind of dynamic HTML code.
NagVis 1.4 std_speedometer gadget on test map with enabled label.
The gadgets get their information via a HTTP-Get call from NagVis (if you include share/userfiles/gadgets/gadgets_core.php
it will be placed in two arrays. For more information take a look at the description there).
The following parameters are being passed to the gadgets:
Parameter | Example value | Description | Variable |
---|---|---|---|
name1 | localhost | The name of the host | $aOpts['name1'] |
name2 | Current Load | The service description of the object | $aOpts['name2'] |
scale | 100 | The scale of the gadget | $aOpts['scale'] |
state | OK | The string which represents the current state (OK, WARNING, CRITICAL, UNKNOWN) | $aOpts['state'] |
stateType | HARD | The type of the current state. Can be HARD or SOFT | $aOpts['stateType'] |
ack | 0 | Is set to 1 if the represented object state has been acknowledged | $aOpts['ack'] |
downtime | 0 | Is set to 1 if the represented object state is in a downtime | $aOpts['downtime'] |
perfdata | load1=0.960;5.000;10.000;0; load5=0.570;4.000;6.000;0; load15=0.540;3.000;4.000;0; | The current performance data information provided by Nagios. It's important to have valid performance data here. | $aPerfdata[<index>][<tag>] |
A valid http get on the std_speedometer.php looks like this:
std_speedometer.php?name1=localhost&name2=Current%20Load&state=OK&stateType=HARD&perfdata=load1=0.450;5.000;10.000;0;%20load5=0.260;4.000;6.000;0;%20load15=0.750;3.000;4.000;0;
Please check the parameters view_type
, gadget_url
and gadget_opts
of the service object in the map configuration format description. This is an example of a definition in your map file:
define service { host_name=localhost service_description=root-volume x=50 y=50 view_type=gadget gadget_url=std_bar.php // name of the file in share/userfiles/gadgets/ // gadget_url=[http://localhost/nagvis/userfiles/gadgets/std_bar.php] // valid as well // gadget_scale=200 // default is 100 (percent) // gadget_opts=columns=3 label=1 // gadget dependent }
Using the code shown included in gadgets_core.php two arrays are filled. $aPerfdata contains the performance data. $aOpts contains the options set in gadget_opts.
The best thing is to take a look at the code of the standard gadgets and adapt the core things from there.
You should set a sample perfdata string in the gadget code by writing it to
the variable $sDummyPerfdata. This makes it possible to show the gadget with
dummy data during editing. It's much easier to edit the maps when the gadgets are shown.
Important: The variable needs to be set before the gadgets_core.php is included.
A second example can be found in std_speedometer2.php. In contrast to std_speedometer.php it supports output produced by check_multi. The background will be set to yellow or red if the performance data indicates such a state. The service state is not taken into account. Several options set via gadget_opts
influence the behaviour of the gadget:
Parameter | Example value | Description |
---|---|---|
label | 1 | 1 = Show host name / service description in the upper left corner of the graph; 0 = don't show the information (default) |
current | 1 | 1 = Show the current performance data value (default); 0 = don't show the information |
columns | 5 | Graphs can be arranged in columns. The number of rows is calculated based on the maximum number of performance data items. Default is 3 |
string | pct | The performance data label has to contain the string to be displayed. In case of check_multi output only the last part is examined. Default is an empty string |
NagVis 1.5 std_speedometer2 gadget in normal, warning and critical state
A third example is based on an idea found on Nagvis Exchange. Performance data is shown as a horizontal bar. The last quarter of the graph changes to yellow or red if the performance data indicates a warning or critical value. The status is not the state of the service! That is due to the fact that the data might contain multiple data sources. In many cases not all data sources of a service are found to be in a warning or critical state so you don't want to get false alarms (new in 1.5.7 or git newer than 2010.12.12).
Parameter | Example value | Description |
---|---|---|
label | 1 | 1 = Show host name / service description label in the last quarter of the graph (default); 0 = don't show the information |
current | 1 | 1 = Show the current performance data value (default); 0 = don't show the information |
columns | 5 | Graphs can be arranged in columns. The number of rows is calculated based on the maximum number of performance data items. Default is 3 |
string | pct | The performance data label has to contain the string to be displayed. In case of check_multi output only the last part is examined. Default is an empty string |
threshold | value | Determines if the warning and critical thresholds are shown in percent (default) or integer values |
NagVis 1.5 std_bar gadget in normal, warning and critical state
Note: This gadget uses a TrueType font whose name and location is hard coded within the code (variables $fontDir and $fontName). In case the file isn't found the gadget uses a builtin font. The value of $fontDir changes between distributions so if the font doesn't scale properly please check the setting (it defaults to OpenSuSE, other settings are commented out).
[1] The directory structure changed between NagVis 1.4.x and NagVis 1.5. Gadgets were stored innagvis/nagvis/gadgets
and are now stored in share/userfiles/gadgets
. Gadgets found on NagVis Exchange might use the former structure so you might have to move the files to the new location (e.g. cp -pr <source>/nagvis/nagvis/gadgets/<gadget> <target>/share/userfiles/gadgets/
).
nagvis-nagvis-1.9.47/docs/en_US/geomap.html 0000664 0000000 0000000 00000015223 15014016017 0020465 0 ustar 00root root 0000000 0000000
The NagVis Geomap map source was introduced in NagVis 1.7. It has been developed to get well rendered and scaled overview maps without much work.
The geomap renders several hosts on an Open Street Map powered map which is used as background image.
For the current geomap all you need is a CSV file which tells NagVis the hosts to render and the geo coordinates where the hosts should be positioned at.
Unlike the NagVis Worldmaps, which have been introduced with NagVis 1.9, the geomaps are designed to be static maps without user interaction. You can not zoom in/out and pan like you can on the worldmaps.
There is no special software needed on the NagVis host. But there is one special requirement. To
be able to use this feature, NagVis needs to be able to access the host geomap.nagvis.org
via port 80. NagVis uses a simple HTTP based API to get the map image and the coordinates of that image.
In most cases the NagVis host does not have direct internet access. You can configure the http_proxy
option in the [global]
section of your NagVis main configuration to tell NagVis to use
a proxy such requests. Most proxies require an authentication to control access to the internet.
Please use the option http_proxy_auth
to set the credentials.
NagVis comes with a demo geomap called "demo-geomap". If your NagVis is configured correctly you should see a map of germany with two nodes. One node is showing the host "ham-srv1" in Hamburg. The other host "muc-srv1" is located in Munich.
The geomap is defined using the regular map configuration file "demo-geomap.cfg". The contents look like this:
global { sources=geomap alias=Demo: 4 Geomap parent_map=demo-overview iconset=std_medium backend_id=demo # Geomap Parameters source_type=csv source_file=demo-locations width=800 height=600 }
The sources=geomap
line tells the map to use the geomap source for altering the
map configuration.
The source_type=csv
(new in 1.7.4) line tells the geomap
source to use the CSV file defined in the
source_file=demo-locations
definition located in the etc/geomap
directory
for gathering a list of hosts and coordinates to add to the geomap.
The demo-locations.csv
file contains the following two lines:
ham-srv1;Hamburg Server 1;53.556866;9.994622 muc-srv1;Munich Server1;48.1448353;11.5580067
Each line defines one host to be added to the map. The columns are separated by ;
signs.
The first column contains the host-name, the second an optional alias, the third the LAT coordinate and
the fourth the LONG coordinate.
(starting with git-version as of 2013-03-21): Lines starting with the usual comment characters
(;
, #
, or //
) are treated as comments.
: It is also possible to set source_type=backend
to use the backend set via backend_id
to gather the list of hosts to be shown on the geomap
and their coordinates. This is only possible when using the livestatus backend. It fetches all hosts
from the backend and uses all hosts which have the custom object variables _LAT
and
_LONG
configured. It is possible to filter the fetched hosts by the membership in a host group
by setting the option filter_group
to the name of the host group.
The geomap source uses view parameters for configuration. For details take a look at the modify view dialog which can be opened using the header menu "Actions -> Modify view".
The view parameters can also be given as map configuration attributes in the global section of the maps.
Parameter | Default | Description |
---|---|---|
geomap_type | mapnik | Define the render mode of the geomap. Can be osmarender, mapnik and cycle. |
geomap_zoom | Configure the zoom level of the geomap during map request. Take a look at the OSM zoom documentation for further details. | |
geomap_border | 0.25 | The border to add on each side of the geomap. This value is simply added to the calculated min/max geo coordinates. |
source_type | csv | The type of the datasource used for for fetching the geomap objects. Might be csv
or backend . |
source_file | The name of the CSV file to use as source for rendering the geomap. Is only used when
source_type is set to csv . |
|
width | Defines the width of the geomap in pixels. The maximum size of the geomap is limited by the queried webservice. geomap.nagvis.org supports up to 50 tiles per map which should make 1920x1080 resolutions possible. Please contact us if you need more. | |
height | Defines the height of the geomap in pixels. The maximum size of the geomap is limited by the queried webservice. geomap.nagvis.org supports up to 50 tiles per map which should make 1920x1080 resolutions possible. Please contact us if you need more. |
share/userfiles/templates/pages/
relative to the nagvis root directory. The templates are named like this: *.header.html
.Macro | Description |
---|---|
{$currentMap} (was [current_map]) | Name of the current map (e.g. demo,demo2) |
{$currentMapAlias} (was [current_map_alias]) | Alias of the current map |
{$currentLanguage} (was [current_language]) | String representing the current language (For example en_US). This is needed for link to documentation. |
{$currentUser} | Name of the current user. |
{$mod} | The current Module (Map, AutoMap, Overview, Welcome, ...). |
{$act} | The current Action (view, edit, ...). |
{$bRotation} | Is true when currently viewing a rotation. Otherwise it is False.. |
{$permittedOverview} | Is true when the user is permitted to access the overview page. Otherwise it is False.. |
{$permittedEdit} | Is true when the user is permitted to edit the current map. Otherwise it is False.. |
{$permittedEditAnyMap} | Is true when the user is allowed to edit at least one map. Otherwise it is False.. |
{$permittedChangePassword} | Is true when the user is permitted to change the own password. Otherwise it is False.. |
{$permittedEditMainCfg} | Is true when the user is permitted to edit the main configuration file. Otherwise it is False.. |
{$permittedManageBackgrounds} | Is true when the user is permitted to manage backgrounds. Otherwise it is False.. |
{$permittedManageMaps} | Is true when the user is permitted to manage maps. Otherwise it is False.. |
{$permittedManageShapes} | Is true when the user is permitted to manage shapes. Otherwise it is False.. |
{$permittedUserMgmt} | Is true when the user is permitted to manage user accounts. Otherwise it is False.. |
{$permittedRoleMgmt} | Is true when the user is permitted to manage roles. Otherwise it is False.. |
{$permittedLogout} | Is true when the user is permitted to log out. Otherwise it is False.. |
{$supportedChangePassword} | Is true when the current auth module supports changing passwords. Otherwise it is False.. |
{foreach $maps map} {$map.mapName} {/foreach} |
A list of all maps defined in NagVis. The code between {foreach $maps map} and {/foreach}
is repeated for each map. For an example have a look at share/userfiles/templates/pages/default.header.html .
Within the BEGIN/END-Tags the following macros are available: * {$map.mapName} (Was [map_name]): Name of the map * {$map.mapAlias} (Was [map_alias]): Alias of the map * {$map.permittedEdit}: Is the user permitted to edit this map? |
{foreach $langs lang} {$lang.language} {/foreach} |
A list of all languages available to the users in NagVis. The code between {foreach $langs lang} and {/foreach} is repeated for each language. For an example have a look at share/userfiles/templates/pages/default.header.html .Within the BEGIN/END-Tags the following macros are available: * {$lang.language}: Internal name of the language * {$lang.classUnderline}: Underline the language * {$lang.langLanguageLocated}: Located name of the language. |
{if $viewType == 'Map' || $viewType == 'Automap'} | To be more flexible in the templates we added some sort of if statements. These can be used as in native PHP. For an example have a look at share/userfiles/templates/pages/default.header.html . |
{$pathBase} (was [html_base]) | URL to HTML-Base (/nagvis) |
{$pathImages} (was [html_images]) | URL to HTML-Images (/nagvis/images) |
{$pathHeaderJs} | Path to header specific javascript file |
{$pathTemplates} (was [html_templates]) | Path to header templates (/nagvis/userfiles/templates) |
{$pathTemplateImages} (was [html_template_images]) | Path to header template images (/nagvis/userfiles/images/templates) |
{$langOpen} (was [lang_select_map]) | Label for opening new views |
{$langEditMap} (was [lang_edit_map]) | Label for edit map link |
{$langNeedHelp} (was [lang_need_help]) | Label for help selection |
{$langOnlineDoc} (was [lang_online_doc]) | Label for link to online documentation |
{$langForum} (was [lang_forum]) | Label for link to NagVis forum |
{$langSupportInfo} (was [lang_support_info]) | Label for link to support information |
{$langOverview} (was [lang_overview]) | Label for overview string |
{$langInstance} (was [lang_instance]) | Label for the instance string |
{$langRotationStart} (was [lang_rotation_start]) | Label for starting the map rotation |
{$langRotationStop} (was [lang_rotation_stop]) | Label for stopping the map rotation |
{$langSearch} | Label for searching an object on the map. |
{$langToggleGrid} | Label for enabling/disabling the grid. |
{$langActions} | Label for choosing the available actions. |
{$langUser} | Label for the user. |
{$langLoggedIn} | Label for "Logged in as". |
{$langChangePassword} | Label for changing the user's password. |
{$langUserMgmt} | Label for managing users. |
{$langManageRoles} | Label for managing user roles. |
{$langLogout} | Label for logging out. |
{$langChooseLanguage} | Label for choosing the user's language. |
share/userfiles/templates
relative to the nagvis root directory. The templates are named like this: *.hover.html
.
There are macros which are available in hover menus of all object types and some which are only available for some special objects. All standard macros are listed below.
Macro | Description |
---|---|
General | |
[obj_type] | Type of the object (host, service, hostgroup, ...) |
[obj_name] | Name of the object (hostname, hostgroupname, servicegroupname, mapname,...) |
[obj_alias] | Alias of the object (If no alias is defined it is equal to [obj_name]) |
[obj_display_name] | Display name of the object |
[obj_state] | State of the object (OK, WARNING, CRITICAL,...) |
[obj_summary_state] | Merged state of the object and all child objects (OK, WARNING, CRITICAL, ...) |
[obj_acknowledged] | When the state is acknowledged the macro is replaced with "(Acknowledged)" |
[obj_summary_acknowledged] | When the summary state is acknowledged the macro is replaced with "(Acknowledged)" |
[obj_in_downtime] | When the object is currenty in a downtime this macro is replaced with "(In Downtime)" |
[obj_summary_in_downtime] | When the object is currenty in a downtime this macro is replaced with "(In Downtime)" |
[obj_output] | Output for this object |
[obj_summary_output] | Summary output of the object |
Language macros | |
[lang_name] | Label for the object name |
[lang_child_name] | Label for the child object names |
[lang_alias] | Label for the object alias |
[lang_address] | Label for the object address |
[lang_state] | Label for the object state |
[lang_obj_type] | Label for the object type |
[lang_summary_state] | Label for the summary state |
[lang_output] | Label for the output |
[lang_summary_output] | Label for the summary output |
[lang_overview] | Label for the overview |
[lang_instance] | Label for the NDO instance |
[lang_next_check] | Label for the next check of the object |
[lang_last_check] | Label for the last check of the object |
[lang_current_attempt] | Label for the current attempt |
[lang_last_state_change] | Label for the last state change |
[lang_state_duration] | Label for the state duration |
[lang_service_description] | Label for the service description |
[lang_notes] | Label for the object notes |
Paths | |
[html_base] | Absolute URL to HTML-Base (/nagvis) |
[html_templates] | Path to hover templates directory (/nagvis/userfiles/templates) |
[html_template_images] | Path to hover template images directory (/nagvis/userfiles/images/templates) |
<!-- BEGIN host -->.+?<!-- END host -->
Macro | Description |
---|---|
[obj_backendid] | The backend-id of the objects backend (backend_<*>) |
[obj_backend_instancename] | The NDO instance name of the objects backend |
Macro | Description |
---|---|
[obj_address] | The address of the host object |
[obj_last_check] | The date and time of the last check of this object. The datetime is printed in the defined dateformat. |
[obj_next_check] | The date and time of the next check of this object. The datetime is printed in the defined dateformat. |
[obj_state_type] | The current state type (HARD/SOFT) |
[obj_current_check_attempt] | The number of the current check attempt |
[obj_max_check_attempts] | The number of the maximum check attempts |
[obj_last_state_change] | The date and time of the last state change. The datetime is printed in the defined dateformat. |
[obj_last_hard_state_change] | The date and time of the last hard state change. The datetime is printed in the defined dateformat. |
[obj_state_duration] | The duration of the current state |
[obj_notes] | The configured notes of the host or service objects |
[obj_tags] | When a custom macro is available for this host/service named TAGS, which contains a space separated list of strings, called tags, this list of tags is fully available with this macro. This is available, for example, for all hosts configured with CheckMK. (New in 1.8rc1) |
[obj_taggroup_<group_id>_title] | When using NagVis together with Checkmk (version 1.2.5i6p4 or newer) in an OMD environment, you can use this macro to display tag and taggroup related information in hover menus. This macro can be used to display the title of a taggroup matching the given group_id. (New in 1.8rc1) |
[obj_taggroup_<group_id>_topic] | When using NagVis together with Checkmk (version 1.2.5i6p4 or newer) in an OMD environment, you can use this macro to display tag and taggroup related information in hover menus. This macro can be used to display the tag group topic of the taggroup matching the given group_id. (New in 1.8rc1) |
[obj_taggroup_<group_id>_value] | When using NagVis together with Checkmk (version 1.2.5i6p4 or newer) in an OMD environment, you can use this macro to display tag and taggroup related information in hover menus. This macro can be used to display the raw value, means the choosen tag, of a taggroup matching the given group_id. (New in 1.8rc1) |
[obj_taggroup_<group_id>_value_title] | When using NagVis together with Checkmk (version 1.2.5i6p4 or newer) in an OMD environment, you can use this macro to display tag and taggroup related information in hover menus. This macro can be used to display the title of the choosen tag, of a taggroup matching the given group_id. (New in 1.8rc1) |
Macro | Description |
---|---|
[service_description] | Service description in Nagios |
[pnp_hostname] | Hostname with replaced blanks for links to PNP images |
[pnp_service_description] | Service description with replaced blanks for links to PNP images |
Macro | Description |
---|---|
[pnp_hostname] | Hostname with replaced blanks for links to PNP images |
<!-- BEGIN servicegroup_child --><!-- END servicegroup_child -->
.
Macro | Description |
---|---|
[lang_child_name1] | Label for the host name of the child service |
[obj_name1] | Hostname for the child service |
Since 1.6b2 it is possible to install NagVis into the local/
path of OMD
sites. Please note: This is only recommended for testing purposes
e.g. if you like to test brand new features of new NagVis versions which are not already
included in OMD. We do not recommend using this for productive installations except
you really know what you are doing.
In most cases this is done by doing
su - <sitename>
Get the current NagVis package. The latest release can be found at nagvis.org.
Unpack the archive to a temporary place (for example /tmp) and change to that directory
tar xvzf nagvis-1.8*.tar.gz /tmp cd /tmp/nagvis-1.8*
The OMD site installer is located in the root directory of the NagVis package. The installer has to be made executable before you can use it.
chmod +x omd_install.sh
Now you can execute the installer script.
./omd_install.sh
Confirm the question with y
and wait for the script to complete. It should finish
quickly.
You can remove the sources after installation.
rm -rf /tmp/nagvis-1.8*
Now you should be able to use the new version opening it in the browser with the url
http://<hostname>/<sitename>/nagvisnagvis-nagvis-1.9.47/docs/en_US/installation_instructions.html 0000664 0000000 0000000 00000013442 15014016017 0024543 0 ustar 00root root 0000000 0000000
tar xvzf nagvis-1.8.x.tar.gz
Place the NagVis directory tree somewhere on your system. For most cases
/usr/local/nagvis
is the best place.
mv nagvis /usr/local/nagvis
You should see the following directory listing:
# ls -l /usr/local/nagvis etc LICENCE README share varDON'T move any files or folders inside the NagVis directory (in fact you can move, but in this case you have to change/add some parameters and values in the main config file - if everything is left untouched it should run "out of the box" without changes in the configuration files)
cd /usr/local/nagvisAn example main configuration file can be found in
etc/nagvis.ini.php-sample
.
If you like to change some settings, copy this example to etc/nagvis.ini.php
.
cp etc/nagvis.ini.php-sample etc/nagvis.ini.phpNow you can edit this file with your favourite text editor - I use vi:
vi etc/nagvis.ini.phpMost lines in the freshly copied
nagvis.ini.php
are commented out (starting with a semicolon).
If you want to set different settings, you can simply uncomment the line and change its value.Since NagVis 1.5 it is necessary to configure the webserver to be able to use NagVis.
You will find a sample configuration file in etc/apache2-nagvis.conf-sample
.
Simply copy the file to the conf.d
directory of your webserver. For example this is /etc/apache2/conf.d
.
cp etc/apache2-nagvis.conf-sample /etc/apache2/conf.d/apache2-nagvis.conf
Now you need to open that file and edit it to fit your needs. It is important
to replace the macros @NAGVIS_WEB@
and @NAGVIS_PATH@
.
In this example you need to replace @NAGVIS_WEB@
with /nagvis
and @NAGVIS_PATH@
with /usr/local/nagvis/share
.
This is very important for a neatly working installation.
First check which unix user account is used to run your webserver (in my case it iswwwrun
). If you don't know which user the webserver is running then have a look at the webserver configuration. In case of Apache you can do this by the following command:grep -e 'USER' /etc/apache2/envvarsSuSE/RedHat/Debian (SLES, OpenSuSE, Fedora)
grep -e '^User' /etc/apache2/*.confIf your configuration file is located at another path you should correct this in the command above.
chown wwwrun:www /usr/local/nagvis -R chmod 664 /usr/local/nagvis/etc/nagvis.ini.php chmod 775 /usr/local/nagvis/etc/maps chmod 664 /usr/local/nagvis/etc/maps/* chmod 775 /usr/local/nagvis/etc/geomap chmod 664 /usr/local/nagvis/etc/geomap/* chmod 775 /usr/local/nagvis/share/userfiles/images/maps chmod 664 /usr/local/nagvis/share/userfiles/images/maps/* chmod 775 /usr/local/nagvis/var chmod 664 /usr/local/nagvis/var/* chmod 775 /usr/local/nagvis/var/tmpl/cache chmod 664 /usr/local/nagvis/var/tmpl/cache/*It's possible to set more restrictive permissions on the files but for most setups the example should be fine. Only change them if you know what you are doing!
There are two ways configuring NagVis. The first one is the web based configuration using the NagVis frontend (http://<nagiosserver>/<path-to-NagVis>/
). Take a look
at the header menu for options. To modify existing map objects you need to unlock the object you like to edit.
The second way is to edit the configuration files directly using a text editor of your choice. The map config files are located at etc/maps/
.
For valid formats and values have a look at Map Config Format Description.
http://<nagiosserver>/<path-to-nagvis>/frontend/nagvis-js/?mod=Map&show=<mapname>(i.e. http://localhost/nagvis/frontend/nagvis-js/?mod=Map&show=europe).
Have fun and please report bugs! nagvis-nagvis-1.9.47/docs/en_US/installer.html 0000664 0000000 0000000 00000004106 15014016017 0021210 0 ustar 00root root 0000000 0000000
There is a new installer in NagVis 1.4. This installer was created to make the progress of installing or updating NagVis easier. The installer is a bash script which asks for all information needed for installing or updating NagVis.
It is also possible to set all options via command line parameters for running the installer in quiet mode.
Get NagVis. The latest release can be found at nagvis.org.
Unpack the archive to a temporary place (for example /tmp) and change to that directory
tar xvzf nagvis-1.8*.tar.gz /tmp cd /tmp/nagvis-1.8*
The installer is located in the root directory of the NagVis package. The installer has to be made executable before you can use it.
chmod +x install.sh
Now you can run the installer.
./install.sh
Using Icinga you should add "-s icinga".
./install.sh -s icinga
Following the instructions of the installer it should copy the necessary files to the correct places. Please keep in mind that you have to edit the config file nagvis.ini.php
. If you experience any problems please let us know.
You can remove the sources after installation.
rm -rf /tmp/nagvis-1.8*
For details about the command line parameters call the installer with the "-h" option.
nagvis-nagvis-1.9.47/docs/en_US/lines_weathermap_style.html 0000664 0000000 0000000 00000007621 15014016017 0023767 0 ustar 00root root 0000000 0000000By default NagVis can only visualize the normal states in lines using red, yellow and green coloured lines. Have you ever wanted NagVis to display nice weathermap style lines?
Since NagVis 1.5 it is possible to draw such weathermap style lines which can have more than three colours depending on the current load of e.g. the network interface you like to visualize. There can be a wide colour range of e.g. seven different colours. Take a look at the example image - isn't that beautiful?.
The weathermap style lines currently provide two types of lines:
---%--><--%----
: Arrows with percentage labels in the middle of the line.---%+BW--><--%+BW---
: Arrows with percentage labels in the middle of the line and additional labels which display the current bandwidth usage.The new lines are focused on bandwidth visualization. Since NagVis needs to parse the performance data to gather the current colour for the line there are special requirements on the performance data contents. There is a bandwidth measurement plugin for Nagios which comes with the correct performance data information out of the box. It is downloadable from Nagios Exchange.
To create weathermap style lines in NagVis you need services which send the correct performance data to Nagios. If you got some then simply place a line service object on the map and choose the correct line type. Now take a look at your map - it should work now.
You may want to have a legend which shows you the meaning of the different colours. No problem. Simply add a shape to your map and choose the "demo_traffic_load_legend" shape which is delivered with the NagVis core package.
The weathermap lines do not require a specific Nagios plugin. Only the provided performance format needs to match one of the cases below:
inUsage=21103.42%;85;98 outUsage=226363.55%;85;98 inBandwidth=105.52MBs
outBandwidth=212.22MBs
.in=7196.50566429;;;0;1250000.0 inucast=11.6273564992;;;; innucast=0.017617206817;;;; indisc=0.0;;;; inerr=0.0;0.01;0.1;; out=4044.9635368;;;0;1250000.0 outucast=12.1734899105;;;; outnucast=0.0;;;; outdisc=0.0;;;; outerr=0.0;0.01;0.1;; outqlen=0;;;;
.
Thanks to gjfrater for implementing these lines!
nagvis-nagvis-1.9.47/docs/en_US/logon_modules.html 0000664 0000000 0000000 00000000000 15014016017 0022046 0 ustar 00root root 0000000 0000000 nagvis-nagvis-1.9.47/docs/en_US/map_config_format_description.html 0000664 0000000 0000000 00000337261 15014016017 0025303 0 ustar 00root root 0000000 0000000The NagVis configuration file format is very similiar to the format used by Nagios®.
Configuration statements start with the keyword "define" followed by a type field and a left curly bracket ({). Every following line defines variable-value pairs, separated by an equal sign (=) until a right curly bracket (}) is found.
Hashes (#) are used to mark comments, note that a comment line MUST start with a hash not with other chars like whitespaces!
The first definition in every config file should be of the special type "global". Options which are defined at this paragraph are valid for the whole map and are getting inherited to other types defined later.
Example with all options which have to be set:
define global { map_image=lan.png }
Value | Default | Description |
---|---|---|
| |
|
map_image |
The name of the map image displayed in the background of the NagVis map, for example a Visio (TM) drawing. The value can even be "none" or empty for no background image. It is also possible to add URLs here. The URL has to be surrounded by [ and ]. |
|
alias | map name | The alias is the label for each map. If it is defined it is shown everywhere in NagVis frontend. |
backend_id | inherited (nagvis.ini.php) | Backend-ID defined in Main Configuration file where NagVis should search for the object states. If this parameter is not given, the Backend defined as default backend in the Main Configuration file is used. As of NagVis 1.8 it is possible to define a "," separated list of backends here to combine objects of several backends. Host, host and service group objects do support merging their members into one object when multiple backends are configured for an object. |
background_color | inherited (nagvis.ini.php) | Background colour of this map. If this is not set backgroundcolor from Main Configuration file is taken. |
context_menu | inherited (nagvis.ini.php) | Enable/Disable the context menu on your map objects. |
context_template | inherited (nagvis.ini.php) | Default context template to be used on this map |
event_on_load | inherited (nagvis.ini.php) | Enabled/disables eventhandling on page loading. Initial problematic states will raise events in frontend during page rendering. (New in 1.7b3) |
event_repeat_interval | inherited (nagvis.ini.php) | Repeat frontend events in the given interval. The interval is configured in seconds. Set value to 30 to let NagVis re-raise events for problematic objects every 30 seconds. (New in 1.7b3) |
event_repeat_duration | inherited (nagvis.ini.php) | The time in seconds to repeat alerts for a problematic object as configured in event_repeat_interval. This value defaults to -1, this leads to repeated events until the problematic state has been fixed. (New in 1.7b3) |
event_background | inherited (nagvis.ini.php) | Enable/Disable changing background colour on state changes (configured colour is shown when summary state is PENDING, OK or UP). |
event_highlight | inherited (nagvis.ini.php) | Enable/Disable highlighting of the state changing object by adding a flashing border. |
event_highlight_duration | inherited (nagvis.ini.php) | Set the highlight duration in milliseconds |
event_highlight_interval | inherited (nagvis.ini.php) | Set the highlight interval in milliseconds |
event_log | inherited (nagvis.ini.php) | Enable/Disable the eventlog in the new javascript frontend. The eventlog keeps track of important actions and information. |
event_log_level | inherited (nagvis.ini.php) | Loglevel of the eventlog (Available: debug, info, warning, critical). |
event_log_events | inherited (nagvis.ini.php) | Number of events in the eventlog scrollback |
event_log_height | inherited (nagvis.ini.php) | Height of the javascript eventlog in px |
event_log_hidden | inherited (nagvis.ini.php) | Hide/Show the eventlog on map loading |
event_scroll | inherited (nagvis.ini.php) | Enable/Disable scrolling to the icon which changed the state when the icon is out of the visible scope. |
event_sound | inherited (nagvis.ini.php) | Enable/Disable sound signals on state changes. |
exclude_members | It is possible to exclude member objects completely while fetching the object information from the backend. The filtered elements will not appear anywhere in this object. For details about the filter syntax have a look at the exclude regex definition. (New in 1.6b4) |
|
exclude_member_states | It is possible to exclude one or several member states while calculating the summary state of objects. The filtered elements will appear in the member lists but won't be used for summary state calculations. For details about the filter syntax have a look at the exclude regex definition. (New in 1.6b4) |
|
grid_color | inherited (nagvis.ini.php) | The colour of the grid lines. |
grid_show | inherited (nagvis.ini.php) | Enable/Disable a grid to make the alignment of objects easier in edit mode. Objects are aligned to the upper left corner after moving. |
grid_steps | inherited (nagvis.ini.php) | Scale of the grid in px. |
header_menu | inherited (nagvis.ini.php) | Enable/Disable the header menu |
header_template | inherited (nagvis.ini.php) | header template to be used on this map |
hover_childs_limit | inherited (nagvis.ini.php) | Number of maximum children to be displayed. Set to -1 to disable the limit. |
hover_childs_order | inherited (nagvis.ini.php) | Order direction of child objects |
hover_childs_show | inherited (nagvis.ini.php) | Enable/Disable displaying child objects |
hover_childs_sort | inherited (nagvis.ini.php) | Sort method of child objects |
hover_delay | inherited (nagvis.ini.php) | Delay of hover menu appearance in seconds |
hover_menu | inherited (nagvis.ini.php) | Enable/Disable the hover menu |
hover_template | inherited (nagvis.ini.php) | Default hover template to be used on this map |
| | |
iconset | inherited (nagvis.ini.php) | Iconset to use as default for all objects placed on the map. Can be overwritten on a per object base. In the example "std_small" is used which means an OK state will be displayed using "std_small_ok.png", a CRITICAL state will be displayed by using "std_small_critical.png" and so on. |
icon_size | inherited (nagvis.ini.php) | Scales the iconsets up or down while showing in the map. If left empty, the iconset images will be displayed at their natural size. You can configure this option with either a single integer for giving width and height at once, but you can also provide two comma separated integers to specify different values forr the width and height. |
in_maintenance | 0 | Enable/Disable the maintenance mode of this map. If a map is in maintenance mode only a message gets displayed instead of the map. |
label_show | 0 | Enable/Disable labels for the maps objects |
label_x | center | Default x-position of the labels in px (with prefix + or - relative to the upper left corner of the icons, otherwise absolute position). Since 1.7.7 this can also be set do center, which is the new default option. |
label_y | bottom | Default y-position of the labels in px (with prefix + or - relative to the upper left corner of the icons, otherwise absolute position). Since 1.7.7 this can also be set do bottom, which is the new default option. |
label_width | auto | Default width of the labels in px |
label_background | transparent | Default background colour of the labels. The colour should be given in hexcode. Can also be "transparent". |
label_border | #000000 | Default border colour of the labels. The colour should be given in hexcode. Can also be "transparent". |
label_style | Custom styling for the label text. To be given like HTML style attribute contents. E.g. font-family:sans;font-weight:bold; |
|
line_type | Specifies the type of line when view_type=line. Valid values are: "11" for lines with one arrow at the end of a line. "10" for lines with two arrows pointing to each other in the middle of the line. "12" for plain lines without arrow. |
|
line_width | 3 | This defines the width of the line in px when this object is being displayed as line. |
line_weather_colors | inherited (nagvis.ini.php) | This defines the colours of weathermap colours in the different percentage levels. For example above 10% load it will be coloured #8c00ff. |
only_hard_states | inherited (nagvis.ini.php) | Sets whether soft states should be ignored. Default setting is 0. |
parent_map | The parent map of this map. This option is only used in the menu visualisations of the header menu and sidebar | |
recognize_services | inherited (nagvis.ini.php) | Sets whether the states of the services on hosts, hostgroup objects should be recognised. If this is not given in the config it's set to 1. |
show_in_lists | inherited (nagvis.ini.php) | Show the maps in lists (dropdowns, index page, ...) |
ignore_linked_maps_summary_state | 0 | Ignore child map summary state in parent's summary state |
show_in_multisite | inherited (nagvis.ini.php) | Show the maps in multisite snapin |
stylesheet | inherited (nagvis.ini.php) | Filename of the custom stylesheet to use on the maps (The file needs to be located in the share/nagvis/styles directory) |
url_target | _self | Target of the Icon link, this option adapts <a target=""> (_self is same window) |
host_url | inherited (nagvis.ini.php) | The default url to follow when a user left-clicks on a host object. Available macros: [htmlcgi], [htmlbase], [host_name], [backend_id] |
hostgroup_url | inherited (nagvis.ini.php) | The default url to follow when a user left-clicks on an hostgroup object. Available macros: [htmlcgi], [htmlbase], [hostgroup_name], [backend_id] |
serviceurl | inherited (nagvis.ini.php) | The default url to follow when a user left-clicks on an service object. Available macros: [htmlcgi], [htmlbase], [host_name], [service_description], [backend_id] |
servicegroup_url | inherited (nagvis.ini.php) | The default url to follow when a user left-clicks on an servicegroup object. Available macros: [htmlcgi], [htmlbase], [servicegroup_name], [backend_id] |
dyngroup_url | inherited (nagvis.ini.php) | The default url to follow when a user left-clicks on a dynamic group object. This is disabled by default, because there is no good link target in the default web GUI. So if you use another web GUI, there might be a useful target. Available macros: [htmlcgi], [htmlbase], [dyngroup_name], [backend_id] |
aggr_url | inherited (nagvis.ini.php) | The default url to follow when a user left-clicks on an aggregation object. Available macros: [htmlcgi], [htmlbase], [aggr_name], [backend_id] |
map_url | inherited (nagvis.ini.php) | The default url to follow when a user left-clicks on an map object. Available macros: [htmlcgi], [htmlbase], [map_name] |
zoom | 100 | Zoom factor of the map. Can be set to any percentage value that the map objects should be zoomed in or out (New in 1.7b1). Since 1.8b1 this can be set to "fill", the map is being zoomed to fill the browsers viewport. |
zoombar | inherited (nagvis.ini.php) | Enables a floating bar to make the map zooming controllable by this bar or by using the mouse wheel. To control NagVis scrolling via mouse wheel, you need to press the ALT key and then scroll the mouse wheel while holding the ALT key. (New in 1.8b1) |
Example with all options which have to be set (note that options already defined in the global section are optional):
define host { host_name=localhost x=100 y=200 }
Value | Default | Description |
---|---|---|
object_id | Unique identifier of the object on the current map. Each object on the map needs to have an object_id. The object_id is built of alphanumeric signs of any length. When no object_id is given NagVis will generate one for the object. | |
host_name | Name of the host as defined in Nagios | |
x | X axis coordinate(s). Take a look at the coordinate definition for details. | |
y | Y axis coordinate(s). Take a look at the coordinate definition for details. | |
backend_id | inherited (global) | Backend-ID defined in Main Configuration file where NagVis should search for the object states. If this parameter is not given, the Backend which was set in global section of the map is taken. As of NagVis 1.8 it is possible to define a "," separated list of backends here to combine objects of several backends. All services for hosts with matching names found in all given backends will be added to the single host object. |
context_menu | inherited (nagvis.ini.php) | Enable/Disable the context menu for this object. |
context_template | inherited (nagvis.ini.php) | Context template for this object. |
exclude_members | It is possible to exclude member objects completely while fetching the object information from the backend. The filtered elements will not appear anywhere in this object. For details about the filter syntax have a look at the exclude regex definition. (New in 1.6b4) |
|
exclude_member_states | It is possible to exclude one or several member states while calculating the summary state of objects. The filtered elements will appear in the member lists but won't be used for summary state calculations. For details about the filter syntax have a look at the exclude regex definition. (New in 1.6b4) |
|
hover_menu | inherited (nagvis.ini.php) | Enable/Disable the hover menu |
hover_delay | inherited (nagvis.ini.php) | Delay of hover menu appearance in seconds |
hover_template | inherited (global) | Hover template for this object |
| | |
hover_url | URL which should be displayed in hover menu instead of standard information. There are some macros available: [host_name]: This macro stands for the object name. |
|
hover_childs_show | inherited (nagvis.ini.php) | Enable/Disable displaying child objects |
hover_childs_sort | inherited (nagvis.ini.php) | Sort method of child objects |
hover_childs_order | inherited (nagvis.ini.php) | Order direction of child objects |
hover_childs_limit | inherited (nagvis.ini.php) | Maximum number of children to be displayed. Set to -1 to disable the limit. |
iconset | inherited (global) | Special iconset. Is inherited from global paragraph if not specified. |
icon_size | inherited (nagvis.ini.php) | Scales the iconsets up or down while showing in the map. If left empty, the iconset images will be displayed at their natural size. You can configure this option with either a single integer for giving width and height at once, but you can also provide two comma separated integers to specify different values forr the width and height. |
label_show | inherited (global) | Enable/Disable label for this object |
label_text | [name] | Text of the label. Available macros: [name], [alias], [output] |
label_x | inherited (global) | Label X-Position (with prefix + or - relative to the upper left corner of the icons, otherwise absolute position) |
label_y | inherited (global) | Label Y-Position (with prefix + or - relative to the upper left corner of the icons, otherwise absolute position) |
label_width | inherited (global) | Width of the label in px |
label_background | inherited (global) | Background colour of the label. The colour should be given in hexcode. Can also be "transparent". |
label_border | inherited (global) | Border colour of the labels. The colour should be given in hexcode. Can also be "transparent". |
label_style | inherited (global) | Custom styling for the label text. To be given like HTML style attribute contents. E.g. font-family:sans;font-weight:bold; |
line_type | inherited (global) | Specifies the type of line when view_type=line. Valid values are: "11" for lines with one arrow at the end of a line. "10" for lines with two arrows pointing to each other in the middle of the line. "12" for plain lines without arrow. |
line_width | inherited (global) | This defines the width of the line in px when this object is being displayed as line. |
only_hard_states | inherited (global) | Sets whether soft states should be ignored. Default setting is 0. |
recognize_services | inherited (global) | Defines if the services of the host affect the displayed state. If set to "1" a critical service on the host will result in a host state display as critical too. If set to "0" only the Nagios Host State (UP or DOWN) will be used and the services of the host will be ignored. |
url | URL where the Icon should link to. Default link is to the Nagios CGIs. Macros [host_name], [htmlcgi] and [htmlbase] are available. The value can be set to "#" to disable the link. | |
url_target | _self | Target of the Icon link, this option adapts <a target=""> (_self is same window). Macro [name] is available. |
use | Comma separated list of object templates to use. For details see template objects | |
view_type | icon | This option defines the type of view for this object. Possible values are: "icon" or "line". Before NagVis 1.4 you could change the view of an object by setting the line_type. Since NagVis 1.4 you need to set the view_type for changing icons to lines. |
z | 1 | The z option defines the order of icons which are stacked on top of each other. The highest value will be displayed on top. The background image has the value of 0. So valid values should be above or equal 1. Note: To prevent conflicts with the header navigation you should keep this value below 100. |
Example with all options which have to be set (note that option already defined in the global section are optional):
define service { host_name=localhost service_description=ping iconset=std_big x=100 y=200 }
Value | Default | Description |
---|---|---|
object_id | Unique identifier of the object on the current map. Each object on the map needs to have an object_id. The object_id is built of alphanumeric signs of any length. When no object_id is given NagVis will generate one for the object. | |
host_name | Name of the host as defined in Nagios | |
service_description | Name of the service as defined in Nagios | |
x | X axis coordinate(s). Take a look at the coordinate definition for details. | |
y | Y axis coordinate(s). Take a look at the coordinate definition for details. | |
backend_id | inherited (global) | Backend-ID defined in Main Configuration file where NagVis should search for the object states. If this parameter is not given, the Backend which was set in global section of the map is taken. |
context_menu | inherited (nagvis.ini.php) | Enable/Disable the context menu for this object. |
context_template | inherited (nagvis.ini.php) | Context template for this object. |
exclude_members | It is possible to exclude member objects completely while fetching the object information from the backend. The filtered elements will not appear anywhere in this object. For details about the filter syntax have a look at the exclude regex definition. (New in 1.6b4) |
|
exclude_member_states | It is possible to exclude one or several member states while calculating the summary state of objects. The filtered elements will appear in the member lists but won't be used for summary state calculations. For details about the filter syntax have a look at the exclude regex definition. (New in 1.6b4) |
|
gadget_url | The value can be a gadget script in gadget path (nagvis/gadgets ) e.g. "std_speedometer.php" or a full URI to a gadget like script surrounded by brackets e.g. "[http://127.0.0.1/nagvis/gadgets/std_speedometer.php]". For details about gadgets see here. This option is only recognised when view_type="gadget" is set. |
|
gadget_scale | 100 | The scale of the gadget. Default scale is 100 (percent). The gadgets should be able to be resized by this parameter |
gadget_type | img | The type of the rendered output. This can be "html" when the gadget renders normal HTML code, or "img" when the gadget renders an image. |
gadget_opts | Optional gadget specific params. The contents can be freely defined for each gadget. The value is processed as GET param "opts". We recommend to use a var/val format like this: key1=val1,key2=val2. Then you can easily split this string to an array in the gadget. | |
hover_menu | inherited (nagvis.ini.php) | Enable/Disable the hover menu |
hover_template | inherited (global) | Hover template for this object |
| | |
hover_delay | inherited (nagvis.ini.php) | Delay of hover menu appearance in seconds |
hover_url | URL which should be displayed in hover menu instead of standard information. There are some macros available: [host_name]: This macro stands for the object name. [service_description]: This macro stands for the service description and will only be replaced in service objects. |
|
hover_childs_show | inherited (nagvis.ini.php) | Enable/Disable displaying child objects |
hover_childs_sort | inherited (nagvis.ini.php) | Sort method of child objects |
hover_childs_order | inherited (nagvis.ini.php) | Order direction of child objects |
hover_childs_limit | inherited (nagvis.ini.php) | Maximum number of children to be displayed. Set to -1 to disable the limit. |
iconset | inherited (global) | Special iconset. Is inherited from global paragraph if not specified. |
icon_size | inherited (nagvis.ini.php) | Scales the iconsets up or down while showing in the map. If left empty, the iconset images will be displayed at their natural size. You can configure this option with either a single integer for giving width and height at once, but you can also provide two comma separated integers to specify different values forr the width and height. |
label_show | inherited (global) | Enable/Disable label for this object |
label_text | [name] [service_description] | Text of the label. Available macros: [name], [alias], [service_description], [output] |
label_x | inherited (global) | Label X-Position (with prefix + or - relative to the upper left corner of the icons, otherwise absolute position) |
label_y | inherited (global) | Label Y-Position (with prefix + or - relative to the upper left corner of the icons, otherwise absolute position) |
label_width | inherited (global) | Width of the label in px |
label_background | inherited (global) | Background colour of the label. The colour should be given in hexcode. Can also be "transparent". |
label_border | inherited (global) | Border colour of the labels. The colour should be given in hexcode. Can also be "transparent". |
label_style | inherited (global) | Custom styling for the label text. To be given like HTML style attribute contents. E.g. font-family:sans;font-weight:bold; |
line_type | inherited (global) | Specifies the type of line when view_type=line. Valid values are: "11" for lines with one arrow at the end of a line. "10" for lines with two arrows pointing to each other in the middle of the line. "12" for plain lines without arrow. |
line_width | inherited (global) | This defines the width of the line in px when this object is being displayed as line. | line_cut | 0.5 | Lines with two parts have the cut in the middle of the line. This equates to a line cut value of "0.5". It is possible to relocate the cut by changing this value. Valid values are 0.0 to 1.0. |
line_label_pos_in | 0.5 | Weathermap lines have their labels in the middle of the line by default. This equates to a value of "0.5". It is possible to relocate the cut by changing this value. Valid values are 0.0 to 1.0. |
line_label_pos_out | 0.5 | Weathermap lines have their labels in the middle of the line by default. This equates to a value of "0.5". It is possible to relocate the cut by changing this value. Valid values are 0.0 to 1.0. |
line_label_in | in | Specify which performance data name you want to use for the "inbound" weathermap line. |
line_label_out | out | Specify which performance data name you want to use for the "outbound" weathermap line. |
line_label_y_offset | 2 | This option defines the offset of the labels to the line when rendering weathermap lines which show percentage and absolute bandwidth labels. |
line_weather_colors | inherited (global) | This defines the colours of weathermap colours in the different percentage levels. For example above 10% load it will be coloured #8c00ff. |
only_hard_states | inherited (global) | Sets whether soft states should be ignored. Default setting is 0. |
url | URL where the Icon should link to. Default link is to the Nagios CGIs. Macros [host_name], [htmlcgi] and [htmlbase] are available. The value can be set to "#" to disable the link. | |
url_target | _self | Target of the Icon link, this option adapts <a target=""> (_self is same window). Available macros: [name], [service_description], |
use | Comma separated list of object templates to use. For details see template objects | |
view_type | icon | This option defines the type of view for this object. Possible values are: "icon" or "line". Before NagVis 1.4 you could change the view of an object by setting the line_type. Since NagVis 1.4 you need to set the view_type for changing icons to lines. |
z | 1 | The z option defines the order of icons which are stacked on top of each other. The highest value will be displayed on top. The background image has the value of 0. So valid values should be above or equal 1. Note: To prevent conflicts with the header navigation you should keep this value below 100. |
Example with all options which have to be set (note that options already defined in the global section are optional):
define hostgroup { hostgroup_name=servers x=100 y=200 }
Value | Default | Description |
---|---|---|
object_id | Unique identifier of the object on the current map. Each object on the map needs to have an object_id. The object_id is built of alphanumeric signs of any length. When no object_id is given NagVis will generate one for the object. | |
hostgroup_name | Name of the hostgroup as defined in Nagios | |
x | X axis coordinate(s). Take a look at the coordinate definition for details. | |
y | Y axis coordinate(s). Take a look at the coordinate definition for details. | |
backend_id | inherited (global) | Backend-ID defined in Main Configuration file where NagVis should search for the object states. If this parameter is not given, the Backend which was set in global section of the map is taken. As of NagVis 1.8 it is possible to define a "," separated list of backends here to combine objects of several backends. All host members of host groups with matching names found in all given backends will be added to the single host group object. |
context_menu | inherited (nagvis.ini.php) | Enable/Disable the context menu for this object. |
context_template | inherited (nagvis.ini.php) | Context template for this object. |
exclude_members | It is possible to exclude member objects completely while fetching the object information from the backend. The filtered elements will not appear anywhere in this object. For details about the filter syntax have a look at the exclude regex definition. (New in 1.6b4) |
|
exclude_member_states | It is possible to exclude one or several member states while calculating the summary state of objects. The filtered elements will appear in the member lists but won't be used for summary state calculations. For details about the filter syntax have a look at the exclude regex definition. (New in 1.6b4) |
|
hover_menu | inherited (nagvis.ini.php) | Enable/Disable the hover menu |
hover_delay | inherited (nagvis.ini.php) | Delay of hover menu appearance in seconds |
hover_template | inherited (global) | Hover template for this object |
| | |
hover_url | URL which should be displayed in hover menu instead of standard information. There are some macros available: [hostgroup_name]: This macro stands for the object name. |
|
hover_childs_show | inherited (nagvis.ini.php) | Enable/Disable displaying child objects |
hover_childs_sort | inherited (nagvis.ini.php) | Sort method of child objects |
hover_childs_order | inherited (nagvis.ini.php) | Order direction of child objects |
hover_childs_limit | inherited (nagvis.ini.php) | Maximum number of children to be displayed. Set to -1 to disable the limit. |
iconset | inherited (global) | Special iconset. Is inherited from global paragraph if not specified. |
icon_size | inherited (nagvis.ini.php) | Scales the iconsets up or down while showing in the map. If left empty, the iconset images will be displayed at their natural size. You can configure this option with either a single integer for giving width and height at once, but you can also provide two comma separated integers to specify different values forr the width and height. |
label_show | inherited (global) | Enable/Disable label for this object |
label_text | [name] | Text of the label. Available macros: [name], [alias], [output] |
label_x | inherited (global) | Label X-Position (with prefix + or - relative to the upper left corner of the icons, otherwise absolute position) |
label_y | inherited (global) | Label Y-Position (with prefix + or - relative to the upper left corner of the icons, otherwise absolute position) |
label_width | inherited (global) | Width of the label in px |
label_background | inherited (global) | Background colour of the label. The colour should be given in hexcode. Can also be "transparent". |
label_border | inherited (global) | Border colour of the labels. The colour should be given in hexcode. Can also be "transparent". |
label_style | inherited (global) | Custom styling for the label text. To be given like HTML style attribute contents. E.g. font-family:sans;font-weight:bold; |
line_type | inherited (global) | Specifies the type of line when view_type=line. Valid values are: "11" for lines with one arrow at the end of a line. "10" for lines with two arrows pointing to each other in the middle of the line. "12" for plain lines without arrow. |
line_width | inherited (global) | This defines the width of the line in px when this object is being displayed as line. |
recognize_services | inherited (global) | Defines if the services of the hosts affect the displayed state. If set to "1" a critical service on one of the host will result in a hostgroup state display as critical too. If set to "0" only the Nagios Host State (UP or DOWN) will be used and the services of the hosts will be ignored. |
url | URL where the Icon should link to. Default link is to the Nagios CGIs. Macros [host_name], [htmlcgi] and [htmlbase] are available. The value can be set to "#" to disable the link. | |
url_target | _self | Target of the Icon link, this option adapts <a target=""> (_self is same window). Available macros: [name] |
use | Comma separated list of object templates to use. For details see template objects | |
view_type | icon | This option defines the type of view for this object. Possible values are: "icon" or "line". Before NagVis 1.4 you could change the view of an object by setting the line_type. Since NagVis 1.4 you need to set the view_type for changing icons to lines. |
z | 1 | The z option defines the order of icons which are stacked on top of each other. The highest value will be displayed on top. The background image has the value of 0. So valid values should be above or equal 1. Note: To prevent conflicts with the header navigation you should keep this value below 100. |
Example with all options which have to be set (note that options already defined in the global section are optional):
define servicegroup { servicegroup_name=servicegroup1 x=100 y=200 }
Value | Default | Description |
---|---|---|
object_id | Unique identifier of the object on the current map. Each object on the map needs to have an object_id. The object_id is built of alphanumeric signs of any length. When no object_id is given NagVis will generate one for the object. | |
servicegroup_name | Name of the servicegroup as defined in Nagios. | |
x | X axis coordinate(s). Take a look at the coordinate definition for details. | |
y | Y axis coordinate(s). Take a look at the coordinate definition for details. | |
backend_id | inherited (global) | Backend-ID defined in Main Configuration file where NagVis should search for the object states. If this parameter is not given, the Backend which was set in global section of the map is taken. As of NagVis 1.8 it is possible to define a "," separated list of backends here to combine objects of several backends. All service members of groups with matching names found in all given backends will be added to the single servie group object. |
context_menu | inherited (nagvis.ini.php) | Enable/Disable the context menu for this object. |
context_template | inherited (nagvis.ini.php) | Context template for this object. |
exclude_members | It is possible to exclude member objects completely while fetching the object information from the backend. The filtered elements will not appear anywhere in this object. For details about the filter syntax have a look at the exclude regex definition. (New in 1.6b4) |
|
exclude_member_states | It is possible to exclude one or several member states while calculating the summary state of objects. The filtered elements will appear in the member lists but won't be used for summary state calculations. For details about the filter syntax have a look at the exclude regex definition. (New in 1.6b4) |
|
hover_menu | inherited (nagvis.ini.php) | Enable/Disable the hover menu |
hover_url | URL which should be displayed in hover menu instead of standard information. There are some macros available: [servicegroup_name]: This macro stands for the object name. |
|
hover_template | inherited (global) | Hover template for this object |
| | |
hover_delay | inherited (nagvis.ini.php) | Delay of hover menu appearance in seconds |
hover_childs_show | inherited (nagvis.ini.php) | Enable/Disable displaying child objects |
hover_childs_sort | inherited (nagvis.ini.php) | Sort method of child objects |
hover_childs_order | inherited (nagvis.ini.php) | Order direction of child objects |
hover_childs_limit | inherited (nagvis.ini.php) | Number of maximum children to be displayed. Set to -1 to disable the limit. |
iconset | inherited (global) | Special iconset. Is inherited from global paragraph if not specified. |
icon_size | inherited (nagvis.ini.php) | Scales the iconsets up or down while showing in the map. If left empty, the iconset images will be displayed at their natural size. You can configure this option with either a single integer for giving width and height at once, but you can also provide two comma separated integers to specify different values forr the width and height. |
label_show | inherited (global) | Enable/Disable label for this object |
label_text | [name] | Text of the label. Available macros: [name], [alias], [output] |
label_x | inherited (global) | Label X-Position (with prefix + or - relative to the upper left corner of the icons, otherwise absolute position) |
label_y | inherited (global) | Label Y-Position (with prefix + or - relative to the upper left corner of the icons, otherwise absolute position) |
label_width | inherited (global) | Width of the label in px |
label_background | inherited (global) | Background colour of the label. The colour should be given in hexcode. Can also be "transparent". |
label_border | inherited (global) | Border colour of the labels. The colour should be given in hexcode. Can also be "transparent". |
label_style | inherited (global) | Custom styling for the label text. To be given like HTML style attribute contents. E.g. font-family:sans;font-weight:bold; |
line_type | inherited (global) | Specifies the type of line when view_type=line. Valid values are: "11" for lines with one arrow at the end of a line. "10" for lines with two arrows pointing to each other in the middle of the line. "12" for plain lines without arrow. |
line_width | inherited (global) | This defines the width of the line in px when this object is being displayed as line. |
only_hard_states | inherited (global) | Sets whether soft states should be ignored. Default setting is 0. |
url | URL where the Icon should link to. Default link is to the Nagios CGIs. Macros [host_name], [htmlcgi] and [htmlbase] are available. The value can be set to "#" to disable the link. | |
url_target | _self | Target of the Icon link, this option adapts <a target=""> (_self is same window). Available macros: [name] |
use | Comma separated list of object templates to use. For details see template objects | |
view_type | icon | This option defines the type of view for this object. Possible values are: "icon" or "line". Before NagVis 1.4 you could change the view of an object by setting the line_type. Since NagVis 1.4 you need to set the view_type for changing icons to lines. |
z | 1 | The z option defines the order of icons which are stacked on top of each other. The highest value will be displayed on top. The background image has the value of 0. So valid values should be above or equal 1. Note: To prevent conflicts with the header navigation you should keep this value below 100. |
Example with all options which have to be set (note that options already defined in the global section are optional):
define map { map_name=webserver x=77 y=156 }
Value | Default | Description |
---|---|---|
object_id | Unique identifier of the object on the current map. Each object on the map needs to have an object_id. The object_id is built of alphanumeric signs of any length. When no object_id is given NagVis will generate one for the object. | |
map_name | Name of the NagVis map cfg file (without .cfg extension) | |
x | X axis coordinate(s). Take a look at the coordinate definition for details. | |
y | Y axis coordinate(s). Take a look at the coordinate definition for details. | |
context_menu | inherited (nagvis.ini.php) | Enable/Disable the context menu for this object. |
context_template | inherited (nagvis.ini.php) | Context template for this object. |
exclude_members | It is possible to exclude member objects completely while fetching the object information from the backend. The filtered elements will not appear anywhere in this object. For details about the filter syntax have a look at the exclude regex definition. (New in 1.6b4) |
|
exclude_member_states | It is possible to exclude one or several member states while calculating the summary state of objects. The filtered elements will appear in the member lists but won't be used for summary state calculations. For details about the filter syntax have a look at the exclude regex definition. (New in 1.6b4) |
|
hover_menu | inherited (nagvis.ini.php) | Enable/Disable the hover menu |
hover_url | URL which should be displayed in hover menu instead of standard information. There are some macros available: [map_name]: This macro stands for the object name. |
|
hover_template | inherited (global) | Hover template for this object |
| | |
hover_delay | inherited (nagvis.ini.php) | Delay of hover menu appearance in seconds |
hover_childs_show | inherited (nagvis.ini.php) | Enable/Disable displaying child objects |
hover_childs_sort | inherited (nagvis.ini.php) | Sort method of child objects |
hover_childs_order | inherited (nagvis.ini.php) | Order direction of child objects |
hover_childs_limit | inherited (nagvis.ini.php) | Number of maximum children to be displayed. Set to -1 to disable the limit. |
iconset | inherited (global) | Special iconset. Is inherited from global paragraph if not specified. |
icon_size | inherited (nagvis.ini.php) | Scales the iconsets up or down while showing in the map. If left empty, the iconset images will be displayed at their natural size. You can configure this option with either a single integer for giving width and height at once, but you can also provide two comma separated integers to specify different values forr the width and height. |
label_show | inherited (global) | Enable/Disable label for this object |
label_text | [name] | Text of the label. Available macros: [name], [alias], [output] |
label_x | inherited (global) | Label X-Position (with prefix + or - relative to the upper left corner of the icons, otherwise absolute position) |
label_y | inherited (global) | Label Y-Position (with prefix + or - relative to the upper left corner of the icons, otherwise absolute position) |
label_width | inherited (global) | Width of the label in px |
label_background | inherited (global) | Background colour of the label. The colour should be given in hexcode. Can also be "transparent". |
label_border | inherited (global) | Border colour of the labels. The colour should be given in hexcode. Can also be "transparent". |
label_style | inherited (global) | Custom styling for the label text. To be given like HTML style attribute contents. E.g. font-family:sans;font-weight:bold; |
line_type | inherited (global) | Specifies the type of line when view_type=line. Valid values are: "11" for lines with one arrow at the end of a line. "10" for lines with two arrows pointing to each other in the middle of the line. "12" for plain lines without arrow. |
line_width | inherited (global) | This defines the width of the line in px when this object is being displayed as line. |
only_hard_states | inherited (global) | Sets whether soft states should be ignored. Default setting is 0. |
url | URL where the Icon should link to. Default link is to the Nagios CGIs. Macros [host_name], [htmlcgi] and [htmlbase] are available. The value can be set to "#" to disable the link. | |
url_target | _self | Target of the Icon link, this option adapts <a target=""> (_self is same window). Available macros: [name] |
use | Comma separated list of object templates to use. For details see template objects | |
view_type | icon | This option defines the type of view for this object. Possible values are: "icon" or "line". Before NagVis 1.4 you could change the view of an object by setting the line_type. Since NagVis 1.4 you need to set the view_type for changing icons to lines. |
z | 1 | The z option defines the order of icons which are stacked on top of each other. The highest value will be displayed on top. The background image has the value of 0. So valid values should be above or equal 1. Note: To prevent conflicts with the header navigation you should keep this value below 100. |
Example with major options:
define textbox { text="This is an informational text which can be placed anywhere on the map, HTML can also be used for formatting purposes" x=200 y=100 }
Value | Default | Description |
---|---|---|
object_id | Unique identifier of the object on the current map. Each object on the map needs to have an object_id. The object_id is built of alphanumeric signs of any length. When no object_id is given NagVis will generate one for the object. | |
text | Your own text, HTML is possible. There are some macros: [refresh_counter]: Shows the time until the next reload/rotate dynamically [worker_last_run]: Shows the time of the last worker run |
|
x | X axis coordinate(s). Take a look at the coordinate definition for details. | |
y | Y axis coordinate(s). Take a look at the coordinate definition for details. | |
w | auto | Width of the textbox in px (pixels). Set to "auto" for auto scaling. |
h | auto | Height of the textbox in px (pixels). Set to "auto" for auto scaling. |
background_color | #C0C0C0 | Background colour of the textbox. The colour should be given in hexcode. Can also be "transparent". |
border_color | #000000 | Background colour of the textbox. The colour should be given in hexcode. Can also be "transparent". |
style | Custom styling for the text. To be given like HTML style attribute contents. E.g. font-family:sans;font-weight:bold; |
|
use | Comma separated list of object templates to use. For details see Template | |
z | 1 | The z option defines the order of icons which are stacked on top of each other. The highest value will be displayed on top. The background image has the value of 0. So valid values should be above or equal 1. Note: To prevent conflicts with the header navigation you should keep this value below 100. |
Basicaly shapes are simple images which can be moved and positioned on the map. The shapes are meant to be layout elements. The shapes were added to give the users the option to create less static maps.
Example with all values which have to be set:
define shape { icon="test" x=200 y=100 }
Value | Default | Description |
---|---|---|
object_id | Unique identifier of the object on the current map. Each object on the map needs to have an object_id. The object_id is built of alphanumeric signs of any length. When no object_id is given NagVis will generate one for the object. | |
icon | Filename of the shape. Shapes have to be located in the shape directory (default: nagvis/images/shapes ).
It is also possible to add URLs here. The URL has to be surrounded by [ and ].
|
|
x | X axis coordinate(s). Take a look at the coordinate definition for details. | |
y | Y axis coordinate(s). Take a look at the coordinate definition for details. | |
enable_refresh | 0 | This option activates the shape for regular updates in the frontend. This is only needed for dynamic shape images which change once in a while. |
hover_menu | 0 | Enable/Disable the hover menu |
hover_url | URL which should be displayed when hovering over the image. By default there is no action on hover. | |
hover_delay | inherited (nagvis.ini.php) | Delay of hover menu appearance in seconds |
url | URL where the Icon should link to. By default there is no link. The value can be empty to disable the link. | |
url_target | _self | Target of the Icon link, this option adapts <a target=""> (_self is same window) |
use | Comma separated list of object templates to use. For details see Template | |
z | 1 | The z option defines the order of icons which are stacked on top of each other. The highest value will be displayed on top. The background image has the value of 0. So valid values should be above or equal 1. Note: To prevent conflicts with the header navigation you should keep this value below 100. |
The line is a stateless layout element to connect elements and visualize stateless connections between other objects. The objecttype has been created to make the design less static.
Example with all values which have to be set:
define line { line_type=1 x=200 y=100 }
Value | Default | Description |
---|---|---|
object_id | Unique identifier of the object on the current map. Each object on the map needs to have an object_id. The object_id is built of alphanumeric signs of any length. When no object_id is given NagVis will generate one for the object. | |
line_type | Specifies the type of line when view_type=line. Valid values are: "11" for lines with one arrow at the end of a line. "10" for lines with two arrows pointing to each other in the middle of the line. "12" for plain lines without arrow. |
|
x | X axis coordinate(s). Take a look at the coordinate definition for details. | |
y | Y axis coordinate(s). Take a look at the coordinate definition for details. | |
line_width | 3 | The width of the line in pixels. |
line_color | #ffffff | The fill colour of the line in hex form. Can also be "transparent". |
line_color_border | #000000 | The border colour of the line in hex form. Can also be "transparent". |
hover_menu | 0 | Enable/Disable the hover menu |
hover_url | URL which should be displayed when hovering over the image. By default there is no action on hover. | |
hover_delay | inherited (nagvis.ini.php) | Delay of hover menu appearance in seconds |
url | URL where the Icon should link to. By default there is no link. The value can be empty to disable the link. | |
url_target | _self | Target of the Icon link, this option adapts <a target=""> (_self is same window) |
use | Comma separated list of object templates to use. For details see Template | |
z | 1 | The z option defines the order of icons which are stacked on top of each other. The highest value will be displayed on top. The background image has the value of 0. So valid values should be above or equal 1. Note: To prevent conflicts with the header navigation you should keep this value below 100. |
With this object you have the ability to define all values except the
must-have-attributes
in one object for many others. You can
set all attributes to the value you need and inherit them with the
use
attribute to each object.
Please note: When editing objects using object templates using the web based editing functions the values configured in the template will be copied to the edited objects. From this time the values set in the object are not used anymore. It is not recommended to use the web editing frontend and template objects at the same time.
Example with all values which have to be set:
define template { name=generic-template }
Value | Default | Description |
---|---|---|
name | Template name (simple string without space - has to be unique within the map) | |
... | All values which are available in the objects which inherit this template |
Example with major options:
define container { url="std_hello.php" x=200 y=100 }
Option | Default | Description |
---|---|---|
object_id | Unique identifier of the object on the current map. Each object on the map needs to have an object_id. The object_id is built of alphanumeric signs of any length. When no object_id is given NagVis will generate one for the object. | |
url | The URL to load the contents of the container from. This can be given as simple filename,
in this case script is loaded from the It is possible to add a set of parameters to the URL, it is up to the script to handle them. |
|
x | X axis coordinate. Take a look at the coordinate definition for details. | |
y | Y axis coordinate(s). Take a look at the coordinate definition for details. | |
w | auto | Width of the textbox in px (pixels). Set to "auto" for auto scaling. |
h | auto | Height of the textbox in px (pixels). Set to "auto" for auto scaling. |
view_type | inline | This option defines the way to render the image. Possible values are: "inline" an "iframe". Inline means the
fetched contents are directly put in the a container object (innerHTML ). When setting the
value to iframe an iframe object is created to render the given URL in this iframe. |
enable_refresh | 0 | Enabling this option activates regular updates for this object while being displayed in the frontend. This is only needed for contents which might change during showing the map. |
background_color | #C0C0C0 | Background colour of the textbox. The colour should be given in hexcode. Can also be "transparent". |
border_color | #000000 | Background colour of the textbox. The colour should be given in hexcode. Can also be "transparent". |
style | Custom styling for the text. To be given like HTML style attribute contents. E.g.
font-family:sans;font-weight:bold; . It is applied to a "span" element, the
container element which gets the contents of the requested url added. |
|
use | Comma separated list of object templates to use. For details see Template | |
z | 5 | The z option defines the order of icons which are stacked on top of each other. The highest value will be displayed on top. The background image has the value of 0. So valid values should be above or equal 1. Note: To prevent conflicts with the header navigation you should keep this value below 100. |
This script is delivered with NagVis. It can be used to list data fetched via livestatus on your maps to e.g. display lists of items or just raw numbers.
Please note: By default all queries get the current username added with the AuthUser
livestatus filer. Resulting from this a user can only see the hosts and services he is a contact of.
To change this behaviour you can customize (copy) the std_lq.php and change the setAuthUser
to the following definition:
$setAuthUser = true;
To add the script to your maps you need to add std_lq.php
with additional parameters
to the url
parameter in a container object. The parameters are given as URL parameters.
You have to call this script with at least two parameters:
backend_id | The id of the backend to use as configured in NagVis |
query | The livestatus query to execute (newlines must be given as \\n) |
Optional parameters:
type | Customize the way the resulting data is displayed |
Example calls to this script:
Query a single cell as simple string:std_lq.php?backend_id=live_1&query=GET hosts\\nLimit: 1\\nColumns: host_name\\n&type=cellQuery several columns from a single dataset. Resulting values are displayed separated by ", ":
std_lq.php?backend_id=live_1&query=GET hosts\\nLimit: 1\\nColumns: host_name address state\\n&type=rowQuery one column from several datasets. Each cell found is displayed on a separate line:
std_lq.php?backend_id=live_1&query=GET hosts\\nLimit: 2\\nColumns: host_name\\n&type=columnQuery several columns from several datasets and display them as a table:
std_lq.php?backend_id=live_1&query=GET hosts\\nLimit: 2\\nColumns: host_name state address\\n&type=list
Please note: Dynamic groups can only be used with livestatus backends.
This example creates a dynamic group named "My Dynamic Group" which engroups all services which have the name "CPU load". All used options have to be set (note that options already defined in the global section are optional):
define dyngroup { name=My Dynamic Group object_types=service object_filter=Filter: service_description = CPU load\n x=100 y=200 }
Value | Default | Description |
---|---|---|
object_id | Unique identifier of the object on the current map. Each object on the map needs to have an object_id. The object_id is built of alphanumeric signs of any length. When no object_id is given NagVis will generate one for the object. | |
name | You can configure any name here, it is just a string to make the object identifyable for you. | |
object_types | Controls which type of objects are used within the dynamic group. Can be set to either "host" or "service". | |
object_filter | This is used in the livestatus queries belonging to this object to filter the member objects used in this dynamic group. You need to provide valid livestatus filter definitions here. | |
x | X axis coordinate(s). Take a look at the coordinate definition for details. | |
y | Y axis coordinate(s). Take a look at the coordinate definition for details. | |
backend_id | inherited (global) | Backend-ID defined in Main Configuration file where NagVis should search for the object states. If this parameter is not given, the Backend which was set in global section of the map is taken. As of NagVis 1.8 it is possible to define a "," separated list of backends here to combine objects of several backends. All host members of host groups with matching names found in all given backends will be added to the single host group object. |
context_menu | inherited (nagvis.ini.php) | Enable/Disable the context menu for this object. |
context_template | inherited (nagvis.ini.php) | Context template for this object. |
hover_menu | inherited (nagvis.ini.php) | Enable/Disable the hover menu |
hover_delay | inherited (nagvis.ini.php) | Delay of hover menu appearance in seconds |
hover_template | inherited (global) | Hover template for this object |
| | |
hover_url | URL which should be displayed in hover menu instead of standard information. There are some macros available: [dyngroup_name]: This macro stands for the object name. |
|
hover_childs_show | inherited (nagvis.ini.php) | Enable/Disable displaying child objects |
hover_childs_sort | inherited (nagvis.ini.php) | Sort method of child objects |
hover_childs_order | inherited (nagvis.ini.php) | Order direction of child objects |
hover_childs_limit | inherited (nagvis.ini.php) | Maximum number of children to be displayed. Set to -1 to disable the limit. |
iconset | inherited (global) | Special iconset. Is inherited from global paragraph if not specified. |
icon_size | inherited (nagvis.ini.php) | Scales the iconsets up or down while showing in the map. If left empty, the iconset images will be displayed at their natural size. You can configure this option with either a single integer for giving width and height at once, but you can also provide two comma separated integers to specify different values forr the width and height. |
label_show | inherited (global) | Enable/Disable label for this object |
label_text | [name] | Text of the label. Available macros: [name], [alias], [output] |
label_x | inherited (global) | Label X-Position (with prefix + or - relative to the upper left corner of the icons, otherwise absolute position) |
label_y | inherited (global) | Label Y-Position (with prefix + or - relative to the upper left corner of the icons, otherwise absolute position) |
label_width | inherited (global) | Width of the label in px |
label_background | inherited (global) | Background colour of the label. The colour should be given in hexcode. Can also be "transparent". |
label_border | inherited (global) | Border colour of the labels. The colour should be given in hexcode. Can also be "transparent". |
label_style | inherited (global) | Custom styling for the label text. To be given like HTML style attribute contents. E.g. font-family:sans;font-weight:bold; |
line_type | inherited (global) | Specifies the type of line when view_type=line. Valid values are: "11" for lines with one arrow at the end of a line. "10" for lines with two arrows pointing to each other in the middle of the line. "12" for plain lines without arrow. |
line_width | inherited (global) | This defines the width of the line in px when this object is being displayed as line. |
recognize_services | inherited (global) | Defines if the services of the hosts affect the displayed state. If set to "1" a critical service on one of the host will result in a hostgroup state display as critical too. If set to "0" only the Nagios Host State (UP or DOWN) will be used and the services of the hosts will be ignored. |
url | URL where the Icon should link to. Default link is to the Nagios CGIs. Macros [dyngroup_name], [htmlcgi] and [htmlbase] are available. The value can be set to an empty string to disable the link. | |
url_target | _self | Target of the Icon link, this option adapts <a target=""> (_self is same window). Available macros: [name] |
use | Comma separated list of object templates to use. For details see template objects | |
view_type | icon | This option defines the type of view for this object. Possible values are: "icon" or "line". Before NagVis 1.4 you could change the view of an object by setting the line_type. Since NagVis 1.4 you need to set the view_type for changing icons to lines. |
z | 1 | The z option defines the order of icons which are stacked on top of each other. The highest value will be displayed on top. The background image has the value of 0. So valid values should be above or equal 1. Note: To prevent conflicts with the header navigation you should keep this value below 100. |
Please note: Aggregations can currently only be used with the "mkbi" backend.
This example creates an object showing the state of a Checkmk BI Aggregation which is named "Host localhost". All used options have to be set (note that options already defined in the global section are optional):
define aggr { name=Host localhost x=100 y=200 }
Value | Default | Description |
---|---|---|
object_id | Unique identifier of the object on the current map. Each object on the map needs to have an object_id. The object_id is built of alphanumeric signs of any length. When no object_id is given NagVis will generate one for the object. | |
name | The name you configure here needs to match the name of the Checkmk BI Aggregation you like to show the state of. | |
x | X axis coordinate(s). Take a look at the coordinate definition for details. | |
y | Y axis coordinate(s). Take a look at the coordinate definition for details. | |
backend_id | inherited (global) | Backend-ID defined in Main Configuration file where NagVis should search for the object states. If this parameter is not given, the Backend which was set in global section of the map is taken. As of NagVis 1.8 it is possible to define a "," separated list of backends here to combine objects of several backends. All host members of host groups with matching names found in all given backends will be added to the single host group object. |
context_menu | inherited (nagvis.ini.php) | Enable/Disable the context menu for this object. |
context_template | inherited (nagvis.ini.php) | Context template for this object. |
hover_menu | inherited (nagvis.ini.php) | Enable/Disable the hover menu |
hover_delay | inherited (nagvis.ini.php) | Delay of hover menu appearance in seconds |
hover_template | inherited (global) | Hover template for this object |
| | |
hover_url | URL which should be displayed in hover menu instead of standard information. There are some macros available: [aggr_name]: This macro stands for the object name. |
|
hover_childs_show | inherited (nagvis.ini.php) | Enable/Disable displaying child objects |
hover_childs_sort | inherited (nagvis.ini.php) | Sort method of child objects |
hover_childs_order | inherited (nagvis.ini.php) | Order direction of child objects |
hover_childs_limit | inherited (nagvis.ini.php) | Maximum number of children to be displayed. Set to -1 to disable the limit. |
iconset | inherited (global) | Special iconset. Is inherited from global paragraph if not specified. |
icon_size | inherited (nagvis.ini.php) | Scales the iconsets up or down while showing in the map. If left empty, the iconset images will be displayed at their natural size. You can configure this option with either a single integer for giving width and height at once, but you can also provide two comma separated integers to specify different values forr the width and height. |
label_show | inherited (global) | Enable/Disable label for this object |
label_text | [name] | Text of the label. Available macros: [name], [alias], [output] |
label_x | inherited (global) | Label X-Position (with prefix + or - relative to the upper left corner of the icons, otherwise absolute position) |
label_y | inherited (global) | Label Y-Position (with prefix + or - relative to the upper left corner of the icons, otherwise absolute position) |
label_width | inherited (global) | Width of the label in px |
label_background | inherited (global) | Background colour of the label. The colour should be given in hexcode. Can also be "transparent". |
label_border | inherited (global) | Border colour of the labels. The colour should be given in hexcode. Can also be "transparent". |
label_style | inherited (global) | Custom styling for the label text. To be given like HTML style attribute contents. E.g. font-family:sans;font-weight:bold; |
line_type | inherited (global) | Specifies the type of line when view_type=line. Valid values are: "11" for lines with one arrow at the end of a line. "10" for lines with two arrows pointing to each other in the middle of the line. "12" for plain lines without arrow. |
line_width | inherited (global) | This defines the width of the line in px when this object is being displayed as line. |
recognize_services | inherited (global) | Defines if the services of the hosts affect the displayed state. If set to "1" a critical service on one of the host will result in a hostgroup state display as critical too. If set to "0" only the Nagios Host State (UP or DOWN) will be used and the services of the hosts will be ignored. |
url | URL where the Icon should link to. Default link is to the Checkmk BI Aggregation in Checkmk Web-GUI. Macros [aggr_name], [htmlcgi] and [htmlbase] are available. The value can be set to an empty string to disable the link. | |
url_target | _self | Target of the Icon link, this option adapts <a target=""> (_self is same window). Available macros: [name] |
use | Comma separated list of object templates to use. For details see template objects | |
view_type | icon | This option defines the type of view for this object. Possible values are: "icon" or "line". Before NagVis 1.4 you could change the view of an object by setting the line_type. Since NagVis 1.4 you need to set the view_type for changing icons to lines. |
z | 1 | The z option defines the order of icons which are stacked on top of each other. The highest value will be displayed on top. The background image has the value of 0. So valid values should be above or equal 1. Note: To prevent conflicts with the header navigation you should keep this value below 100. |
This chapter explains the different variable types used in the map configuration file.
The objects on the NagVis maps are positioned using coordinates. By default each coordinate is
a single integer which defines the offset from the upper left corner of the map in px (Pixels).
The example below is a host object which is positioned 100px from the left and 100px from the top of
the map:
define host { object_id=41790e host_name=localhost x=100 y=100 }
It is possible to define multiple coordinates for one object. This is needed for drawing lines on the maps. One example of a line which starts at 100/100 and ends at 200/200:
define service { object_id=1dd76b host_name=localhost service_description=Interface eth0 view_type=line line_type=10 x=110,200 y=110,200 }
When lines have one part (e.g. --->) there must be two coords set. When using lines with two (e.g. ---><---) parts it is possible to set two coordinates for direct lines or three coordinates to reposition the middle of the line to a custom place.
Since NagVis 1.6 it is possible to position objects depending on other objects. A relationship between
two objects is defined from the "childs" view. This means the configuration needs to be done in
the object which belongs to another object.
To define a relationship the coordinate is not given as integer anymore. Instead of the px offset the object_id of the parent object is used to define a relative position.
41790e%+30
= coordinate of object 41790e plus 30 pixels41790e%-199
= coordinate of object 41790e minus 199 pixels41790e%+0
= coordinate same as of object 41790eWe adapt the examples above and give the start of the line a relative position to the host object:
define host { object_id=41790e host_name=localhost x=100 y=100 } define service { object_id=1dd76b host_name=localhost service_description=Interface eth0 view_type=line line_type=10 x=41790e%+0,200 y=41790e%+0,200 }
With the configuration above the beginning of the line is attached to the host object and moved every time the host object is moved.
The above example does not result in exactly the same positions as the first example. The line beginning in the first example is 10px more to the left and 10px more to the bottom. To get that fixed it is possible to define an optional offset to the parent object.
Set the following coordinates to configure an offset of 10px in both directions:
x=41790e%+10,200 y=41790e%+10,200
It is also possible to set a negative offset by replacing the plus (+) sign with a minus (-) sign.
The exclude regular expressions can be used to filter out one or several members of objects. For example it is possible to filter out one specific service of a host, like in this simple example where the service "CPU load" is excluded:
define host { object_id=5932ab host_name=localhost x=123 y=123 exclude_members=CPU load }This was not a real regex but for example this regex would exclude all services starting with the string "DB_test"
exclude_members=^DB_test
The same is possible for hostgroups, servicegroups and so on.
Another more advanced task is to exclude just one service of one host from a hostgroup. This can be seen as a member element of a member. Let's exclude "CPU load" of the host "localhost".
define hostgroup { object_id=b5932a hostgroup_name=mygroup x=42 y=23 exclude_members=localhost~~CPU load }
When excluding members of members you need to use the string "~~" as separator between the two expressions for matching the member name (host_name in this case) and the regex for the name of the members member (service description in this case).
nagvis-nagvis-1.9.47/docs/en_US/maps.html 0000664 0000000 0000000 00000017730 15014016017 0020162 0 ustar 00root root 0000000 0000000The different views in NagVis are named "maps". The classic and most common type of NagVis maps are the static maps. This means one creates a map configuration using the web based configuration editor or using a text editor to create the map configuration.
In NagVis 1.7x a new extension has been made to the map configuration. It is still based on the static map configuration approach but now it is possible to extend those static configuration parts using dynamic and programmable mechanisms.
The new feature has been named "map sources". Each map can make use of one or several map sources. Each of these sources can clear, replace, or alter the whole map configuration.
A map source is built of several PHP functions which take a standardised set of parameters to do their work. The functions are completely free in what they are doing. A source can read CSV files with objects and coordinates, can connect to databases to fetch information, or read data from external services. It is up to the developer.
Text files containing PHP code need to be placed in the share/server/core/sources
directory relative to the NagVis base directory. In OMD the site local files can be placed in
local/share/nagvis/htdocs/server/core/sources
relative to the site base directory.
There no 1:1 relation between the files and the sources themselves. A file can contain one source, several different sources, or even no sources (e.g. to define functions needed by several sources).
One map source consists of two PHP functions which must match the following specifications:
Function name pattern | Parameters |
---|---|
process_<source-name> This is the real source processing function. It can alter the map configuration in place. The return code of the function is not used in any way at the moment. |
$MAPCFG - The GlobalMapCfg PHP object |
$map_name - The name of the map as string |
|
&$map_config - Reference of the map config array. This array must be modified
to alter the map configuration.
|
|
changed_<source-name> This function is used to tell the map config processing of NagVis whether or not the the map configuration has to be reloaded. It must return "true" to tell NagVis to reload the map configuration. This means also to execute the process_* function of all configured sources. |
$MAPCFG - The GlobalMapCfg PHP object |
$compare_time - The unix timestamp of the currently cached map configuration.
|
When loading a map configuration NagVis checks whether or not the map configuration has already been parsed and cached. If the map is already cached and the cache is up-to-date NagVis can use the map configuration cache which can be processed much faster than parsing and validating the map configuration.
In general NagVis compares the file ages of the used config files (main configuration and map configuration files) with the map configuration cache to make the decision.
When using map sources each source must tell the map config processing code whether or not the map source thinks that the map configuration has to be reloaded or can use the map configuration cache. This is done by the changed_* function of each source. When this function returns "true" this tells NagVis to reload the map configuration.
Loading the map configuration means that NagVis parses the map configuration file to fill the array of map objects. Then this information is validated to prevent broken configurations. Then all configured map sources are processed to provide the opportunity to alter the map configuration.
Each map source can define view parameters and config variables to be available in maps which make use of these sources. This is an example definition of the geomap map source:
// options to be modifiable by the user(url) global $viewParams; $viewParams = array( 'geomap' => array( 'zoom', 'geomap_type', 'source_file', ) ); // Config variables to be registered for this source global $configVars; $configVars = array( 'geomap_type' => array( 'must' => false, 'default' => 'osmarender', 'match' => '/^(osmarender|mapnik|cycle)$/i', 'field_type' => 'dropdown', 'list' => 'list_geomap_types', ), 'source_file' => array( 'must' => false, 'default' => '', 'match' => MATCH_STRING_EMPTY, 'field_type' => 'dropdown', 'list' => 'list_geomap_source_files', ), 'zoom' => array( 'must' => false, 'default' => '', 'match' => MATCH_INTEGER_EMPTY, ), );
These definitions lead to a) three new map configuration options for the global section of the map and b) make these three URL parameters available in the URLs of the maps using this source.
Since implementation of the map sources feature even regular maps without any configured sources can be modified using some default view parameters. Some of the parameters are not completely new, they have just been recoded to be view parameters. Here is the list of general view parameters:
Parameter | Description |
---|---|
backend_id | Changes the default backend to be used in the current map. Take a look at the map configuration option for details. |
iconset | Overrides the iconset configured in global section of the map. Take a look at the map configuration option for details. |
width | Can be used to alter the map configuration dimensions. Is not used by regular maps at the moment. This option is only used by some map sources. |
height | Can be used to alter the map configuration dimensions. Is not used by regular maps at the moment. This option is only used by some map sources. |
header_menu | Overrides the header_menu setting configured in global section of the map. Take a look at the map configuration option for details. |
hover_menu | Overrides the hover_menu setting configured in global section of the map. Take a look at the map configuration option for details. option for details. |
context_menu | Overrides the context_menu setting configured in global section of the map. Take a look at the map configuration option for details. option for details. |
At the moment there are three map sources available in default NagVis. Descriptions about the geomap, the automap and the dynmap sources can be found on their dedicated documentation pages.
The Main Configuration file is designed in plain text "ini"-like format.
There are sections which are marked by the surrounding brackets [] and variables which have an assigned value. The variables have to be in the correct section so you have to ensure to have uncommented the section too.
Semicolons (;
) are used to mark comments. Sections and variables with a leading semicolon are commented out and won't be recognised by NagVis.
In a fresh NagVis installation there is no file with the default configuration. The default configuration is stored in the PHP-Code of NagVis. If there is a file etc/nagvis.ini.php
which has stored configuration information it will override the default configurations.
There is a file etc/nagvis.ini.php-sample
with sample configuration values. All values are commented out.
All values which are used througout NagVis are stored in the global section.
Value | Default | Description |
---|---|---|
audit_log | 0 | Enable/Disable logging of security related user actions in Nagvis. For example user logins and logouts are logged in var/nagvis-audit.log. |
authmodule | CoreAuthModSQLite | Defines the authentication module to use. By default NagVis uses the built-in SQLite authentication module. On delivery there is no other authentication module available. It is possible to add own authentication modules for supporting other authentication mechanism. |
authorisationmodule | CoreAuthorisationModSQLite | Defines the authorisation module to use. By default NagVis uses the built-in SQLite authorisation module. On delivery there is no other authorisation module available. It is possible to add own authorisation modules for supporting other authorisation mechanism. |
dateformat | Y-m-d H:i:s | The format of date and time shown in NagVis. Available options like in date function of php |
dialog_ack_sticky | 1 | Is set to 1 by default to enable the preselection of the "sticky acknowledgement" checkbox in the problem acknowledgement dialog. |
dialog_ack_notify | 1 | Is set to 1 by default to enable the preselection of the "notify acknowledgement" checkbox in the problem acknowledgement dialog. |
dialog_ack_persist | 0 | Is set to 0 by default to disable the preselection of the "persist comment" checkbox in the problem acknowledgement dialog. |
geomap_server (new in 1.7) | http://geomap.nagvis.org/ | The server to use as source for the NagVis geomaps. Must implement the API which can be found here |
worldmap_tiles_url (new in 1.9.13) | https://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png | Worldmap uses OpenStreetMap tiles as default map background. The URL specifies where to GET the PNG tile images from. |
worldmap_tiles_attribution (new in 1.9.13) | © <a href="http://www.openstreetmap.org/copyright">OpenStreetMap</a> | Map tiles attribution text (shown in bottom right corner) |
worldmap_satellite_tiles_url worldmap_satellite_tiles_attribution (new in 1.9.13) |
Secondary map background tiles (satellite images) URL and attribution. When used, the layers control appears on top right corner of the map. | |
http_proxy (new in 1.6) | The proxy server to use for external HTTP request. | |
http_timeout (new in 1.6) | 2 | The timeout in seconds for external HTTP requests. |
language | en_US | Select default language to use in NagVis. There are several translations delivered by default: en_US (English), de_DE (German), fr_FR (French) and pt_BR (Brazilian Portuguese; since 1.4.4). Since NagVis 1.4 you have to select the languages in a new format ("en_US" instead of "english") |
language_available | de_DE,en_US,es_ES,fr_FR,pt_BR | You may want to give your users a limited number of languages to choose from. You can control the behaviour without deleting the language files from your NagVis installation. If this value is left empty NagVis will fallback to all configured in languages. If you like to add a new language to your NagVis installation you need to add it to the list here. |
language_detection | user,session,browser,config | This controls how NagVis tries to detect the language of the user to translate NagVis. NagVis knows several mechanisms to detect the language: - user: Explicit user selected language - session: When the user selects a language it is stored in the current session - browser: NagVis tries to detect the user language by the browser agent - config: The installation default language The order you set the options determines how NagVis uses the different mechanisms. |
logonmodule | LogonMixed | Defines the logon module to use. By default NagVis uses the mixed auth module which trusts the username given in REMOTE_USER or displays a HTML logon dialog for requesting authentication information from the user when REMOTE_USER is not set. On delivery there are the following modules available: LogonMixed: The mixed logon module uses the LogonEnv module as default and the LogonDialog module as fallback when LogonEnv returns no username. This should fit the requirements of most environments. LogonDialog: This is an HTML logon dialog for requesting authentication information from the user. LogonEnv: It is possible to realise a fully "trusted" authentication mechanism like all previous NagVis versions used it before. This way the user is not really authenticated with NagVis. NagVis trusts the provided username implicitly. NagVis uses the configured environment variable to identify the user. You can add several authentication mechanisms to your webserver, starting from the basic authentication used by Nagios (.htaccess) to single sign-on environments. Simply set logonmodule to "LogonEnv", put the environment variable to use as username to the option logonenvvar and tell the authentication module to create users in the database when provided users do not exist. The option logonenvcreaterole tells the module to assign the new user to a specific role; set to empty string to disable that behaviour. LogonMultisite: This module uses the authentication provided by auth_* cookies which have been generated by Checkmk multisite when using the cookie based authentication. It is possible to add own logon modules for serving other dialogs. |
logonenvvar | REMOTE_USER | Defines the environment variable to be used for fetching the authenticated user from the webservers environment. This option is only used with the logon modules LogonEnv and LogonMixed. |
logonenvcreateuser | 1 | Tells the LogonEnv/LogonMixed module to create a user account for each unknown user who opens the NagVis pages. This option is only used with the logon modules LogonEnv and LogonMixed. |
logonenvcreaterole | Guests | Tells the LogonEnv/LogonMixed module to create the user accounts with the given role associated. This option is only used with the logon modules LogonEnv and LogonMixed. |
logon_multisite_htpasswd | The path to the htpasswd file which is used by multisite. Only used by the LogonMultisite module. | |
logon_multisite_secret | The path to the auth secret file which is used by multisite. Only used by the LogonMultisite module. | |
logon_multisite_createuser | 1 | Same as the above "logonenvcreateuser" option. Only used by the LogonMultisite module. |
logon_multisite_createrole | Guest | Same as the above "logonenvcreaterole" option. Only used by the LogonMultisite module. |
logon_multisite_cookie_version | 0 | When you use Checkmk 2.2 or newer, you need to set this to 1. Only used by the LogonMultisite module. |
multisite_snapin_layout | list | Can be set to "tree" to change the layout of the multisite snapin contents to a tree which is built using the parent_map configuration option defined in the global sections of the maps. |
only_permitted_objects | 0 | Enable/Disable access to permitted monitoring objects only. This is useful if you want to restrict the access to status information by NagVis AND by the authorization mechanism of the monitoring software (e.g. Nagios). Disabled: access to status information is controlled by NagVis only. Every NagVis user who has access to a NagVis map can see the status of all objects on this map. If he has the permission to add objects to a map he can add ALL monitoring objects and is not restricted by the NagVis permission management. Enabled: every user in NagVis can see the status information only of those monitoring objects for which he has a contact definition in the monitoring software. This means that he can see status information only if he is allowed to access a map AND if he has the permission from the monitoring software for this object. The same applies to adding objects to a map. |
refreshtime | 60 | Refresh time of maps or reloading the next map in map rotation |
sesscookiedomain | auto-detect | You may need to control for which domain NagVis will store the session cookie. By default NagVis tries to auto detect this option value by using the webservers environment variables. This should work in most environments but may be changed e.g. when using url rewriting. |
sesscookiepath | auto-detected | You may need to control the path on which the cookie will be set. By default NagVis uses the paths/htmlbase value for setting the cookie. This should work in most environments but may be changed e.g. when using url rewriting. |
sesscookieduration | 86400 | Lifetime of the NagVis session cookie in seconds. The default value is set to 24 hours. The value of the NagVis session cookie contains will be renewed on every page visit. If a session is idle for more time than configured here it will become invalid. |
sesscookiehttponly | 0 | Most modern browsers will deny javascript access to cookies if the HttpOnly flag is set. This prevents XSS attacks from stealing cookies. Default is off to not break any existing installations that rely on this functionality. Set to 1 to enable. |
sesscookiesecure | 0 | Most modern browsers will prevent cookies from being sent unencrypted if the Secure flag is set. Default is off since not all Nagvis installations require HTTPS. Set to 1 to enable. |
staleness_threshold (new in 1.8b5) | 1.5 | Staleness threshold (Only used with livestatus backend). Take a look at the Checkmk documentation for details about the staleness of hosts/services. The staleness means that an object has not received any state information for a given time. The configured value is a factor of the regular check interval. A value of 1.5 means that an object is marked as stale after one and a half check intervals have passed without update. |
startmodule | overview | The default module to show when none is given by the user |
startaction | view | The default action to do when none is given by the user |
startshow | The startshow parameter is only used by some views at the moment. It is used by the Map and the AutoMap modules. |
Value | Default | Description |
---|---|---|
base | /usr/local/nagvis/share/ | Absolute physical NagVis path |
htmlbase | /nagvis | Absolute html NagVis path |
htmlcgi | /nagvis/cgi-bin | Absolute html NagVis cgi path |
Value | Default | Description |
---|---|---|
backend | live_1 | Default backend (ID of the backend - copy the text from which
<backend-id> stands for in [backend_<backend-id>] ).
As of NagVis 1.8 it is possible to define a "," separated list of backends here to combine
objects of several backends. Host, host and service group objects do support merging their
members into one object when multiple backends are configured for an object. |
backgroundcolor | transparent | Default background colour of maps |
contextmenu | 0 | Enable/Disable the context menu on your map objects. |
contexttemplate | default | Default context template. |
event_on_load | 0 | Enabled/disables event handling on page loading. Initial problematic states will raise events in frontend during page rendering. (New in 1.7b3) |
event_repeat_interval | 0 | Repeat frontend events in the given interval. The interval is configured in seconds. Set value to 30 to let NagVis re-raise events for problematic objects every 30 seconds. Setting this value smaller than [worker] interval will have no effect. (New in 1.7b3) |
event_repeat_duration | -1 | The time in seconds to repeat alerts for a problematic ojects for as configured in event_repeat_interval. This value defaults to -1, this leads to repeated events until the problematic state has been fixed. (New in 1.7b3) |
eventbackground | 0 | Enable/Disable changing background colour on state changes (configured colour is shown when summary state is PENDING, OK or UP) |
eventhighlight | 1 | Enable/Disable highlighting of the state changing object by adding a flashing border |
eventhighlightduration | 10000 | Duration of the highlighting in milliseconds |
eventhighlightinterval | 500 | Interval of the highlighting in milliseconds |
eventlog | 0 | Enable/Disable the eventlog in the new javascript frontend. The eventlog keeps track of important actions and information |
eventlogevents | 24 | Number of events in the eventlog scrollback |
eventloglevel | info | Loglevel of the eventlog (Available: debug, info, warning, critical) |
eventlogheight | 100 | Height of the javascript eventlog in px |
eventloghidden | 1 | Hide/Show the eventlog on map loading |
eventscroll | 1 | Enable/Disable scrolling to the icon which changed the state when the icon is out of the visible scope |
eventsound | 1 | Enable/Disable sound signals on state changes |
headermenu | 1 | Enable/Disable the header menu |
headertemplate | default | Default header template |
header_show_states | 0 | New in 1.8b1: Enable/Disable displaying of map summary states in the headers sidebar menu This is disabled by default to prevent performance problems in large installations. You can safely enable this to test wether the performance impact is OK for you. |
hoverchildslimit | 10 | Limit hover child objects to this maximum value |
hoverchildsorder | asc | Order of the child objects (Available: asc/desc) |
hoverchildsshow | 1 | Enable/Disable the child objects in hover menu |
hoverchildssort | a | Sort method of the child objects (available: "s": state, "a": alphabet, "k": keep original order) |
hoverdelay | 0 | Delay of hover menu appearance in seconds |
hovermenu | 1 | Enable/Disable the hover menu |
hovertemplate | default | Default hover template |
| | |
icons | std_medium | Default iconset |
icon_size | Scales the iconsets up or down while showing in the map. If left empty, the iconset images will be displayed at their natural size. You can configure this option with either a single integer for giving width and height at once, but you can also provide two comma separated integers to specify different values forr the width and height. | |
onlyhardstates | 0 | Recognize only hard states (not soft) |
recognizeservices | 1 | Recognize service states in host/hostgroup objects |
showinlists | 1 | Show the maps in lists (dropdowns,index page,...) |
showinmultisite | 1 | Show the maps in multisite snapin |
stylesheet | Filename of the custom stylesheet to use on the maps (the file needs to be located in the share/nagvis/styles directory) | |
urltarget | _self | Target of the Icon link, this option adapts <a target=""> (_self is same window) |
hosturl | [htmlcgi]/status.cgi?host=[host_name] | The default url to follow when a user left-clicks on a host object. Available macros: [htmlcgi], [htmlbase], [host_name], [backend_id] |
hostgroupurl | [htmlcgi]/status.cgi?hostgroup=[hostgroup_name] | The default url to follow when a user left-clicks on an hostgroup object. Available macros: [htmlcgi], [htmlbase], [hostgroup_name], [backend_id] |
serviceurl | [htmlcgi]/extinfo.cgi?type=2&host=[host_name]&service=[service_description] | The default url to follow when a user left-clicks on an service object. Available macros: [htmlcgi], [htmlbase], [host_name], [service_description], [backend_id] |
servicegroupurl | [htmlcgi]/status.cgi?servicegroup=[servicegroup_name] | The default url to follow when a user left-clicks on an servicegroup object. Available macros: [htmlcgi], [htmlbase], [servicegroup_name], [backend_id] |
dyngroupurl | The default url to follow when a user left-clicks on a dynamic group object. This is disabled by default, because there is no good link target in the default web GUI. So if you use another web GUI, there might be a useful target. Available macros: [htmlcgi], [htmlbase], [dyngroup_name], [backend_id] | |
aggrurl | The default url to follow when a user left-clicks on an aggregation object. Available macros: [htmlcgi], [htmlbase], [aggr_name], [backend_id] | |
mapurl | [htmlbase]/index.php?mod=Map&act=view&show=[map_name] | The default url to follow when a user left-clicks on an map object. Available macros: [htmlcgi], [htmlbase], [map_name] |
host_downtime_url | [html_cgi]/cmd.cgi?cmd_typ=55&host=[name] | The default url to open when a user clicks on the downtime link in the context menu of hosts. Available macros: [htmlcgi], [htmlbase], [host_name], [backend_id] |
host_ack_url | [html_cgi]/cmd.cgi?cmd_typ=96&host=[name]&force_check | The default url to open when a user clicks on the acknowledge link in the context menu of hosts. Available macros: [htmlcgi], [htmlbase], [host_name], [backend_id] |
service_downtime_url | [html_cgi]/cmd.cgi?cmd_typ=56&host=[name]&service=[service_description] | The default url to open when a user clicks on the downtime link in the context menu of services. Available macros: [htmlcgi], [htmlbase], [host_name], [service_description], [backend_id] |
service_ack_url | [html_cgi]/cmd.cgi?cmd_typ=7&host=[name]&service=[service_description]&force_check | The default url to open when a user clicks on the acknowledge link in the context menu of services. Available macros: [htmlcgi], [htmlbase], [host_name], [service_description], [backend_id] |
view_template | default | Templates to be used for the different views. |
label_show | 0 | Show the objects labels or not. |
line_weather_colors | 10:#8c00ff,25:#2020ff,40:#00c0ff,55:#00f000,70:#f0f000,85:#ffc000,100:#ff0000 | This defines the colours of weathermap lines in the different percentage levels. For example above 10% load it will be coloured #8c00ff. |
zoombar | 0 | Enables a floating bar to make the map zooming controllable by this bar or by using the mouse wheel. To control NagVis scrolling via mouse wheel, you need to press the ALT key and then scroll the mouse wheel while holding the ALT key. (New in 1.8b1) |
zoom_scale_objects | 1 | This option allows users to control the scaling behaviour of zoomed objects. By default the whole maps is zoomed like in previous versions. But when zoom_scale_objects is set to 0, the map objects and labels are not resized, but only repositioned according to the given zoom factor. (New in 1.8b3) |
Value | Default | Description |
---|---|---|
backgroundcolor | #fff | Configure the background colour of the overview page |
4 | Maps per row in map listing (Deprecated in 1.8) | |
headermenu | 1 | Enable/Disable the header menu |
headertemplate | default | Default header template |
showautomaps | 1 | Enable/Disable the listing of automaps |
showmaps | 1 | Enable/Disable the listing of maps |
showmapthumbs | 0 | Enable/Disable the listing of map thumbnails |
showrotations | 1 | Enable/Disable the listing of defined rotations |
Value | Default | Description |
---|---|---|
defaultparams | &childLayers=2 | These are the parameters for the automap views and links in the lists (map index page, dropdown menus in header) |
defaultroot | localhost | Default value for the root object. For details see Automap documentation |
graphvizpath | /usr/local/bin | If the graphviz binaries (dot,neato,twopi,...) could not be found in the PATH the path has to be set here |
1 | Enable/Disable the automap in map lists (map index page, dropdown menus in header) (Deprecated in 1.7) |
Value | Default | Description |
---|---|---|
25 | In this interval the map gets backuped by the WUI. (Deprecated in 1.6) | |
grid_show | 0 | Enable/Disable a grid to make the alignment of objects easier in the WUI. Objects are aligned to the upper left corner after moving. |
grid_color | #F7F7F7 | The colour of the grid lines. |
grid_steps | 32 | Scale of the grid in px. |
1 | Enable/Disable the header menu in the WUI. (Deprecated in 1.6) | |
default | Default header template to use in the WUI. (Deprecated in 1.5) | |
maplocktime | 5 | Time in minutes a map is locked by an editing user. |
Value | Default | Description |
---|---|---|
interval | 5 | The interval in seconds in which the worker will check for objects which need to be updated. |
requestmaxparams | 0 | The maximum number of parameters used in ajax http requests. Some intrusion detection/prevention systems have a problem with too many parameters in the url. Set to 0 for no limit. |
requestmaxlength | 1900 | The maximum length of http request urls during ajax http requests. Some intrusion detection/prevention systems have a problem with queries being too long. |
updateobjectstates | 15 | The retention time of the states in seconds in the frontend. The state information will be refreshed after this time is over on next worker interval. |
The backend sections to define the backends are all named [backend_<backend-id>]
.
In the example the backend_id
is live_1
.
Depending on the value in backendtype the valid values for the backends have to be set. In this example it is the MKLivestatus backend.
[backend_live_1] backendtype="mklivestatus" htmlcgi="/nagios/cgi-bin" ; the following options depend on the selected backendtype, in this case it is MKLivestatus socket="unix:/usr/local/nagios/var/rw/live"
Value | Default | Description |
---|---|---|
backendtype | mklivestatus | type of backend - MUST be set |
statushost | The status host can be used to prevent annoying timeouts when a backend is not reachable. This is only useful in multi backend setups. It works as follows: The assumption is that there is a "local" backend which monitors the host of the "remote" backend. When the remote backend host is reported as UP the backend is queried as normal. When the remote backend host is reported as "DOWN" or "UNREACHABLE" NagVis won't try to connect to the backend anymore until the backend host gets available again. The statushost needs to be given in the following format: "<backend_id>:<hostname>" -> e.g. "live_2:nagios" The host needs to be in another backend than the current one to work correctly. |
|
htmlcgi | /nagios/cgi-bin | Path to the cgi-bin directory of this backend (interesting for multiple backends) |
custom_1 | First custom variable which is available in the context and hover menus. With this option different custom URLs can be added to the context/hover menus based on the backend used. Might be interesting when adding links to different Nagios instances. | |
custom_2 | Second custom variable. Same as above. | |
custom_3 | Third custom variable. Same as above. |
For the backendtype specific options see the backends documentation.
[rotation_demo] maps="demo,demo2" interval=15
Value | Default | Description |
---|---|---|
interval | 15 | Map rotation interval in seconds |
maps |
Comma separated list of maps to rotate in this pool. You can also add
external URLs surrounded by [ and ] (e.g. If you like to include whole websites with e.g. own styling and scripts, you should
configure the URL to be included as iframe. This is done like this:
You can add labels in the following format <label>:<map> and <label>:<[url]>. The labels are displayed in the rotation list on the overview page. |
Since NagVis 1.7.6 it is possible to use so called actions to extend the
default context menu. This enables users to connect directly to the monitored
hosts from the NagVis context menu. The configuration is done using
[action_*]
sections in the main configuration.
It is possible to add such actions to the context menus of service and host
objects depending on the "obj_type" option. They are not added blindly to all
objects of those types, you can use the attribute "condition" to configure
which objects shall have the specific actions. By default we use Nagios custom
macros of the host object to make the actions visible/invisible. This filtering
mechanism is not limited to custom macros, you can also use regular host
attributes which are available within NagVis.
With the option "client_os" you can configure the option to only be available
on the clients which have a listed operating system running.
Here is an example for such a section, taken from the sample config:
; Adds the action "connect via ssh" to service/host objects which have the ; string "unix" in the TAGS Nagios custom macro. Is only added when NagVis ; detects that the client watching the map uses linux or mac os. ; When clicking on the link, the browser opens the URL ssh://<address>/, ; you need to configure your clients browser to handle these urls correctly. [action_ssh_url] action_type="ssh_url" obj_type="host,service" client_os="mac,lnx" condition="TAGS~unix"
Value | Default | Description |
---|---|---|
action_type | The type of the custom action (used as reference to the optional custom
action script files located in share/server/core/actions ). |
|
obj_type | host,service | Comma separated list of object types to display this custom action for |
client_os | Comma separated list of client operating systems to display this custom action for. You can
use the values win , lnx and/or mac here. |
|
condition | You can use some sort of filtering mechanism to display the action not on all
objects of that type. The example above can be read like this: "Add this filter to all host and
service objects which contain the string You can use regular attributes or even custom macros of the objects as keys.
At the moment you can use the operator |
An action can be constructed out of three parts:
share/server/core/actions
).The sample configuration defines several sample actions, which might be useful for some users. Here is the list and a short description of the actions:
Action Id | Description |
---|---|
rdp | Adds the action "connect via rdp" to service/host objects where the host object has the string "win" in the TAGS Nagios custom macro. When clicking on the link, NagVis generates a .rdp file which contains a call to make the client connect to the given host via RDP. |
win_ssh | Adds the action "connect via ssh" to service/host objects which have the string "unix" in the TAGS Nagios custom macro. Is only added when NagVis detects that the client watching the map uses windows. When clicking on the link, NagVis generates a .cmd file which contains a call to putty which makes putty connect via SSH to this host. |
ssh_url | Adds the action "connect via ssh" to service/host objects which have the string "unix" in the TAGS Nagios custom macro. Is only added when NagVis detects that the client watching the map uses linux or mac os. When clicking on the link, the browser opens the URL ssh://<address>/, you need to configure your clients browser to handle these urls correctly. |
http | Adds the action "connect via http" to service/host objects which have the string "web-80" in the TAGS Nagios custom macro When clicking on the link, the browser opens a new window with the URL http://<host_address>/. This can be changed by modifying the context template. |
https | Adds the action "connect via https" to service/host objects which have the string "web-443" in the TAGS Nagios custom macro When clicking on the link, the browser opens a new window with the URL https://<host_address>/. This can be changed by modifying the context template. |
Options which affect the handling and appearance of the different states in the NagVis installation.
These settings define the state handling behaviour. Mainly it is possible to configure which state will cover another state changing these values. The state with the highest value will become the "summary state" for an object. For example a critical state (5) will cover a warning state (4). Another example: An acknowledged critical state (2) will not cover a warning state (4).
Value | Default |
---|---|
down | 10 |
down_ack | 6 |
down_downtime | 6 |
unreachable | 9 |
unreachable_ack | 6 |
unreachable_downtime | 6 |
critical | 8 |
critical_ack | 5 |
critical_downtime | 5 |
warning | 7 |
warning_ack | 5 |
warning_downtime | 5 |
unknown | 4 |
unknown_ack | 3 |
unknown_downtime | 3 |
error | 4 |
error_ack | 3 |
error_downtime | 3 |
up | 2 |
ok | 1 |
unchecked (new in 1.6) | 0 |
pending | 0 |
This settings define the behaviour of states in the frontend.
Value | Default |
---|---|
unreachable_bgcolor | #F1811B |
unreachable_color | #F1811B |
unreachable_ack_bgcolor | |
unreachable_downtime_bgcolor | |
unreachable_sound | std_unreachable.mp3 |
down_bgcolor | #FF0000 |
down_color | #FF0000 |
down_ack_bgcolor | |
down_downtime_bgcolor | |
down_sound | std_down.mp3 |
critical_bgcolor | #FF0000 |
critical_color | #FF0000 |
critical_ack_bgcolor | |
critical_downtime_bgcolor | |
critical_sound | std_critical.mp3 |
warning_bgcolor | #FFFF00 |
warning_color | #FFFF00 |
warning_ack_bgcolor | |
warning_downtime_bgcolor | |
warning_sound | std_warning.mp3 |
unknown_bgcolor | #FFCC66 |
unknown_color | #FFCC66 |
unknown_ack_bgcolor | |
unknown_downtime_bgcolor | |
unknown_sound | |
error_bgcolor | #0000FF |
error_color | #0000FF |
error_ack_bgcolor | |
error_downtime_bgcolor | |
error_sound | |
ok_bgcolor | #00FF00 |
ok_color | #00FF00 |
ok | |
up_bgcolor | #00FF00 |
up_color | #00FF00 |
up_sound | |
unchecked_bgcolor (new in 1.6) | #C0C0C0 |
unchecked_color (new in 1.6) | #C0C0C0 |
unchecked_sound (new in 1.6) | |
pending_bgcolor | #C0C0C0 |
pending_color | #C0C0C0 |
pending_sound |
You need an installed, configured and running Nagios to get NagVis working.
You can get Nagios from the official Nagios Homepage.
More information on available Icinga packages/downloads can be found on the official Icinga website.
Since NagVis 1.5 we switched the default backend to MKLivestatus since it is much faster, more lightweight and stable than the NDO. And last but not least it is easy to handle and to install. You don't need any database to get MKLivestatus running.
MKLivestatus is an Event Broker Module for Nagios which serves a unix socket where third party addons like NagVis can connect to for gathering live status information in a very fast way.
You can get MKLivestatus from the official MKLivestatus Homepage.
NagVis is a web based application realised in Javascript and PHP. You need a webserver with PHP support to run NagVis. We recommend the usage of Apache Webserver with mod_php.
The minimum version requirement of PHP is 5.0.0.
Besides the base php packet you need the following modules in your PHP installation. The names of the modules may vary between distributions:
Note: Maybe some of these functions are already compiled into your PHP. php -m
will show the built-in modules.
The backends connect to external datasources and often need some special modules. Here is a list of the needed modules for the different backends. You only need to meet the requirements of the backends you use.
mklivestatusThe Automap is based on Graphviz. You need it when you like to use the automap feature. We recommend the use of Graphviz version >= 2.14 (Earlier versions (with lower version numbers) have some problems with truecolor rendering).
Graphviz is available in some distributions. When you can not use a precompiled distribution package, you can get Graphviz from the official Graphviz Homepage for compiling it on your own.
You will also need more packages like gd, libpng, freetype, ... but if you get graphviz compiled and/or installed it should work.
nagvis-nagvis-1.9.47/docs/en_US/toc.html 0000664 0000000 0000000 00000013334 15014016017 0020003 0 ustar 00root root 0000000 0000000(*) New in 1.9
nagvis-nagvis-1.9.47/docs/en_US/update_instructions.html 0000664 0000000 0000000 00000007767 15014016017 0023341 0 ustar 00root root 0000000 0000000There have been many changes to the internal structure of NagVis and the configuration values.
The recommended way for upgrading to the latest NagVis version is to set up the new version as new
installation and migrate your maps/icons/configurations/... manually.
You should take a look at the following places:
From NagVis 1.4x to NagVis 1.5x we changed a lot in the directory structure.
But in the newest NagVis version there is an installer script included for installing
NagVis. This script can also upgrade NagVis 1.4x versions and newer to the latest NagVis release.
So it is recommended to use this script (install.sh
) distributed with the
newest NagVis version to upgrade your installation.
The permission configuration changed with NagVis 1.5. So the installer removes the allowed_for_config and allowed_users parameters from the map configuration files. The permissions are not automatically re-added to the new permission database. The removed permissions are stored as dump in the nagvis/etc/auth-backup file. With this information you can re-apply the permissions to your maps using the new role based permission system.
It is possible to perform the 1.4x to 1.5x (or newer) update manually too but it has not been tested and documented by anyone. So if you like to update your installation manually you will need to do some research. Basically it should be the same as described above (copying custom files to the new locations and merging your settings into nagvis.ini.php. Don't copy this file!).
Once you made some experience in updating NagVis 1.4x to 1.5 or 1.6 manually please let us know so that we can extend this documentation.
nagvis-nagvis-1.9.47/docs/en_US/user_interface.html 0000664 0000000 0000000 00000005312 15014016017 0022211 0 ustar 00root root 0000000 0000000This page is meant do describe the different views of the NagVis User Interface. The paths are relative to the NagVis root directory.
URL | Description | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
NagVis frontend | |||||||||||
index.php | This is a redirection to nagvis/index.php (NagVis frontend) | ||||||||||
nagvis/frontend/nagvis-js/index.php | This is the overview page. On this view all maps and rotations the user is permitted for are listed and linked. You can exclude a map by setting the option show_in_lists to 0. | ||||||||||
nagvis/frontend/nagvis-js/index.php?mod=Map&show=<name> |
This is the classic map view. This view shows the specified NagVis map. The contents is automatically refreshed using ajax calls to the NagVis core. The following parameters are available:
|
||||||||||
nagvis/frontend/nagvis-js/index.php?mod=Info | This is a page with some support information which you can submit when you are having problems with NagVis | ||||||||||
Rotations | |||||||||||
nagvis/frontend/nagvis-js/index.php?mod=Rotation&show=<name> | This is the map rotation mode. In this mode you call a rotation (rotation has to be defined in main configuration file). The rotation switches different views after a configured timeperiod. |
If you experience any problems using this information please contact us at www.nagvis.org.
Copyright © 2008-2016 NagVis Project
The NagVis Worldmap was introduced in NagVis 1.9. It has been developed to make it possible to create modern and interactive geographical maps.
You can put any kind of NagVis object on a worldmap which is then rendered using Open Street Map.
The most significant different to classic maps is that the single worldmaps don't have a dedicated set of map objects. In fact a worldmap is mainly the definition of a viewport (visible area, zoom) on the world. Each object you position on a worldmap is saved globally across all your worldmaps. This means if you add an object to a worldmap on a high zoom (detail level), the object is also added to worldmaps which are showing the whole earth. This has been done this way out of the assumption that each geographically positioned object has a single position on all maps.
There is no special software needed on the NagVis server, but there is one special requirement. To be able to use this feature, the browser opening NagVis worldmaps needs to be able to fetch the background images (map tiles) from the internet, or a local mirror, see below. In most corporate environments this means that your client needs to have a proxy server configured.
The worldmaps use the official tile servers of Open Street Map (https://{s}.tile.openstreetmap.org/
) as a default.
Alternative tile server (local mirror) may be set in configuration, for example: worldmap_tiles_url="http://my-tiles.local/{z}/{x}/{y}.png"
The switch2osm guides might help you to spin up your local OpenStreetMap mirror.
NagVis comes with a demo worldmap called "demo-worldmap". If your NagVis is configured correctly and your browser is able to fetch the background images from the tile server, you should see a map of germany with three nodes. One node is showing the map "demo-ham-racks", which contains hosts located in Hamburg, one hostgroup "cgn" which contains all hosts located in Cologne and another hostgroup "muc" which contains all hosts located in Munich.
This worldmap is defined using the map configuration file "demo-worldmap.cfg". The contents look like this:
define global { alias=Demo: 4 Worldmap parent_map=demo-overview backend_id=demo iconset=std_geo icon_size=32 sources=worldmap worldmap_center=50.86837814203458,10.21728515625 worldmap_zoom=6 worldmap_tiles_saturate=33 filter_group=my_group }
The attributes after icon_size=32
are worldmap specific definitions.
The sources=worldmap
(mandatory) line tells the map to use the worldmap source, which cares about
putting all the objects having geographical coordinates, for rendering the map.
The worldmap_center=50.86837814203458,10.21728515625
(mandatory) specifies the latitude and longitude
coordinates to use as initial center for the worldmaps viewport.
The worldmap_zoom=6
(mandatory) specifies the initial zoom level to be used when rendering the worldmap.
NagVis allows zoom levels from 2 (world) to 20 (building, detail).
The worldmap_tiles_saturate=33
(optional) dims the colors of default OpenStreetMap so that red motorways or
large green forests don't interfere with actual map objects. Possible values are 0 (no colors, grayscale) through 100 (full colors).
The filter_group=my_group
(optional) is an attribute for filtering the host objects on a worldmap by their
memberships in the given host group. Only members of the group will be shown on the worldmap.
You can start creating your own worldmap by using the way you use for other maps too. Select Options > Manage Maps, then fill the Create Map form while choosing Geographical map (interactive) from the map type dropdown and hit Create.
After opening the new map, you can pan and zoom to get the viewport you like, then choose Edit Map > Viewport > Save View to persist the current viewport as initial viewport in the current worldmap.
You can also create a new worldmap from an existing one by zoom and pan to create the viewport you like to use for your new worldmap, then choose Edit Map > Viewport > Save as new Map.
Parameter | Default | Description |
---|---|---|
min_zoom | 2 | Only show the object at specified zoom level or higher (more detailed view) |
max_zoom | 20 | Only show the object at specified zoom levels or lower (wider view) |
Parameter | Default | Description |
---|---|---|
scale_to_zoom | No | Scale the textbox size down to 50% for every zoom level below normal_size_at_zoom ,
or 50% up for every zoom level above.
|
normal_size_at_zoom | 19 | At this zoom level, the scale_to_zoom=yes textboxes are displayed at original 1:1 (100%) size. |