[APP][Pro] Simple (Sys) LOG - Use this app for Simple (Sys) Logging

Apps
, , , ,
182

Yes

183

Hi Arie

I found a bug in the syslog level setting of the app (v3.0.3).

When I set the client to level info, it still sends the debug message to the syslog server…

image
image477×548 21.2 KB

Syslog

[2023-05-11T16:26:36.557277] Incoming log entry; input='<151>1 2023-05-11T16:26:36.719Z HP23 dingz 17775 - - DingzApp > onInit()\x0a', msg='0x7fbcf562a000', rcptid='0'
[2023-05-11T16:26:36.565911] Incoming log entry; input='<151>1 2023-05-11T16:26:36.719Z HP23 dingz 17775 - - DingzApp > onInit()\x0a', msg='0x7fbcf562a280', rcptid='0'
[2023-05-11T16:26:36.732371] Incoming log entry; input='<150>1 2023-05-11T16:26:36.725Z HP23 dingz 17775 - - dingz - v1.2.5 is started\x0a', msg='0x7fbcf562a500', rcptid='0'
[2023-05-11T16:26:36.793818] Incoming log entry; input='<151>1 2023-05-11T16:26:36.843Z HP23 dingz 17775 - - DingzSwitchDriver > onInit()\x0a', msg='0x7fbcf562a780', rcptid='0'
[2023-05-11T16:26:36.794267] Incoming log entry; input='<151>1 2023-05-11T16:26:36.843Z HP23 dingz 17775 - - DingzSwitchDriver > onInit()\x0a', msg='0x7fbcf562aa00', rcptid='0'
[2023-05-11T16:26:36.863690] Incoming log entry; input='<143>1 2023-05-11T16:26:37.060Z HP23 dingz 17775 - - DingzDevice::Dev-Dingz+ > HttpAPI > Initialized\x0a', msg='0x7fbcf562ac80', rcptid='0'
[2023-05-11T16:26:36.863806] Incoming log entry; input='<143>1 2023-05-11T16:26:37.060Z HP23 dingz 17775 - - DingzDevice::Dev-Dingz+ > HttpAPI > Initialized\x0a', msg='0x7fbcf562af00', rcptid='0'
[2023-05-11T16:26:36.868044] Incoming log entry; input='<143>1 2023-05-11T16:26:37.066Z HP23 dingz 17775 - - DingzDevice::Dev-Dingz+ > onInit()\x0a', msg='0x7fbcf562b180', rcptid='0'
184

And will it send the levels that are higher?
Perhaps i have wrong check for level, since the highest level is 0 and the lowest (debug) is 7.
So perhaps i have the condition wrong.

185

G’day Arie,

New problem. When I send via the API debug log message to the SimpleLog app, (only) the debug message, are sent twice to the syslog server, in SimpleLog they are displayed only once.

Chris

Console:

image
image1268×65 6.26 KB

SimpleLog:

image
image849×176 23.5 KB

Syslog server log:

[2023-05-12T05:39:40.357651] Incoming log entry; input='<151>1 2023-05-12T05:39:40.094Z HP23 dingz 17775 - - DingzApp > onInit()\x0a', msg='0x7f9593e2f000', rcptid='0'
[2023-05-12T05:39:40.360152] Incoming log entry; input='<151>1 2023-05-12T05:39:40.094Z HP23 dingz 17775 - - DingzApp > onInit()\x0a', msg='0x7f9593e2f280', rcptid='0'
[2023-05-12T05:39:40.393488] Incoming log entry; input='<150>1 2023-05-12T05:39:40.109Z HP23 dingz 17775 - - dingz - v1.2.5 is started\x0a', msg='0x7f9593e2f280', rcptid='0'
[2023-05-12T05:39:40.433058] Incoming log entry; input='<151>1 2023-05-12T05:39:40.322Z HP23 dingz 17775 - - DingzSwitchDriver > onInit()\x0a', msg='0x7f9593e2f280', rcptid='0'
[2023-05-12T05:39:40.433396] Incoming log entry; input='<151>1 2023-05-12T05:39:40.322Z HP23 dingz 17775 - - DingzSwitchDriver > onInit()\x0a', msg='0x7f9593e2f280', rcptid='0'
[2023-05-12T05:39:40.465595] Incoming log entry; input='<151>1 2023-05-12T05:39:40.410Z HP23 dingz 17775 - - DingzSwitchDriver > driver ready\x0a', msg='0x7f9593e2f280', rcptid='0'
[2023-05-12T05:39:40.465842] Incoming log entry; input='<151>1 2023-05-12T05:39:40.410Z HP23 dingz 17775 - - DingzSwitchDriver > driver ready\x0a', msg='0x7f9593e2f280', rcptid='0'
186

I just update BLL and Simple (Sys) Log: When sending logs to a Sysloc server, the date is now in localized UTC style:
2023-05-12:09:14:12.334+02:00
This resolves the “wrong” dates in IETF / rfc5424.

187

Found the bug: This happends after changing a device-settings and pressing save.
Solving it now.

188

Okay, both issues are resolved: When changing device-settings, the old level was keept, creating double messages and not allowing to really change the log-severity.

Update to 3.0.5.
Also update BLL.

189

Okay, one more update: Update SSL and BLL.

190

The debug logs are sent only once.

BUT,

The time in the syslog message is wrong, “2023-05-12T08 Uhr:41:41.576+02:00” is output.

The info logs are no longer displayed at log level debug. It should be like this Log-Level “Debug” all logs from SEVERITY 0 to 7, Log-Level “info” SEVERITY 0 to 6, and so on.

