This check in string-script.cpp should check whether the first argument is > self.GetLength() rather than >= self.GetLength(). As it currently stands, one can not take a substring of the empty string (i.e. "".substring(0, 0) fails in icinga-script) or take an empty substring star

The first letter of Custom Variables is currently always a capital letter, regardless of the real spelling. This is very confusing, especially if users work with apply rules where custom variables should be case sensitive.

Example:

object Host "srv01.localdomain" {
  import "generic-host"

  address = "10.37.129.3"
  vars.checker = "srv02.localdomain"
  vars.role = "master"
}

Describe the bug
It seems that values from "total" columns are in the "known" columns. The HTML view is showing the correct values

Thruk Version
Thruk 2.33-20191129 - OMD 3.21~2019-11-29-labs-edition

To Reproduce
Steps to reproduce the behavior:

1. Create a report for yesterday with a timeperiod smaller than the whole day
2. create the report in XLS/CSV & HTML
3. The "known

Hi, we're using Nagstamon 3.3-20194015 on Windows x64 with Zabbix 4.0.9.
In Filters tab, we choosed to show only :

• All down hosts
• All warning services
• All average services
• All critical services
• All high services

When we modify settings to only show thats informations, we have "INFORMATIONS" status who arrived too.

![image](https://user-images.githubusercontent.com/2508208

In Version 1.3.6 the graph link is clickable within 100% of the column width.

Expected Behavior

The link is only clickable inside the graph

Current Behavior

I can click it outside of the graph

Possible Solution

Put the Link into a
<div style="display: inline-block;">

I really would like a change in the normal verbose mode. The first line should be the Plugin Command

OK/CRITICAL/WARNING/... <message>
the rest can be long text/verbose | plus perfdata

Right now the first line is always: I am a Cisco IOS Software... which makes the verbose mode unusable (most likely) for additional debug information in nagios/naemon/incigna.

This would have the nice

Sahi proxy requires one to import certificates generated by Sahi proxy.
Documentation only contains a sample for Firefox, but IE requires different actions.

Expected behaviour:
With hover_url on host or service object set to panel iframe URL (similar to http://play.grafana.org/d-solo/000000012/grafana-play-home?orgId=1&from=1575808514878&to=1575815714878&panelId=2 from play.grafana.org) a panel from grafana should be displayed on hover.

Problem:
On hover iframe with following error message is displayed:

If you're seeing this Grafana ha

I would like to suggest a description field.
A description field to give a description to a certificate. So you can specify for which the certificate is used. Sometimes the certificates have no meaningful names.

Expected Behavior

The Puppet master should query the Icinga 2 Master for a client's ticket.

Current Behavior

The Puppet module uses its own hashing function which might break if the Icinga 2's hashing algorithm is changed for tickets.

https://github.com/Icinga/puppet-icinga2/blob/master/lib/puppet/parser/functions/icinga2_ticket_id.rb

Possible Solution

Use the API action

Expected Behavior

Search should be case insensitive by default to be in line with normal icingaweb behaviour

Current Behavior

Search is case senitive

Your Environment

• Version/GIT-Hash of this module: d139cd0d797ca0fbc92b448dc17c5febcb9ac381
• Icinga Web 2 version: 2.7.2

Expected Behavior

If the eventstream.retry_interval configuration option is left out from the configuration I expect the program to either pick a reasonable default or abort with a useful error message.

Current Behavior

panic: non-positive interval for NewTicker

goroutine 47 [running]:
time.NewTicker(0x0, 0x

1. Use the documentation default configs on Ubuntu 18.04, eg:

class profile::icingaweb2 {
  contain ::icingaweb2
  contain ::icingaweb2::module::monitoring
  class { 'icingaweb2::module::monitoring':
    ido_host        => '127.0.0.1',
    ido_db_name     => 'db',
    ido_db_username => 'user',
    ido_db_password =>

$releasever should not be used, at least with the release RPMs.

Some distributions ship weird defaults here, examples:

• 7Server
• 7Client
• 6.5

refs #123

Describe the change

Only create single icinga services for NodePort (Like all other objects.)

Current situation

Currently an icinga service is made for each worker/NodePort service.

Should

Add a nodeport service via the kube cluster.

Additional context

Add any other context about the problem here.

Expected Behavior

Can we add border-left to each event row according to state of the check?

Current Behavior

Currently on selection the class "active" is applied which is default icinga-blue.

Possible Solution

Take check_result.vars_after.state as input for coloring border-left. This can be helpful in identifying result state in one view. Eg: icinga-red for state CRITICAL, icin