Data Feed Trigger

[SergeiBakhaev]

Hello everyone!

I have quite a lot of data feeds that runs every 5 minutes to keep up with data changes.

If I'm not wrong, in one of the FFTH I've heard something about service/app, that could listen for changes in Archer and trigger Data Feed.

Have anyone aware of this?

Best regards,

Sergei

[BodieMinster]

The activity taking place in that space is the construction of the cache file. This should take some time on the first execution, but should take much less time on subsequent runs. Does that match what you are observing?

[SergeiBakhaev]

As far as I can see, no change in subsequent runs.

For example, run after one that I've mentioned:

11.15.2018 09:07:00.725  :: INFO :: [LoggingInit] ::  Logging Initialized
11.15.2018 09:15:44.789  :: INFO :: DataFeedMonitor.CheckMonitors() ::  Checking criteria for monitor DF1 (A2A).
11.15.2018 09:15:46.356  :: INFO :: DataFeedMonitor.CheckMonitors() ::  Criteria not met.
11.15.2018 09:15:46.379  :: INFO :: DataFeedMonitor.CheckMonitors() ::  Checking criteria for monitor DF2 (A2A).
11.15.2018 09:15:47.288  :: INFO :: DataFeedMonitor.CheckMonitors() ::  Criteria not met.
11.15.2018 09:15:47.291  :: INFO :: DataFeedMonitor.CheckMonitors() ::  Checking criteria for monitor DF3 (A2A).
11.15.2018 09:15:48.333  :: INFO :: DataFeedMonitor.CheckMonitors() ::  Criteria not met.
11.15.2018 09:15:48.335  :: INFO :: DataFeedMonitor.CheckMonitors() ::  Checking criteria for monitor DF4 (A2A).
11.15.2018 09:15:49.385  :: INFO :: DataFeedMonitor.CheckMonitors() ::  Criteria not met.
11.15.2018 09:15:49.390  :: INFO :: DataFeedMonitor.CheckMonitors() ::  Checking criteria for monitor DF5 (A2A).
11.15.2018 09:15:50.373  :: INFO :: DataFeedMonitor.CheckMonitors() ::  Criteria not met.
11.15.2018 09:15:50.374  :: INFO :: DataFeedMonitor.CheckMonitors() ::  Checking criteria for monitor DF6 (А2А).
11.15.2018 09:15:52.266  :: INFO :: DataFeedMonitor.CheckMonitors() ::  Criteria met, executing feed D393B502-D97C-451D-A538-24C7FDA1FC39.‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Or more recent one:

11.16.2018 08:49:00.764  :: INFO :: [LoggingInit] ::  Logging Initialized
11.16.2018 08:57:37.526  :: INFO :: DataFeedMonitor.CheckMonitors() ::  Checking criteria for monitor DF1 (A2A).
11.16.2018 08:57:37.746  :: INFO :: DataFeedMonitor.CheckMonitors() ::  Criteria not met.
11.16.2018 08:57:37.746  :: INFO :: DataFeedMonitor.CheckMonitors() ::  Checking criteria for monitor DF2 (A2A).
11.16.2018 08:57:37.963  :: INFO :: DataFeedMonitor.CheckMonitors() ::  Criteria not met.
11.16.2018 08:57:37.964  :: INFO :: DataFeedMonitor.CheckMonitors() ::  Checking criteria for monitor DF3 (A2A).
11.16.2018 08:57:38.212  :: INFO :: DataFeedMonitor.CheckMonitors() ::  Criteria not met.
11.16.2018 08:57:38.212  :: INFO :: DataFeedMonitor.CheckMonitors() ::  Checking criteria for monitor DF4 (A2A).
11.16.2018 08:57:38.583  :: INFO :: DataFeedMonitor.CheckMonitors() ::  Criteria not met.
11.16.2018 08:57:38.584  :: INFO :: DataFeedMonitor.CheckMonitors() ::  Checking criteria for monitor DF5 (A2A).
11.16.2018 08:57:39.074  :: INFO :: DataFeedMonitor.CheckMonitors() ::  Criteria not met.
11.16.2018 08:57:39.075  :: INFO :: DataFeedMonitor.CheckMonitors() ::  Checking criteria for monitor DF6 (А2А).
11.16.2018 08:57:39.360  :: INFO :: DataFeedMonitor.CheckMonitors() ::  Criteria met, executing feed D393B502-D97C-451D-A538-24C7FDA1FC39.‍‍‍‍‍‍‍‍‍‍‍‍‍

By the way, is there an option to disable log entirely, or maybe change level from INFO to ERROR?

[Ilya_Khen]

Wow, that is really huge delay. And I assume you did provided cache path in the configuration without defining its name, right? 

It was so for me, when I defined it non-properly, the delay was about 1 minute, and dropped to 15 sec afterwards.

[SergeiBakhaev]

No, filename is defined. Both in app settings, and in monitors itself.

For example:

 <add key="cacheFileNameAndPath" value="C:\ArcherFiles\RSA Archer Data Feed Monitor\cache.txt" />

[Ilya_Khen]

Yeah, this is a mistake. Maybe in documentation. Drop the file name, leave only path.

 <add key="cacheFileNameAndPath" value="C:\ArcherFiles\RSA Archer Data Feed Monitor\" />

Then your first launch will be considered as cold, but the rest - warm.

[SergeiBakhaev]

Wow, this helped a lot.

11.16.2018 01:45:00.729  ::   INFO :: [LoggingInit] ::  Logging Initialized
11.16.2018 01:45:07.260  ::   INFO :: DataFeedMonitor.CheckMonitors() ::  Checking criteria for monitor DF1 (A2A).‍‍

Down from 7-8 minutes to 7 seconds.

[Ilya_Khen]

All props to Bodie Minster 

[BodieMinster]

I like this community. You guys are good people!

[Ilya_Khen]

Same here

[ShaunMartinLaw2]

Hey Bodie Minster, still attempting to get the Datafeed Monitor going on our environments, we have a case open currently with support, but thought I’d check with you, will the DF trigger kick off a convoy of referenced DFs successfully?