...
- Payloads capturing is not supported
- Payloads are not being sent
- Payloads capture in DPOD has errors Payloads are sent but or filtered out in DPOD
- Payloads fully collected and in DPOD but still not appears
For each reason you should perform different checks.
...
- 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>/. this are 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 size 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