Adobe campaign Classic - Monitoring on Interaction and offers using Linux command

[somasundaramh]

Hi all,

I want to be able to monitor offers and interactions using linux command something like below:

nlserver monitor interactions

reference link: Monitoring processes | Adobe Campaign

And want to know what are the possible data that will be available when we use this command to monitor offers and interactions.

Thanks,

Somasundaram

[Jonathon_wodnicki · Accepted solution]

Hi,

You can read proposition logs with SOAP calls to xtk:queryDef#ExecuteQuery on the marketing instance, e.g.

curl -4 \
	-X POST 'https://REDACTED/nl/jsp/soaprouter.jsp' \
	-H 'Content-Type: application/soap+xml; action=xtk:queryDef#ExecuteQuery; charset=utf-8' \
	-H 'SOAPAction: xtk:queryDef#ExecuteQuery' \
	-H 'Cookie: __sessiontoken=___ebee5af9-f41b-433a-8429-978ca8e255db' \
	-H 'X-Security-Token: @N6jXYmfjqZppiOKdrJjamfmR_kwfTFgQfoYYA1Sac8mpyTDkN22PFvWZb6_585tFdmgUEuJsLaeYdsoLbvIUAmv1QNE9jC-a87WGP5HBmc4=' \
	-H 'Host: REDACTED' \
	--data-binary @- <<SOAP
<?xml version='1.0'?>
<SOAP-ENV:Envelope xmlns:xsd='http://www.w3.org/2001/XMLSchema'
  xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
  xmlns:ns='urn:xtk:queryDef'
  xmlns:SOAP-ENV='http://schemas.xmlsoap.org/soap/envelope/'>
  <SOAP-ENV:Body>
    <ExecuteQuery xmlns='urn:xtk:queryDef' SOAP-ENV:encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'>
      <__sessiontoken xsi:type='xsd:string'></__sessiontoken>
      <entity xsi:type='ns:Element' SOAP-ENV:encodingStyle='http://xml.apache.org/xml-soap/literalxml'>
        <queryDef firstRows="true" lineCount="200" operation="select" schema="nms:propositionRcp" xtkschema="xtk:queryDef">
          <select>
            <node expr="@eventDate" label="Event date"/>
            <node expr="offer" label="Offer"/>
            <node expr="@rank" label="Ranking"/>
            <node expr="@weight" label="Weight"/>
            <node expr="@status" label="Status"/>
            <node expr="@id"/>
          </select>
          <where>
            <condition expr="[@offerSpace-id] = 5744"/>
          </where>
          <orderBy>
            <node expr="@eventDate" sortDesc="true"/>
          </orderBy>
        </queryDef>
      </entity>
    </ExecuteQuery>
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
SOAP

Here a filter for offer space is applied. The select and where clauses can be altered as desired (consult nms:proposition schema), or a having clause added to count status above a threshold.

Heartbeat calls can also be made to the Interaction service itself to check that it's answering requests, alongside standard monitoring checking nlserver and its dependencies are running and available.

Thanks,

-Jon