Best practice

Tip of the Month

Here you will find our monthly tips to improve your OTRS, i-doit, SNAG-View and NeDi configuration. If you need support in setting up your systems or need special adaptations, then simply contact us at +49 441 390 10 10 40 or send us an e-mail, we will be happy to advise you.

More than 100 customers from all areas of business and public administration trust our software solutions and services.

Monitor HPE Nimble Storage

2023-02-27 11:57

In the current tip of the month, we describe how you can monitor HPE Nimble Storage using SNAG-View.

You can currently monitor the following parameters:

Array
Hardware
Volumes

Installation:

The plugin nimble.pl must be copied to libexec-customer

Necessary Perl modules:

perl-Types-Serialiser
perl-JSON-XS
perl-common-sense

As an API user, a "read" user must be set up in the HPE storage.

Checkcommand:

$USER2$/nimble.pl --mode $ARG1$ --hostname $HOSTADDRESS$ --port 5392 --api-username {nimbel_user} --api-password '{nimbel_pass}' --insecure

By Michael Rütten, (comments: 0)

29 Apr

SNAG-View Application Monitoring

With SNAG-View, application monitoring can be set up very easily and very comprehensively!

Using the ticket system Znuny as an example, we show you how deeply you can monitor an application.

By Michael Rütten, (comments: 0)

28 Nov

Edit LDAP-Filter-String in i-doit manually

If you do not wish to include all Active Directory users in i-doit, you can restrict said users via filters. Previously, the configuration of the LDAP filter could only be achieved by using the Filter Builder.

Starting from i-doit Version 31, the filter string can be edited directly.

(comments: 0)

02 May

Own $USERX$ macros for SNAG-View 3

Additional placeholders for the path to plugins ($USERXXX$) can be integrated very easily in SNAG-View. The following steps are necessary for this:

A new <item> entry must be created in the "resource_cfg.xml".

Note: Be careful not to change or delete existing <item> entries.

Example:

Beispiel $User3$

We currently ship two predefined macros: "$USER1$ and $USER2$". After the change, the macro $USER3$ is available for the path /var/lib/nagios/libexec-customer2.

The script "/usr/bin/createNagiosCfg.sh" is then executed, so that the configuration is saved and saved in the resource.cfg.