You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Disabling SSL on local network with only one computer should speed up the logging, but after removing the option, logger stopped connecting to the client.
Version: 1.7.0 Cocoapods
let logger = LoggerInit()
let options:UInt32 = UInt32(kLoggerOption_BufferLogsUntilConnection | kLoggerOption_CaptureSystemConsole)
LoggerSetViewerHost(logger, "192.168.1.153" as NSString, 50000)
LoggerSetOptions(logger, options)
LoggerStart(logger)
Adding kLoggerOption_UseSSL to options solves to connection problem, but no logs messages appair. Adding kLoggerOption_BrowseBonjour to see log output.
let options:UInt32 = UInt32(kLoggerOption_BufferLogsUntilConnection | kLoggerOption_CaptureSystemConsole | kLoggerOption_UseSSL | kLoggerOption_BrowseBonjour)
We have a requirement to see both system console and external client app console log, but currently this seems to be force to only support one pipe.
let options:UInt32 = UInt32(kLoggerOption_LogToConsole | kLoggerOption_BufferLogsUntilConnection | kLoggerOption_CaptureSystemConsole)
Should log to both pipes, but currently LogToConsole flag disables functionality but should be opposite as adding the pipe.
Another option would be adding a new option kLoggerOption_LogToNetwork so both can be defined.
Also when my app sends 50 log lines a second, client app starts to hog the CPU. My late 2014 MacBook pros CPU went as high as 70%, which is unusually high for such a small task.
Otherwise, good work and thanks for the support 🥇
The text was updated successfully, but these errors were encountered:
Disabling SSL on local network with only one computer should speed up the logging, but after removing the option, logger stopped connecting to the client.
Version: 1.7.0 Cocoapods
Adding kLoggerOption_UseSSL to options solves to connection problem, but no logs messages appair. Adding kLoggerOption_BrowseBonjour to see log output.
We have a requirement to see both system console and external client app console log, but currently this seems to be force to only support one pipe.
Should log to both pipes, but currently LogToConsole flag disables functionality but should be opposite as adding the pipe.
Another option would be adding a new option kLoggerOption_LogToNetwork so both can be defined.
Also when my app sends 50 log lines a second, client app starts to hog the CPU. My late 2014 MacBook pros CPU went as high as 70%, which is unusually high for such a small task.
Otherwise, good work and thanks for the support 🥇
The text was updated successfully, but these errors were encountered: