Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Export Event Profiles by ID and Type

    Use this API to export a specific event profile to an XML file.

    URI

    https://[host]/api/juniper/servicenow/event-profile-management/eventProfiles/{id}/export/ {type} (HTTP method = GET)

    URI Parameters

    Parameter

    Type

    Required

    Description

    id

    Integer

    Yes

    ID of the event profile whose data is to be exported

    type

    String

    Yes

    Type of file to which the event profile data is to be exported

    In this release, you can export data only in the XML format.

    Consumes

    None

    Produces

    An XML file containing the event profile data is output.

    Response Elements

    Element

    Type

    Description

    profileName

    String

    Name of the event profile

    description

    String

    Description of the event profile

    scriptsEnabledCount

    Integer

    Number of scripts enabled in the event profile

    scriptsDisabledCount

    Integer

    Number of scripts disabled in the event profile

    createdBy

    String

    Entity that created the event profile

    The value is always set to Service Now.

    bundle

    String

    Specifies details such as name and version of the script bundle to which the event profile belongs

    event

    String

    Specifies details such as description, category, KB article, and AI-Script bundle ID associated with the event profile

    Sample Output

    Sample XML Output

    <event-profiles>
      <event-profile>
        <profileName>Base_Profile_4_1R4_1</profileName>
        <description>Base Profile for Bundle Version: 4.1R4.1</description>
        <scriptsEnabledCount>2</scriptsEnabledCount>
        <scriptsDisabledCount>0</scriptsDisabledCount>
        <createdBy>Service Now</createdBy>
        <bundle>
          <name>jais-4.1R4.1-signed.tgz</name>
          <version>4.1R4.1</version>
        </bundle>
        <events>
          <event>
            <activateDescription>Capture ACCT_MALLOC_FAILURE Events</activateDescription>
            <briefDescription>ACCT_MALLOC_FAILURE</briefDescription>
            <category>PFED</category>
            <eventDescription>The accounting statistics process could not allocate memory from the heap.</eventDescription>
            <expressRMA>false</expressRMA>
            <featureName>ACCT_MALLOC_FAILURE.slax</featureName>
            <fileName>ACCT_MALLOC_FAILURE.slax</fileName>
            <helpText>ACCT_MALLOC_FAILURE</helpText>
            <kbURL>KB18749</kbURL>
            <minimumVersion>9.4</minimumVersion>
            <name>ACCT_MALLOC_FAILURE</name>
            <priority>3</priority>
            <scriptId>47</scriptId>
            <subType>Memory Consumption</subType>
            <type>Resource Exhaustion</type>
          </event>
          <event>
            <activateDescription>Capture ACCT_XFER_POPEN_FAIL Events</activateDescription>
            <briefDescription>ACCT_XFER_POPEN_FAIL</briefDescription>
            <category>ACCT</category>
            <eventDescription>A call to the popen() function failed when the accounting statistics process invoked the indicated command to transfer the indicated file.</eventDescription>
            <expressRMA>false</expressRMA>
            <featureName>ACCT_XFER_POPEN_FAIL.slax</featureName>
            <fileName>ACCT_XFER_POPEN_FAIL.slax</fileName>
            <helpText>ACCT_XFER_POPEN_FAIL</helpText>
            <kbURL>KB18750</kbURL>
            <minimumVersion>9.4</minimumVersion>
            <name>ACCT_XFER_POPEN_FAIL</name>
            <priority>3</priority>
            <scriptId>263</scriptId>
            <subType>Communication Error</subType>
            <type>Software Failure</type>
          </event>events>
      </event-profile>
    </event-profiles>

    Modified: 2016-08-10