WEBVTT

1
00:00.000 --> 00:03.920
To wrap up this set of videos regarding the 40 Analyzer, I'd like to pose a

2
00:03.920 --> 00:04.400
scenario.

3
00:04.400 --> 00:08.510
And here it is. We have a customer that's using 40 Analyzer, but they feel that

4
00:08.510 --> 00:08.640
, like,

5
00:08.640 --> 00:12.950
when they use 40 view as part of 40 Analyzer, it's not showing all the real-

6
00:12.950 --> 00:13.840
time data that's

7
00:13.840 --> 00:17.740
being sent from the 40 gates. Now, my question for you, and if we are

8
00:17.740 --> 00:19.280
consulting with this customer,

9
00:19.280 --> 00:23.330
the question for us is, how would we explain that to the customer? What would

10
00:23.330 --> 00:24.160
we say? Why is it

11
00:24.160 --> 00:28.600
the customer may not be seeing all that information in the prebuilt 40 view

12
00:28.600 --> 00:29.840
dashboards, as well as the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

13
00:30.240 --> 00:34.910
prebuilt 40 view monitors? So take a moment right now, pause the video, think

14
00:34.910 --> 00:36.240
about why that may be

15
00:36.240 --> 00:39.890
the case, and then when you're ready, go ahead and click on resume and we'll

16
00:39.890 --> 00:41.200
discuss it together.

17
00:41.200 --> 00:49.460
All right, so regarding why the customer may not see all the data, one is we

18
00:49.460 --> 00:50.880
may have 40

19
00:50.880 --> 00:54.560
firewalls that are not sending the data. And when data is being sent over to

20
00:54.560 --> 00:55.840
the 40 Analyzer,

21
00:55.840 --> 00:59.260
the first thing we're doing at the 40 Analyzer is we're receiving those, and we

22
00:59.260 --> 01:00.080
're saving those
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

22
00:59.260 --> 01:00.080
're saving those

23
01:00.080 --> 01:04.240
in a dot log extension. And we can view those right then under log view.

24
01:04.240 --> 01:05.840
However, it's not until

25
01:05.840 --> 01:10.060
that data gets injected or inserted into the SQL database, where we can start

26
01:10.060 --> 01:10.800
using the full

27
01:10.800 --> 01:14.700
functionality and seeing that information in the 40 view dashboards and also

28
01:14.700 --> 01:16.160
the 40 view monitors.

29
01:16.160 --> 01:20.170
So that next step would be insert into SQL. And that could be a reason that

30
01:20.170 --> 01:20.960
they're not seeing it

31
01:20.960 --> 01:25.980
yet in 40 view is because the insert hasn't happened yet on the 40 Analyzer

32
01:25.980 --> 01:27.440
itself. So whether the

33
01:27.440 --> 01:31.680
40 gates aren't sending the data over in the first place, or we have not waited
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

33
01:27.440 --> 01:31.680
40 gates aren't sending the data over in the first place, or we have not waited

34
01:31.680 --> 01:32.400
long enough

35
01:32.400 --> 01:35.930
for it to be inserted into the SQL database, those are two great reasons that

36
01:35.930 --> 01:37.040
information would not

37
01:37.040 --> 01:40.810
show up in 40 view. So thanks for joining me in this set of videos and I look

38
01:40.810 --> 01:41.520
forward to seeing

39
01:41.520 --> 01:45.470
you my friend in another set very, very soon until then, I hope this has been

40
01:45.470 --> 01:46.240
informative,

41
01:46.240 --> 01:49.040
and I'd like to thank you for viewing.

42
01:49.040 --> 01:58.280
[BLANK_AUDIO]