EMS getLogData always returns empty infotable

[draskar]

Hi,

I'm testing some EMSs (one on my pc and some on GW devices) and every invocation of service getLogData returns me an empty infotable.

Of course the EMSs are logging on console and file.

I can't find anykind of configuration needed to read the logs via service.

Why it happens?

[draskar]

I noticed another issue in both EMS versions.

When the EMS encrypt the appKey it changes the name of the parameter from "appKey" to "appkey"

By doing this, our software (that manages dinamically the EMS config file) can't work anymore.

Can you please fix this meanwhile? 

[slangley]

Hi @draskar.

I have opened a case and you should be receiving confirmation containing the case number.  I will monitor the status and update the solution here once the issue has been resolved.  Please discuss the "appKey" case sensitivity issue with the engineer working your case. 

Regards.

--Sharon

[slangley]

Hi @draskar 

Apologies for the delay in responding to this--I have just returned from a 1-year temporary assignment.

The issue with appKey config.json setting being renamed appkey when encrypted during EMS startup has been addressed in EMS 5.5.0. The appKey token is now preserved after encryption (it was renamed appkey in 5.4.8).

Did you have any remaining concerns?  If this post answers your question, please mark it as the Accepted Solution for the benefit of others in the community.

Regards.

--Sharon