Home · facebook/scribe Wiki Apache Logs Viewer | Analyze & View Apache/IIS Log Files Welcome to Apache Flume — Apache Flume crawling and indexing Webmaster Level: Intermediate to Advanced Including a rel=canonical link in your webpage is a strong hint to search engines your about preferred version to index among duplicate pages on the web. It’s supported by several search engines, including Yahoo!, Bing, and Google. While the webmaster sees the “red velvet” page on the left in their browser, search engines notice on the webmaster’s unintended “blue velvet” rel=canonical on the right. We recommend the following best practices for using rel=canonical:A large portion of the duplicate page’s content should be present on the canonical version. One test is to imagine you don’t understand the language of the content—if you placed the duplicate side-by-side with the canonical, does a very large percentage of the words of the duplicate page appear on the canonical page? Imagine that you have an article that spans several pages: example.com/article? rel=canonical from component pages to the view-all page Mistake 5: rel=canonical in the <body>
elasticsearch/logstash-forwarder Viewing live Apache logs with tail, grep and egrep Posted January 24th, 2010 in Apache There are times you may need to monitor what's happening on an Apache web server as is happens. This can be done from the command line using a combination of the tail command, which outputs the last part of a file, and grep or egrep which are used for regular expression pattern matching. Viewing everything If the log file to view is at /var/log/apache/myvirtualhost.log the first command below will show the last few lines from the file and then continue to echo to the command line as new lines are entered into the log file i.e. as additional requests are made to the web server. The -f flag is what makes the tail command output additional data as it is appended to the log. Viewing everything from a specific IP address Tail can be combined with grep to pattern match. This can be useful to only show results from your own requests. Viewing everything excluding a specific IP address Adding the -v flag to grep excludes the pattern. Excluding particular file types
Open sourcing Databus: LinkedIn's low latency change data capture system Co-authors: Sunil Nagaraj, Shirshanka Das, Kapil Surlaker We are pleased to announce the open source release of Databus - a real-time change data capture system. Originally developed in 2005, Databus has been in production in its latest revision at Linkedin since 2011. The Databus source code is available in our github repo for you to get started! What is Databus? LinkedIn has a diverse ecosystem of specialized data storage and serving systems. This leads to a need for reliable, transactionally consistent change capture from primary data sources to derived data systems throughout the ecosystem. As shown above, systems such as Search Index and Read Replicas act as Databus consumers using the client library. How does Databus work? Databus offers the following important features: Source-independent: Databus supports change data capture from multiple sources including Oracle and MySQL. As depicted, the Databus System comprises of relays, bootstrap service and the client library. Try it out
Riemann - A network monitoring system driskell/log-courier spotify/ffwd