[dev.icinga.com #12799] Log Macro warnings for command arguments?

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/12799

Created by mfrosch on 2016-09-26 11:42:33 +00:00

Assignee: (none)
Status: New
Target Version: (none)
Last Update: 2016-09-26 11:42:41 +00:00 (in Redmine)

Backport?: Not yet backported
Include in Changelog: 1

---

We encountered an interesting problem regarding macro resolving in command arguments.

When a macro for an argument can not be resolved, or macros in the macro, the full argument is dropped. Here is an example with a typo in "notifcation".

The problem is that we can't really log an error about it at the moment, because this would log an error for every argument that is not used/present.

Is there a way to properly tell the user the macro is invalid?

object NotificationCommand "sms-service-notification" {
  import "plugin-notification-command"

  command = [ SysconfDir + "/icinga2/scripts/sendsms.pl" ]

  arguments = {
    //...
    "-m" = {
      value = "$sms_service_message$"
    }
  }

  //...
  vars.sms_service_message = "$notifcation.type$: $host.name$ - $service.name$ is $service.state$: $service.output$"
}

[icinga-migration]

Updated by mfrosch on 2016-09-26 11:42:41 +00:00

• Priority changed from Normal to Low

[gunnarbeutner]

I don't think there's anything we can do here.