• Recent
    • Tags
    • Popular
    • Register
    • Login

    Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

    Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website Mango 5 Documentation Website

    HTTP Sender Data Format

    Mango Automation general Discussion
    2
    2
    915
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • nallenscottN
      nallenscott
      last edited by

      Hello,

      I am trying to configure an HTTP publisher to send data to a Splunk Cloud instance. The publisher can successfully transmit static test data to Splunk, but live data is not formatted correctly. See the Format events for HTTP Event Collector documentation, under "Event metadata" and "Event parsing". Is it possible to reformat the outgoing data from Mango to match the format that Splunk is expecting?

      1 Reply Last reply Reply Quote 0
      • phildunlapP
        phildunlap
        last edited by phildunlap

        Hi nallenscott,

        The format of the HTTP publisher is not modifiable. You can add static parameters, but that's it.

        What is available is the HttpBuilder script utility. see: https://help.infiniteautomation.com/about-mango-java-script or the contextual help for scripting within Mango. There are a few example uses around the forum: https://www.google.com/search?q=site%3A%2F%2Fforum.infiniteautomation.com+httpbuilder&oq=site%3A%2F%2Fforum.infiniteautomation.com+httpbuilder

        You could do this in a script that is triggered on context update. The only downside here would be the HTTP Publisher is expecting a 200 OK back or it will attempt to publish the value again later, but you could script that if you required it by storing the update in some JavaScript list within the script.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post