Starting with December 2020 release of MC2 the EQL Rest requests are being executed without running an EJM Task. The requests are executed in MC2 Load Balancer instance, without involving the EJM engine which is running in MC2 Worker instances. This results in the EQL Rest request not being reflected in the EJM Tasks window in Message Center Console.
The default configuration provided with MC2 will add the EQL Rest request execution information to the database so that it shows in Message Center Console in:
...
This can be controlled by changing the MC2 configuration file. The estar/tpe/dynamic/mc2/cfg/extractservice.yml file can be created to change the configuration for all instances of MC2 in a region. The configuration parameters should be in the extractservice-lb section. The default configuration is:
| Code Block |
|---|
--- |
...
spring: |
...
profiles: extractservice-lb |
...
application: |
...
name: extractservice-lb |
...
eagle.eaglemlrestapi.services.EQL.directexecution: true |
...
eagle.pyservice.executors: 4 |
...
eagle.eaglemlrestapi.services.EQL.messagedetails.level: errorsonly |
...
eagle.eaglemlrestapi.services.EQL.tasks: true |
...
eagle.eaglemlrestapi.services.EQL.filestatistics: true |
NOTE: The --- is important and has to be added as shown to the configuration file. Only one extractservice-lb section should be defined in the configuration file.
...