Details

    • Type: Change Request
    • Status: Open
    • Priority: Trivial
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None

      Description

      It would be great if macro functions were permitted across a wider scope than just inside of trigger-based/problem-update notifications and expressions, map labels and graph names.

      In this way, you could use item values inside of other items or as user macros.

      For instance, I have a HTTP agent check which given some Basic Auth credentials returns a secret key. I would like to be able to use that secret key as the input to the value of a HTTP header in another HTTP agent check. Therefore I would like to be able to use a value likeĀ {{HOST.HOST}:MySecretKey.last()} as my input.

      Allowing a wider scope of execution for these macro functions would achieve this, but I can imagine it would also open the doors for much more interesting things than just this.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              adamc Adam Carrgilson
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: