log-analysis

Plot negative values in logarithmic scale with ggplot 2

痞子三分冷 提交于 2019-11-30 19:05:30
问题 I need to plot with ggplot2 package in R a graph with some negative values using an x logarithmic scale. For example I want to plot these points using an x logarithmic scale x <- c(-1,-10,-100) y <- c(1,2,3) I know that the logarithm of a negative value in R pronuces a NA value, but I need a result like this:click to view the picture Is it possible usign ggplot2? 回答1: There are two problems to solve - calculate log from negative values and then combine logarithmic scale and reverse scale. To

How to display azure app service's web server log on Azure log Analytics?

邮差的信 提交于 2019-11-29 10:04:17
I have an api application hosted on azure App services. For the web server log (iis logs) I've turned on web server logging from Azure portal. Look at the screenshot below. For storing web server logging Server Logs are allowed to be stored on the Azure blob containers only. As per the configuration the logs are stored on blob container as expected. Now I want to use these logs to be displayed on Azure Log Analytics. I've the following storage configurations on Log Analytics in Azure Web portal. On Log Analytics explorer I can view logs from all other sources except the web server (iis logs).

Is writing server log files to a database a good idea?

牧云@^-^@ 提交于 2019-11-27 11:06:11
After reading an article about the subject from O'Reilly , I wanted to ask Stack Overflow for their thoughts on the matter. Write locally to disk, then batch insert to the database periodically (e.g. at log rollover time). Do that in a separate, low-priority process. More efficient and more robust... (Make sure that your database log table contains a column for "which machine the log event came from" by the way - very handy!) I'd say no, given that a fairly large percentage of server errors involve problems communicating with databases. If the database were on another machine, network

Is writing server log files to a database a good idea?

六眼飞鱼酱① 提交于 2019-11-26 17:59:32
问题 After reading an article about the subject from O'Reilly, I wanted to ask Stack Overflow for their thoughts on the matter. 回答1: Write locally to disk, then batch insert to the database periodically (e.g. at log rollover time). Do that in a separate, low-priority process. More efficient and more robust... (Make sure that your database log table contains a column for "which machine the log event came from" by the way - very handy!) 回答2: I'd say no, given that a fairly large percentage of server