Recherche avancée

Sur d’autres sites (9128)

• Handling high volume traffic and traffic peaks with Matomo just got easier

  16 avril 2018, par Matomo Core Team

  When you use the self-hosted version of Matomo on-premise instead of the Matomo cloud-hosted solution, you may experience some traffic peaks on your Matomo server when the traffic volume on your websites increases. For example, every day at a certain time you might receive two or three times the amount of traffic that usually visits your website. This can have many negative impacts, including :

  • Slow loading time for your JavaScript tracker (piwik.js) which in turn may slow down your website giving your users a poor experience. Also you may see less page views in Matomo because by the time the tracker is loaded on your website, the user has already moved on to another page.
  • Some tracking requests might be simply ignored at some point because your server might not be able to handle any tracking requests anymore which results in many untracked visits and page views.
  • You may need additional servers only to handle traffic peaks which results in increased server costs, maintenance work and maintenance costs.

  The solution

  Handling traffic peaks has been possible with Matomo for years using the Queued Tracking plugin. When this feature is enabled, tracking requests are put into a queue instead of being processed immediately. Then when a job is running separately it takes the requests out of the queue and processes them. This brings various benefits.

  Faster tracking

  It improves the tracking speed on your server by a factor of 5 to 15. So for example, instead of a tracking request taking 50ms, it takes only 5ms. This means your server will be able to handle a lot more concurrent requests compared to the traditional tracking and is likely to survive traffics peaks much more likely without any trouble at all.

  Faster processing

  When a request is queued, the request still needs to be processed eventually. Because the Queued Tracking solution can take multiple tracking requests out of the queue at once and process them in one go, the processing speed increases massively as well. This is because by default each tracking request has to bootstrap Matomo and do a lot of things again and again which takes quite a bit of time (you’d be surprised). Instead, many things can now be cached and don’t have to be done multiple times. As a result, your server can process tracking requests much faster and needs less resources overall which in turn reduces cost and trouble.

  Queued Tracking is now easier to set up

  In the background, Queued Tracking has been using Redis, an in-memory database. While Redis is very fast, it’s not simple to setup and maintain it. Especially when it comes to making Redis “highly available” and when you need to scale your Redis. Also, your servers will need a lot more memory for Redis as all queued tracking requests are stored in memory.

  One click setup

  We have now added support for a MySQL database so you can activate Queued Tracking with a simple click. What used to take hours or maybe even weeks to set up and a lot of maintenance, can now be cut down to seconds. Queued Tracking will then simply reuse the database that you have been using all along for storing all your visits. A side benefit is that your server won’t need more memory and all queued tracking requests even survive a server reboot.

  Both Redis and MySQL are now supported in Queued Tracking. If you do have experience with managing Redis, we still recommend using this solution as it’s likely a bit faster. However, in most cases the MySQL solution should work just as well.

  Further improvements

  We have made various other improvements for Queued Tracking that increases the performance and you can now be notified when the number of queued tracking requests reaches a certain threshold. View the changelog for a list of all changes.

  Learn more

  We have been setting up Queued Tracking multiple times when it comes to high volume traffic or dealing with peaks and are amazed by the results. Often, we can even reduce the overall amount of needed servers.

  If this sounds like something that could be beneficial to you, we recommend you have a look at the Queued Tracking page and also check out the FAQ. You might be also interested in learning how to configure Matomo for speed.

  Need help with setting up, maintaining, or scaling Matomo ? Get in touch now.

  The post Handling high volume traffic and traffic peaks with Matomo just got easier appeared first on Analytics Platform - Matomo.