// Log-Level Debug
[2023-05-12T06:41:41.318502] Incoming log entry; input='<151>1 2023-05-12T08 Uhr:41:41.576+02:00 HP23 dingz 29339 - - DingzApp > onInit()\x0a', msg='0x7f9593e35000', rcptid='0'
[2023-05-12T06:41:41.365486] Incoming log entry; input='<151>1 2023-05-12T08 Uhr:41:41.722+02:00 HP23 dingz 29339 - - DingzSwitchDriver > onInit()\x0a', msg='0x7f9593e35000', rcptid='0'
[2023-05-12T06:41:41.397412] Incoming log entry; input='<151>1 2023-05-12T08 Uhr:41:41.757+02:00 HP23 dingz 29339 - - DingzSwitchDriver > driver ready\x0a', msg='0x7f9593e35000', rcptid='0'

// Log-Level Info
[2023-05-12T06:56:52.937003] Incoming log entry; input='<151>1 2023-05-12T08 Uhr:56:53.279+02:00 HP23 dingz 29339 - - DingzApp > onInit()\x0a', msg='0x7f9593e12000', rcptid='0'
[2023-05-12T06:56:52.964323] Incoming log entry; input='<150>1 2023-05-12T08 Uhr:56:53.322+02:00 HP23 dingz 29339 - - dingz - v1.2.5 is started\x0a', msg='0x7f9593e12280', rcptid='0'
[2023-05-12T06:56:53.003819] Incoming log entry; input='<151>1 2023-05-12T08 Uhr:56:53.353+02:00 HP23 dingz 29339 - - DingzSwitchDriver > onInit()\x0a', msg='0x7f9593e12500', rcptid='0'
[2023-05-12T06:56:53.039879] Incoming log entry; input='<151>1 2023-05-12T08 Uhr:56:53.391+02:00 HP23 dingz 29339 - - DingzSwitchDriver > driver ready\x0a', msg='0x7f9593e12780', rcptid='0'
191

@cgHome

Please send a screen shot from the BLL settingsscreen with HH format in it?

image
image407×614 36.8 KB

And update BLL to 3.2.6 to resolve it (after printscreen please :wink: ).

192

image
image390×505 24.6 KB

1 Like
193

@cgHome What is you locale?

194

Solved in 3.0.7.
Live now.

195

image

After the BLL update it now looks like this…

[2023-05-12T07:40:31.734689] Incoming log entry; input='<151>1 2023-05-12T09:40:32.039+02:00 HP23 dingz 29339 - - DingzApp > onInit()\x0a', msg='0x7fe92de2b000', rcptid='0'
[2023-05-12T07:40:31.762397] Incoming log entry; input='<150>1 2023-05-12T09:40:32.076+02:00 HP23 dingz 29339 - - dingz - v1.2.5 is started\x0a', msg='0x7fe92de2b280', rcptid='0'
[2023-05-12T07:40:31.793897] Incoming log entry; input='<151>1 2023-05-12T09:40:32.110+02:00 HP23 dingz 29339 - - DingzSwitchDriver > onInit()\x0a', msg='0x7fe92de2b500', rcptid='0'
[2023-05-12T07:40:31.833549] Incoming log entry; input='<151>1 2023-05-12T09:40:32.145+02:00 HP23 dingz 29339 - - DingzSwitchDriver > driver ready\x0a', msg='0x7fe92de2b780', rcptid='0'```
1 Like
196

The log levels also seem to work now:

// Log-Level: info
[2023-05-12T07:52:57.216171] Incoming log entry; input='<150>1 2023-05-12T09:52:57.349+02:00 HP23 dingz 29995 - - dingz - v1.2.5 is started\x0a', msg='0x7f327d40d000', rcptid='0'

// Log-Level: debug
[2023-05-12T07:55:52.040100] Incoming log entry; input='<151>1 2023-05-12T09:55:52.338+02:00 HP23 dingz 29995 - - DingzApp > onInit()\x0a', msg='0x7f327d40d000', rcptid='0'
[2023-05-12T07:55:52.075817] Incoming log entry; input='<150>1 2023-05-12T09:55:52.383+02:00 HP23 dingz 29995 - - dingz - v1.2.5 is started\x0a', msg='0x7f327d40d000', rcptid='0'
[2023-05-12T07:55:52.096163] Incoming log entry; input='<151>1 2023-05-12T09:55:52.407+02:00 HP23 dingz 29995 - - DingzSwitchDriver > onInit()\x0a', msg='0x7f327d40d000', rcptid='0'
[2023-05-12T07:55:52.115194] Incoming log entry; input='<151>1 2023-05-12T09:55:52.427+02:00 HP23 dingz 29995 - - DingzSwitchDriver > driver ready\x0a', msg='0x7f327d40d000', rcptid='0'
1 Like
197

Any idea when you find the time to work on the cadd - script", @Arie_J_Godschalk?
Since more and more users are switching to the new HP23 it would be very helpfull to add SimpleLOG cards to each normal flow too, in case HP23 doesn’t act as expected… :slight_smile:

198

Well, all i can say is ASAP.
Sorry :wink:

1 Like
199

No need to say sorry , Arie!
Thanks for all your effort!

1 Like
200

Hey @Ronwell,

Please use the Forum or ticket system instead of Reviews to communicate, since a review gives me absolutly no information on how to solved the issue.

So, in the review you say you need to restart the SSL app to get into the Log or you get an error message?
And you need to do this every time?
When you get the Error that BLL is not started, please send me a diagnostic of SSL and BLL (before restarting the apps), so i can find and solve the issues.

1 Like
201

Please let me know the Locale in the BLL App Settings.
Because the Uhr should have been in HH format.
I have resolved it, but wanna see if there are more stuff in there that might mess up formatting.