Versions Compared

Old Version 6

changes.mady.by.user Hanan Kenan

Saved on

compared with

New Version 7

changes.mady.by.user Hanan Kenan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  •  Make sure DPOD WS-M agent is up and running - Check System Services Status with the CLI . It should be up and running.
  •  Make sure DPOD WS-M agent is green. this means that keep alive message are processed. perform tasks appears at Check System Status Using the Web Console
  •  

    Go to WS-M logs and see if there any exceptions. logs shouls be accessed using Telnet . path is /logs/wsmAgents/<Agent-name>/agent-flume_<Agent-name>.log. 

  •  

    This is how good log records should appears:
    11/10/XXXX 08:26:03,477- INFO o.m.a.f.h.NHttpFileServer [I/O-dispatch-2] wsmHttpSource1 Incoming entity content (bytes): 2908. ← an actual arrive payload
    11/10/XXXX 08:26:10,166- INFO o.m.a.f.h.NHttpFileServer [I/O-dispatch-3] wsmHttpSource1 Incoming entity content (bytes): 2220.  ← size 2220 means usually keep alive message

  •  

    If you see any exception contact support. you can look for one by search for ERROR  (with a space before and after).

  •  In some cases DPOD will filtered out messages because of there sizes. please see the following technote WS-M Payloads are not displayed

Payloads fully collected in DPOD but still not appears

This is cause because of bad synchronixation of time and timezones between IDG and DPOD.

  •  You should see your transaction in DPOD but without payload under Investigate → Transaction.
  •  You will be able too see your payload if you go to DPOD Web console → Manage → Internal Health → Store → puh button on high right corner called ES-Head.
  •  In ES-Head click on "Browser" tab and scroll down and in your left look for Types. Few rows below you will see wdpWsm so click on it and it will be marked
    Image Added
  •  Now, below a title Fields and a list of fields . scroll down until  you see transaction-id. please type your transaction id
    Image Added
  •  Now scroll up to the toip - you will see your payload. click on it and see a JSON.
    Image Added
  •  In the JSON look for a fields start-time
    "start-time": "1476237603"

    this is an epoch time. use an online epoch converter and you will have the time of payload and you should compare it to those of the transaction as appear in Inestigate:
    Image Added

  •  if there are not the same you should or not within 5 minutes than adjust time and timezones in IDG and DPOD. You should configure both IDG and DPOD to the same NTP as best practice.