Casting variables in Sentinel Log Manager

Question

Hello! I have been trying to make a collector work to pick up events
from MySQL tables and when I run it on SIEM-Sentinel (classic Sentinel
6.1 on SQL Server and Sentinel-RD ), it works fine. However, I tried
using the same collector on Sentinel Log Manager 1.2, and it does not
pick up the events!
After some debugging, I found the culprit lines of code. I do a lot of
casting to make sure the variables are treated as integers or strings
(mostly when I need to manipulate it as a number, since String is the
default data type, I think) so I have lines that look like this in the
pre-parsing stage of the collector:
this.anInteger = Number ( this.RXmap.col_anInteger);
this.aString = String (this.RXmap.col_aString);
But when debugging, while in SIEM-Sentinel it populates the variable as
expected, in SLM I get "NaN" as the output value. I can see the values I
want to get in RXBufferString, but problem occurs when I cast them.
Maybe this isn't the "Sentinel" way of doing it? While I can do without
casting "String", how can I cast the value as an integer?
Any help is appreciated. Cheers!
Jean-Paul_GM
Jean-Paul_GM's Profile: http://forums.novell.com/member.php?userid=12809
View this thread: http://forums.novell.com/showthread.php?t=447842

Answer 1

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Compare your Sentinel and Log Manager systems' inputs on that line of
code. I'm going to guess that the value in those variables which you
are trying to cast are not the same, causing the problem. NaN shouldn't
be the output if the input can be cast, but I'd also probably avoid
casting the value in the first place since I'm pretty sure that Sentinel
and Log Manager will handle that casting as necessary later (untested,
just assuming from a lack of having ever needed to do that myself in the
past, though I am not an expert collector writer). ECMAscript is not
strongly typed and while I've had issues in one cases where the type was
incorrect it was not a simple string/int type but rather a Date object
that the send() function expected to be present but was in fact not a
valid Date and so the sending failed while everything else (parsing,
etc.) seemed to function properly.
Also whenever you get [Object Object] in the debugger you should be able
to move over to the left-hand side where either 'this' or 'locals' will
show you something that allows you to drill down to the object and then
you can expand it. I do not think I have ever seen a case where the
object existed but could not be accessed as something listed directly
as, or as a child of, something present on the left-hand side section of
the debugger.
Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJOt9tGAAoJEF+XTK08PnB5ohAP/2kW6O2lEI1EDi1XDAKSRTkD
FzCx7WL8ReEXlf0nqEY+KDQAakPOG6h2MqG0fgVzSy1ty/OopF2UYX1QteI+gq/A
+DmlgWa+Os3GOvxZPOjpPg2diWHazZmADVdm0NesGwUrSWLJ4t tTCMDYlME3yIDF
3T8rSd76s40FEZTxlKqYuvGg1T863pGrCb1Ul7PC52VmkrI0p+ gxWqJjIap0nTRF
+DXYHsn9WHJT+OBy7icF1MMYT/arjmNyuVUV4leGpRWkLYVSQJEomn/W7OO7oO0v
uRm9uZ2iNUiigyf/u07BSpyvkQSPCo8ICGeYc5zYb8LoExVu2vH1LA70CoVXzfIZ
RJfQeW6KIVQHeOB10kGt/gjxvsFGsjJ5q3tmiRN33r8fJpE5QZ3hDfBA3qBdcjYz
/dSR+jbLNSpGBG8dvkl9y4JRLEAUgcKAX+OYpY/I0/W4lsZvfcU/Yp8dR41qJDlk
Cp2Ds2vnk4gCUZKqdp0/jMBLxvc8ZZ4XW8oxlsAEOGbOL9pBU57txxIiPOfYV8MR
f0Ylo5yWdQYcLqYgqsWE1z0JRSW18DQz7EtsazMjhS3PuuvVF5 xpc9LUJfeAj7zY
0gYCE4keDH8ljFQZ9v+DrSBhpZnOLDDndKBtC8pk3ahCVnhKPN olxviCliOmUJsB
WeGiUoMtJJks66JkUsmP
=OD70
-----END PGP SIGNATURE-----