.net - Reliable(durable) distributed logging engine -
Trying to find business logging structures for distributed systems. This setting has to allow .NET applications to be logged on a remote server, which can then be collected in the central location. If possible, the central location should store messages in a SQL Server database.
Requirements:
- Be able to initiate the entry of messages on a remote server, even if the network bar prevents the instant messaging message for central location < Li> Removing messages at a central location, in order to prevent any degradation in the performance of ASP.NET applications or web services, should be controlled by any other process than running the .NET application.
- The final delivery of messages for the central location assures that when the remote server is rebooted in the event of a network reboot, the logging message should be distributed until the remote server and normal network conditions were restored Go.
Perhaps a very simple solution can continue to write local logs and log on to a server You can create a separate process to republish, you can log in using a public subscription message bus, or several options including MSMK.
Using a different solution like writing a typical lodge 4 net adapter is definitely an option, but it may be in coupling / dependency problems, so considering the actual deployment environment for adoption needed.
Comments
Post a Comment