how to connect my own project with logExpert?

[ringchenhao]

Hi:
my project is written by C# .net40/48.I want to send my logs to logExpert, to be shown in the datagridview, but i can't find any userguide. I found "enimus" in menu "Plugins" ,and i can config IP and Port in that view,but it seems does not work.Is it used as socket client, or socket server?
Or maybe i should use LogexpertgRPCService.exe to implement my equirement? And how should i make it?

can anyone provide some detailed guidance？
thanks, very much

[Hirogen]

are you logging your logs to a logfile? you can just open it

[ringchenhao]

are you logging your logs to a logfile? you can just open it

My logfile exists, but it is constantly changing. My scenario is like this:
I have a main program that connects to a device through socket, and the logs between the two are stored in a file. I hope to monitor and display the content of this log in real-time through logExpert。

[Hirogen]

yeah you can, just open the logfile in Logexpert, it updates itself when a new line is added

[ringchenhao]

yeah you can, just open the logfile in Logexpert, it updates itself when a new line is added

That can work, but my log file is created by the main program when the connection between the program and the device is established. So i need to implement this is the code, you konw, automated，not manual operation

[Hirogen]

as long as the log is written in a separated file, it wont matter, for logexpert, just open the separated log file in logexpert in your are good to go

[ringchenhao]

as long as the log is written in a separated file, it wont matter, for logexpert, just open the separated log file in logexpert in your are good to go

-_-！ But my boss disagrees with this solution. He wants me to use gRPC to implement communication between the program and LogExpert, passing each log message to LogExpert and displaying them one by one on the LogExpert.

[Hirogen]

Currently Logexpert does not support, messages received via grpc

[ringchenhao]

Currently Logexpert does not support, messages received via grpc

yeah,that's right. I tried to write a grpc client and connect it to Logexpert and call the function LoadFilesAsync ，and only get a result of true, it does not really load the filename i set.

public override Task<FilesReply> LoadFiles(FileNames fileNames, ServerCallContext context)
{
    return Task.FromResult(new FilesReply { Success = true });
}

[ringchenhao]

Currently Logexpert does not support, messages received via grpc

Is there a development plan for this feature?
Additionally, I want to confirm something with you. The reason my boss doesn’t agree to directly open files and use LogExpert to monitor them is that he believes this method lacks the real-time capability compared to gRPC. Is there really such a significant difference ?

[Hirogen]

grpc communication between logexperts will be added, but grpc communication from external currently not

I'm also not sure, why it must be grpc in your use case, its easier to just log it in a text file, grpc seems a little bit overkill for logging

[ringchenhao]

grpc communication between logexperts will be added, but grpc communication from external currently not

I'm also not sure, why it must be grpc in your use case, its easier to just log it in a text file, grpc seems a little bit overkill for logging

"its easier to just log it in a text file" I agree with you, but my boss may be placing greater emphasis on real-time performance

[TheNicker]

My main original intention when going into this project lately was to introduce ETW as a LogExpert data source using a common interface.
Currently LogExpert only knows the concept of file(s).
A file is might be interpreted as a a special case of a "Data Source".

My idea is to refactor out file load into a special case of data source and implement more data sources as plugins, including but not limited to gRpc syslog and ETW.

For that matter, I began refactoring LogFileReader.cs, but due to limited resources, I would probably need help with that.

If this has enough interest, we could discuss implementation details in Discord

Probably should open an issue/ feature request for it. @Hirogen , thoughts ?