Uploaded image for project: 'PuppetDB'
  1. PuppetDB
  2. PDB-3107

new-command-schema validation prevents PDB/NewRelic integration

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PDB 4.2.3.2
    • Component/s: None
    • Labels:
      None
    • Template:
    • Team:
      Systems Engineering
    • Story Points:
      2
    • Sprint:
      SE 2017-03-08
    • Release Notes:
      New Feature
    • Release Notes Summary:
      PuppetDB can now run in conjunction with the New Relic agent.

      Description

      This line:
      https://github.com/puppetlabs/puppetdb/blob/4.1.x/src/puppetlabs/puppetdb/command.clj#L169

      results in this error:

      13:25 <cyberious> ```2016-10-13 23:05:30,557 ERROR [o.a.a.ActiveMQMessageConsumer] ID:ip-10-11-47-46.sj.b2c.nike.com-45556-1476399900148-6:1:1:1 Exception while processing messag
      13:25 <cyberious> e: ID:ip-10-11-47-46.sj.b2c.nike.com-45556-1476399900148-8:1:1:1:4
      13:25 <cyberious> clojure.lang.ExceptionInfo: Input to parse-new-command does not match schema: [(named {:headers {:NewRelicID disallowed-key, :NewRelicTransaction disallowed-
      13:25 <cyberious> key, :JMSXDeliveryCount disallowed-key}} arg0)]```
      

      when PDB is run with the newrelic agent (supplied via java args). Instead of nailing down the exact schema we should just require the appropriate minimal set of keys/headers.

        Attachments

          Activity

            People

            • Assignee:
              russell.mull Russell Mull
              Reporter:
              wyatt Wyatt Alt
            • Votes:
              2 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support