Recherche avancée

Sur d’autres sites (3446)

• What is Web Log Analytics and Why You Should Use It

  26 juin 2024, par Erin

  Can’t use JavaScript tracking on your website ? Need a more secure and privacy-friendly way to understand your website visitors ? Web log analytics is your answer. This method pulls data directly from your server logs, offering a secure and privacy-respecting alternative.  

  In this blog, we cover what web log analytics is, how it compares to JavaScript tracking, who it is best suited for, and why it might be the right choice for you. 

  What are server logs ? 

  Before diving in, let’s start with the basics : What are server logs ? Think of your web server as a diary that notes every visit to your website. Each time someone visits, the server records details like : 

  • User agent : Information about the visitor’s browser and operating system. 

  • Timestamp : The exact time the request was made. 

  • Requested URL : The specific page or resource the visitor requested. 

  These “diary entries” are called server logs, and they provide a detailed record of all interactions with your website. 

  Server log example 

  Here’s what a server log looks like : 

  192.XXX.X.X – – [24/Jun/2024:14:32:01 +0000] “GET /index.html HTTP/1.1” 200 1024 “https://www.example.com/referrer.html” “Mozilla/5.0 (Windows NT 10.0 ; Win64 ; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36” 

  192.XXX.X.X – – [24/Jun/2024:14:32:02 +0000] “GET /style.css HTTP/1.1” 200 3456 “https://www.example.com/index.html” “Mozilla/5.0 (Windows NT 10.0 ; Win64 ; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36” 

  192.XXX.X.X – – [24/Jun/2024:14:32:03 +0000] “GET /script.js HTTP/1.1” 200 7890 “https://www.example.com/index.html” “Mozilla/5.0 (Windows NT 10.0 ; Win64 ; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36” 

  192.XXX.X.X – – [24/Jun/2024:14:32:04 +0000] “GET /images/logo.png HTTP/1.1” 200 1234 “https://www.example.com/index.html” “Mozilla/5.0 (Windows NT 10.0 ; Win64 ; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36” 

  Breakdown of the log entry 

  Each line in the server log represents a single request made by a visitor to your website. Here’s a detailed breakdown of what each part means : 

  • IP Address : 192.XXX.X.X 
    • This is the IP address of the visitor’s device. 
  • User Identifier : – – 
    • These fields are typically used for user identification and authentication, which are not applicable here, hence the hyphens. 
  • Timestamp : [24/Jun/2024:14:32:01 +0000] 
  • • • The date and time of the request, including the timezone. 
  • Request Line : “GET /index.html HTTP/1.1” 
    • The request method (GET), the requested resource (/index.html), and the HTTP version (HTTP/1.1). 
  • Response Code : 200 
    • The HTTP status code indicates the result of the request (200 means OK). 
  • Response Size : 1024 
    • The size of the response in bytes. 
  • Referrer : “https://www.example.com/referrer.html“ 
    • The URL of the referring page that led the visitor to the current page. 
  • User Agent : “Mozilla/5.0 (Windows NT 10.0 ; Win64 ; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36” 
    • Information about the visitor’s browser and operating system. 

  In the example above, there are multiple log entries for different resources (HTML page, CSS file, JavaScript file, and an image). This shows that when a visitor loads a webpage, multiple requests are made to load all the necessary resources. 

  What is web log analytics ? 

  Web log analytics is one of many methods for tracking visitors to your site.  

  

  Web log analytics is the process of analysing server log files to track and understand website visitors. Unlike traditional methods that use JavaScript tracking codes embedded in web pages, web log analytics pulls data directly from these server logs. 

  How it works : 

  1. Visitor request : A visitor’s browser requests your website. 
  2. Server logging : The server logs the request details. 
  3. Analysis : These logs are analysed to extract useful information about your visitors and their activities. 

  Web log analytics vs. JavaScript tracking 

  JavaScript tracking 

  JavaScript tracking is the most common method used to track website visitors. It involves embedding a JavaScript code snippet into your web pages. This code collects data on visitor interactions and sends it to a web analytics platform. 

  

  Differences and benefits :
  

  Privacy : 

  • Web log analytics : Since it doesn’t require embedding tracking codes, it is considered less intrusive and helps maintain higher privacy standards. 

  • JavaScript tracking : Embeds tracking codes directly on your website, which can be more invasive and raise privacy concerns. 

  Ease of setup : 

  • Web log analytics : No need to modify your website’s code. All you need is access to your server logs. 

  • JavaScript tracking : Requires adding tracking code on your web pages. This is generally an easier setup process.  

  Data collection : 

  • Web log analytics : Contain requests of users with adblockers (ghostery, adblock, adblock plus, privacy badger, etc.) sometimes making it more accurate. However, it may miss certain interactive elements like screen resolution or user events. It may also over-report data.  

  • JavaScript tracking : Can collect a wide range of data, including Custom dimensions, Ecommerce tracking, Heatmaps, Session recordings, Media and Form analytics, etc. 

  Why choose web log analytics ? 

  Enhanced privacy 

  Avoiding embedded tracking codes means there’s no JavaScript running on your visitors’ browsers. This significantly reduces the risk of data leakage and enhances overall privacy. 

  Comprehensive data collection 

  It isn’t affected by ad blockers or browser tracking protections, ensuring you capture more complete and accurate data about your visitors. 

  Historical data analysis 

  You can import and analyse historical log files, giving you insights into long-term visitor behaviour and trends. 

  Simple setup 

  Since it relies on server logs, there’s no need to alter your website’s code. This makes setup straightforward and minimises potential technical issues. 

  Who should use web log analytics ? 

  Web log analytics is particularly suited for businesses that prioritise data privacy and security.

  Organisations that handle sensitive data, such as banks, healthcare providers, and government agencies, can benefit from the enhanced privacy.  

  By avoiding JavaScript tracking, these entities minimise data exposure and comply with strict privacy regulations like Sarbanes Oxley and PCI. 

  Why use Matomo for web log analytics ? 

  Matomo stands out as a top choice for web log analytics because it prioritises privacy and data ownership

  

  Here’s why : 

  • Complete data control : You own all your data, so you don’t have to worry about third-party access. 
  • IP anonymisation : Matomo anonymises IP addresses to further protect user privacy. 
  • Bot filtering : Automatically excludes bots from your reports, ensuring you get accurate data. 
  • Simple migration : You can easily switch from other tools like AWStats by importing your historical logs into Matomo. 
  • Server log recognition : Recognises most server log formats (Apache, Nginx, IIS, etc.). 

  Start using web log analytics 

  Web log analytics offers a secure, privacy-focused alternative to traditional JavaScript tracking methods. By analysing server logs, you get valuable insights into your website traffic while maintaining high privacy standards.  

  If you’re serious about privacy and want reliable data, give Matomo’s web log analytics a try.  

  Start your 21-day free trial now. No credit card required. 

  Try Matomo for Free

  21 day free trial. No credit card required.

  
  

  Your email address
  

  Your website address
  

  Your Analytics subdomain will be .matomo.cloud (change)

  Choose your analytics subdomain
  

  .matomo.cloud

• Start of video is not labeled as "0" in QuickTime Video from GoPro

  26 mars 2020, par John Terragnoli

  I’m trying to combine four GoPro videos into a single video, and then rotate it 90 degrees. However, the time scales on the bottom of the videos are all wrong. The videos are 17 minutes and 42 second. But the beginning time is labeled as 5:15:20:32 and the ending time is 5:33:01:32. It just looks really weird and I’d like to fix it. After I use ffmpeg to rotate and concatenate the videos, the problem persists. Could it possibly be fixed with Exiftool ?

  ffmpeg -safe 0 -f concat -i list.txt -vcodec copy -acodec copy merged_videos.MP4

  ffmpeg -i input.mov -vf "transpose=1" output.mov

  Here is the exiftool information on one of the videos :

  File Name                       : GOPR3023.MP4
  
  Directory                       : .
  
  File Size                       : 3.7 GB
  
  File Modification Date/Time     : 2018:04:12 14:56:16-05:00
  
  File Access Date/Time           : 2020:03:25 12:17:18-05:00
  
  File Inode Change Date/Time     : 2020:03:25 17:57:04-05:00
  
  File Permissions                : rwxrwxrwx
  
  File Type                       : MP4
  
  File Type Extension             : mp4
  
  MIME Type                       : video/mp4
  
  Major Brand                     : MP4 v1 [ISO 14496-1:ch13]
  
  Minor Version                   : 2013.10.18
  
  Compatible Brands               : mp41
  
  Movie Data Size                 : 4001979951
  
  Movie Data Offset               : 28
  
  Movie Header Version            : 0
  
  Create Date                     : 2018:04:12 14:38:32
  
  Modify Date                     : 2018:04:12 14:38:32
  
  Time Scale                      : 60000
  
  Duration                        : 0:17:42
  
  Preferred Rate                  : 1
  
  Preferred Volume                : 100.00%
  
  Preview Time                    : 0 s
  
  Preview Duration                : 0 s
  
  Poster Time                     : 0 s
  
  Selection Time                  : 0 s
  
  Selection Duration              : 0 s
  
  Current Time                    : 0 s
  
  Next Track ID                   : 6
  
  Firmware Version                : HD5.03.02.51.00
  
  Lens Serial Number              : NAH6092300301117
  
  Camera Serial Number Hash       : 34676f2cdf49b86a1514817a93377bf7
  
  Track Header Version            : 0
  
  Track Create Date               : 2018:04:12 14:38:32
  
  Track Modify Date               : 2018:04:12 14:38:32
  
  Track ID                        : 1
  
  Track Duration                  : 0:17:42
  
  Track Layer                     : 0
  
  Track Volume                    : 0.00%
  
  Image Width                     : 1920
  
  Image Height                    : 1080
  
  Graphics Mode                   : srcCopy
  
  Op Color                        : 0 0 0
  
  Compressor ID                   : avc1
  
  Source Image Width              : 1920
  
  Source Image Height             : 1080
  
  X Resolution                    : 72
  
  Y Resolution                    : 72
  
  Compressor Name                 : GoPro AVC encoder
  
  Bit Depth                       : 24
  
  Color Representation            : nclx 1 1 1
  
  Video Frame Rate                : 59.94
  
  Time Code                       : 3
  
  Balance                         : 0
  
  Audio Format                    : mp4a
  
  Audio Channels                  : 2
  
  Audio Bits Per Sample           : 16
  
  Audio Sample Rate               : 48000
  
  Text Font                       : Unknown (21)
  
  Text Face                       : Plain
  
  Text Size                       : 10
  
  Text Color                      : 0 0 0
  
  Background Color                : 65535 65535 65535
  
  Font Name                       : Helvetica
  
  Other Format                    : tmcd
  
  Warning                         : [minor] The ExtractEmbedded option may find more tags in the movie data
  
  Matrix Structure                : 1 0 0 0 1 0 0 0 1
  
  Media Header Version            : 0
  
  Media Create Date               : 2018:04:12 14:38:32
  
  Media Modify Date               : 2018:04:12 14:38:32
  
  Media Time Scale                : 60000
  
  Media Duration                  : 0:17:42
  
  Handler Class                   : Media Handler
  
  Handler Type                    : NRT Metadata
  
  Handler Description             : GoPro SOS
  
  Gen Media Version               : 0
  
  Gen Flags                       : 0 0 0
  
  Gen Graphics Mode               : srcCopy
  
  Gen Op Color                    : 0 0 0
  
  Gen Balance                     : 0
  
  Meta Format                     : fdsc
  
  Image Size                      : 1920x1080
  
  Megapixels                      : 2.1
  
  Avg Bitrate                     : 30.1 Mbps
  
  Rotation                        : 0

  Part 2
  There is a pretty obvious "stutter" at the 17:42 mark where the two clips are combined. I’ve tried using ffmpeg and iMovie, but both give the same results. The GoPro broke up the event into multiple clips on it’s own so it seems weird that there would be any information missing. Is there any way to get rid of this stutter ?

  Thanks !

• how to make cloud services for camera device iot monitoring and control

  16 novembre 2019, par guardian presence

  Looking to use ffmpeg to pull video trsp stream over tcp pass the video feeds to opencv for object recognition and tracking passing the output to ardunio serial control systems like alarm systems drones ardunio controlled lawn mores.

  Lets say some one has a cctv system and a drone laying around if they connect to my cloud the system can pull the stream from the cctv cameras pull the stream from the drone if object moves in on camera zone the cloud can control the drone to move to that zone and take a closer look at a face if face detected send alert return drone to docking . if ptz camera opencv tracking zooming to face

  if ros can turn into a cloud service need to know about hosting and
  building front end user login and device login.

  i’m a cctv installer new to programming and want to setup cloud login for camera iot devises were users can control and monitoring of devices from a central cloud