The Government Wants You and Your Search Logs Too

Whether your privacy deserves a better search engine. Steven Levy explained in his article: "Do you want them to save your dreams?" Save search logs for future use, not as anonymous as people think. Internet users think that their search is personal, but the reverse is understood. Steven Wyer's article "Living with the Big Brothers: Government's Footprints in Each Tweet" shows that the government is being advertised about people's search logs and their causes. Levy and Wyer agree that using social media formats society's privacy is compromised and both authors use similar strategies such as language, logos, sorrows, etc. to move viewers to their respective perspectives Did.

There is no problem with the file that captures the log and records it on the disk, but it can not be expanded. If you want to search logs across multiple servers and applications, you need to send all logs to the central repository. There are many log management solutions to help solve this problem. Alternatively, you can set your own Elastic Search cluster. If you want to query all the files on the disk, consider using VisualLogParser. With NLog you can create a data dictionary that can be used as an attribute of a log record. This is useful if you set the customer name to the context and then include that name in all logging statements. Since each transaction has a different customer name, I do not want to set it to global scope. To do this, use the mapping diagnostic context (MDC).

Log service for centralized logging. This is Elastic Stack, Slack, Graylog, and other similar products. To handle large amounts of data, you need a logging stack with a powerful parser / visualizer. Part of the infrastructure can be one of these services and each host in the environment is configured to forward log files on behalf of each service. It tracks the definition of the ID and enables the location of all logs in all micro services that process a single external request. The idea here is to generate a unique ID for each external request entering the micro service and pass that ID to the internal micro service call processing that request. Therefore, by searching for a single tracking ID, you can find all micro service calls generated by a single external access.