Recherche avancée

Sur d’autres sites (7713)

• 5 questions you should ask yourself before defining a custom alert in Matomo

  24 janvier 2018, par InnoCraft

  In Matomo, you can create Custom Alerts to automatically be notified of important changes on your website or app. They are a great way to save time, but they also spam your mailbox quickly. Defining good custom alerts takes therefore time and requires some preparations. Here are recommendations on what you should focus on to only get the right alerts at the right time.

  There are several questions you should ask yourself before you define a custom alert :

  1. Do you really want to be alerted ? If the answer is no, then do not use this feature.
  2. What is the level of this alert ? Not important, interesting, highly critical… if it is not highly critical, do not define an alert for this. Probably the emailing report or custom reports feature will be a better fit.
  3. How would you like to be alerted ? SMS, email, sound, homing pigeon (unfortunately we do not support this feature at that time). If you are looking at your emails once a week, then defining a daily email alert won’t make sense.
  4. How would you like the alert to be named ? Give your alert the most explicit name, that’s the first information you will see when you get alerted.
  5. What will be the next step once the alert is triggered ? If you cannot find any action once the alert is triggered, then probably an alert doesn’t make sense.

  Once those questions are answered, you can start configuring custom alerts. There are many alerts you can define but as just mentioned, which alerts you should create always depends on your goals and what is critical to you, or your business. Let’s look at some custom alerts that we see quite often.

  No visit

  One of the easiest custom alert to define. You probably want to be alerted if your website did not receive any visit. As this alert is highly critical, you will want to receive an e-mail, even an SMS. This alert will trigger only if the number of visits is below 1 on a daily basis :

  

  Here the action we will take is to have a look at the website in order to see if it is still live. If the site still works, we will look at the tracking code in order to see if the website is still correctly tracked or not.

  Convinced of this custom alert ? Let’s look at another example.

  Target achieved

  Let’s say you gave a goal to one of your employee to reach a specific threshold in terms of conversions. You can then define a custom alert in order to inform you when the threshold has been reached.

  You can simply do this with an alert saying “Target achieved by Franck” where number of conversions equals the number of actions you defined with him. It takes you only a minute to define something you would have missed otherwise.

  

  Here the actions we can think of are either to congratulate Franck or to ask him what is going wrong if the target is not achieved.

  Did you know that you can also take advantage of Matomo premium features to define custom alerts ? Let’s see one of them.

  Lost SEO ranking

  If you are using the Search Engine Keyword Performance premium feature, there are really interesting combinations you can use to create custom alerts.
  For example, you can be notified when a specific keyword lost or reached a position :

  

  You will be alerted when your website is losing some positions within the search engine results for specific keywords. Here the action we could take is to investigate why we lost a position on Google for this keyword.

  There are many custom alert combinations waiting for you out there. Why not giving them a try ? If you have any questions, feel free to ask them on the Matomo forums.

  The post 5 questions you should ask yourself before defining a custom alert in Matomo appeared first on Analytics Platform - Matomo.

• Capture ffmpeg's metadata output in powershell

  17 mars 2016, par xdhmoore

  I’m trying to capture the output of ffmpeg in PowerShell(tm) to get some metadata on some ogg & mp3 files. But when I do :

  ffmpeg -i file.ogg 2>&1 | sls GENRE

  The output includes a bunch of lines without my matching string, "GENRE" :

        album_artist    : Post Human Era
  
        ARTIST          : Post Human Era
  
        COMMENT         : Visit http://posthumanera.bandcamp.com
  
        DATE            : 2013
  
        GENRE           : Music
  
        TITLE           : Supplies
  
        track           : 1
  
  At least one output file must be specified

  I am guessing something is different in the encoding. ffmpeg’s output is colored, so maybe there are color control characters in the output that are breaking things ? Or, maybe ffmpeg’s output isn’t playing nicely with powershell’s default UTF-16 ? I can’t figure out if there is another way to redirect stderr and remove the color characters or change the encoding of stderr.

  EDIT :
  Strangely, I also get indeterminate output. Sometimes the output is as shown above. Sometimes with precisely the same command the output is :

        GENRE           :

  

  Which makes slightly more sense, but is still missing the part of the line I care about (’Music’).

  Somewhere powershell is interpreting something as newlines that is not newlines.

• Capture ffmpeg's metadata output in powershell

  17 janvier 2021, par xdhmoore

  I'm trying to capture the output of ffmpeg in PowerShell(tm) to get some metadata on some ogg & mp3 files. But when I do :

  



  ffmpeg -i file.ogg 2>&1 | sls GENRE


  



  The output includes a bunch of lines without my matching string, "GENRE" :

  



        album_artist    : Post Human Era
      ARTIST          : Post Human Era
      COMMENT         : Visit http://posthumanera.bandcamp.com
      DATE            : 2013
      GENRE           : Music
      TITLE           : Supplies
      track           : 1
At least one output file must be specified


  



  I am guessing something is different in the encoding. ffmpeg's output is colored, so maybe there are color control characters in the output that are breaking things ? Or, maybe ffmpeg's output isn't playing nicely with powershell's default UTF-16 ? I can't figure out if there is another way to redirect stderr and remove the color characters or change the encoding of stderr.

  



  EDIT :
Strangely, I also get indeterminate output. Sometimes the output is as shown above. Sometimes with precisely the same command the output is :

  



        GENRE           :


  



  

  



  Which makes slightly more sense, but is still missing the part of the line I care about ('Music').

  



  Somewhere powershell is interpreting something as newlines that is not newlines.