• Merge commit '10eb496d9ae94df6f792b0e1d8750738eb3a0952'

  11 novembre 2017, par James Almer

  Merge commit '10eb496d9ae94df6f792b0e1d8750738eb3a0952'
  * commit '10eb496d9ae94df6f792b0e1d8750738eb3a0952' :
  
    vaapi_mpeg2 : Convert to use coded bitstream infrastructure
  
    mpeg12 : Move finding the best frame rate to common code
  
    cbs_mpeg2 : Add support for picture display extension
  
    cbs_h265 : Fix ranges of prediction weight offsets
  
    cbs_h265 : Fix reading of unknown parameter set extension data
  
    vaapi_h264 : Fix CPB/DPB delays
  This commit is a noop, see
  
  94a4048619665e99a19d9e2961254dc9b5c736a7
  
  9b0c7aa0e446eceec96ba8f4009e004fad29fba3
  
  686e388bbb6aeef077095a83f84b53d143d44d63
  
  278c308ceae6b8d7bac1dfc24518821aae603988
  
  d8928ad6b6e899c409129c8e16b225c09a8a5abb
  Merged-by : James Almer <jamrial@gmail.com>
  

• Piwik SSO options and why is it useful ?

  8 novembre 2017, par Piwik Core Team — Plugins

  Bored with typing again and again different logins and passwords for each service you have access to ? Would you like to add hundreds or thousands of users with different roles to your Piwik at once ? Would you like to save time and effort of managing your users while increasing the security in your business ? Guess what, Piwik has come up with great features to do just that.

  But what is a SSO ?

  Before introducing you to new Piwik features, let me explain what a SSO is.
  SSO is the acronym for Single Sign On. As its name suggests this authentication process allows a user to access multiple applications with one set of login credentials.

  Advantages of using a SSO are numerous :

  • improving security, for example when an employee is leaving your company, how can you check that all his credentials have been removed ?
  • reducing employees time-wasters such as having to enter logins/passwords each time.
  • providing a centralized database for administrators. They can then easily manage permissions of all employees saving them heaps of time.
  • reduces support costs related to authentication / accounts management.

  In order to provide SSO options, two Piwik plugins have been developed and are available on the marketplace :

  • SAML
  • LDAP

  SAML

  

  SAML stands for “Security Assertion Markup Language”, it is a standard in order to exchange authentication and authorization between an identity provider (OneLogin, Okta, Ping Identity, ADFS, Google, Salesforce, SharePoint…) and a service provider.
  An identity provider is an online service that authenticates users on the Internet by using security tokens.

  Are you wondering if your business or organization is using any of these providers ? We recommend to ask your operations team or sysadmin.

  At InnoCraft, we developed a plugin in order to allow SSO with SAML for Piwik. It can ensure consistent access control across the enterprise and external providers, potentially reducing support costs related to authentication and accounts management.

  The installation process is straightforward. All you need is to get the SAML premium feature from the marketplace. Once installed, you will access the SAML configuration interface through the admin where you can configure various settings :

  • SAML Status
  • Identity Provider (Entity ID, SSO endpoint info, Public x509 certificate)
  • Just-in-time provisioning and Mapping attributes
  • Access Synchronization
  • Advanced settings

  

  From there you will need to follow our detailed documentation to have it up and running :
  https://piwik.org/docs/login-saml/.
  Once finished, you will then be able to use SAML to authenticate to your Piwik account :

  

  As all premium features, SAML is eligible to a 30-day period money back guarantee, so do not hesitate to have it a try.

  LDAP

  

  LDAP stands for Lightweight Directory Access Protocol. As its names implies LDAP is a directory, hosted on a server, which organizes the data about people in your company.
  Thanks to the LDAP plugin, Piwik can be connected to your LDAP infrastructure and then use all its power in order to give each individual an access with different rights according to their needs.

  Let’s say that you have 1,000 employees within a company and they all need right now an access to the analytics reports in Piwik with different roles. This is what LDAP can do.

  Moreover if your business or organization is already using LDAP, we recommend using the LDAP connector for Piwik for better security, to stop wasting time of your users and sysadmins, and to reduce the costs related to account management.

  You understood it well. LDAP is a plugin which saves a LOT of time within an organization. Here is a preview of the settings part :

  

  LDAP has been developed by the Piwik core team and is available as a Free plugin on the marketplace.

  Try it now within the marketplace

  If you are surprised by the possibilities that Piwik is offering in terms of plugins, the good news is that many other plugins are waiting for you on the marketplace. Check out our premium marketplace which offers state-of-the-art plugins to get the most out of Piwik.

  And if you are a developer feel free to create your own plugin, a detailed documentation is available at : https://developer.piwik.org/guides/getting-started-part-1.