Recherche avancée

Sur d’autres sites (5207)

• Secure and track every change to your Matomo installation with the Activity Log plugin

  14 novembre 2017, par InnoCraft — Plugins

  Are you wondering how your colleagues are using Matomo (Piwik) ? Would you like to know if an unauthorized user got an access to your installation ? Would you like to remember the last actions you performed in Matomo some weeks ago ? At InnoCraft, we developed a plugin called “Activity Log”. With this feature you can easily track and check all major changes to your Matomo websites, for example : user permissions, goals, and funnels. In this article we will show you the different ways you can use it and explain why it is an invaluable plugin.

  Activity log for better security

  The activity log feature has been designed for security. Also referred to as “audit logging” or “audit trail”, with this plugin you will be able to :

  1. detect any suspicious actions
  2. detect hacker attacks
  3. help identify performance problems
  4. see clearly who did what, and when
  5. find out how people are using Matomo (Piwik) within your company

  1 – detect any suspicious actions

  With audit trail you can easily identify if a former employee still has access to your Matomo (Piwik) installation. You will then be able to know when he accessed it for the last time, and what changes she or he performed. If you got hacked, you will be able to find out if the user created, changed, or deleted any website, goals, or did anything else suspicious.

  2 – detect hacker attacks

  When an unregistered user is trying to access your Matomo (Piwik), each failed login attempt is registered within the Activity Log report.

  3 – help identify performance problems

  Activity Log can help you identify performance problems by registering the sequence of each major action a user performed. For example, if a user updated or installed a third party plugin, and suddenly Matomo (Piwik) is getting performance problems, then it is likely that the plugin update caused it.

  4 – see clearly who did what, and when

  It is always challenging in an organization to know who did what and when. With Activity Log, you will know who were the employee(s) that accessed Matomo (Piwik), created, updated, or deleted a goal, a funnel, a scheduled report, and much more.

  5- find out how people are using Matomo within your company

  By having a look at how people are using Matomo (Piwik) you will have an overview of how your colleagues use Matomo. For example, you can see who is creating Custom segments to analyse the audience in more details, who is creating funnels to learn where your users drop off. You will then be able to identify who has the knowledge and who needs training.

  Did you know ?

  You can help the Matomo (Piwik) core team make Matomo even better by sharing anonymously how you use Matomo on a day to day basis. You just need to install the following plugin : http://plugins.matomo.org/AnonymousPiwikUsageMeasurement

  What’s in it ?

  Once downloaded and installed from the marketplace, you will be able to access the activity log from the admin panel within the diagnostic section :

  

  If you are logged as a super user administrator, you will get an overview and a detailed report about who accessed Matomo (Piwik) and which actions they performed.

  Those reports are critical as they allow the super user to :

  • ensure users are following all documented procedures within your organization such as naming conventions for reports, using the right settings when adding measurables…
  • identify suspicious behavior. As those reports are gathering all major Matomo (Piwik) users activities it is easy to identify non conventional behavior.
  • replay the sequence some users went through in order to fix any potential issues.

  Activity log view report you can access through the admin panel

  So you will see in a second if an unusual user got access to Matomo (Piwik) and the different actions the user performed.
  It is also a good way to see the features that your users are using and identify potential misuse.

  As a regular user or admin, activity log is providing only the historical actions that this user performed :

  

  Actions listed in the log include any changes (add, edit, delete) to the following features (this is a non exhaustive list) :

  • Annotation
  • Custom Alert
  • Custom Dimension
  • Goal
  • Privacy settings
  • Scheduled report
  • Segment
  • User
  • Website
  • …

  This is a ideal to remember the actions they previously performed some weeks/months ago.

  Where can I start from here ?

  Activity log is a premium feature you can acquire through the Matomo (Piwik) marketplace. If you want to experience it before purchasing it, you can try it for free on our cloud infrastructure.

  I want to try the Activity Log plugin

  Activity log is just one out of the many great premium features developed by InnoCraft, the company founded by the creators of Matomo. Discover all their special plugins through the premium marketplace.

   

• FFMPEG- H.264 encoding BGR image data to YUP420P video file resulting in empty video

  22 septembre 2022, par Cogentleman

  I'm new to FFMPEG and trying to use it to do some screen capture to a video file, but after a lot of online searching I am stumped as to what I'm doing wrong. Basically, I've already done the effort of capturing screen data via DirectX which stores in a BGR pixel format and I'm just trying to put each frame in a video file. There's two functions, setup which does all the ffmpeg initialization work, and addImage which is called in the main program loop and puts each buffer of BGR image data into a video file. The technique I'm doing for this is to make two frames, one with the BGR data and one with YUP420P (doesn't need to be the latter but after a lot of trial and error it was all I was able to get working with H.264), and use sws_scale to copy data between the two, and then send that frame to video.mp4. The file seems to be having data written to it successfully (the file size grows and grows as the program runs), but when I try and view it in VLC I see nothing- indeed, VLC fails to fetch a length of the video, and bringing up codec and media information both are empty. I turned on ffmpeg verbose logging but all that is spit out is the following :

  


  Setting default whitelist 'Epu��'
Timestamps are unset in a packet for stream -1259342440. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
Encoder did not produce proper pts, making some up.


  


  From what I am reading, I understand this to be warnings rather than errors that would totally corrupt my video file. I separately went through all the error codes being spit out and everything seems nominal to me (zero for success for most calls, -11 sometimes for avcodec_receive_packet but the docs indicate that's expected sometimes).

  


  Based on my understanding of things as they are, this should be working, but isn't, and the logs and error codes give me nothing to go on, so someone with experience with this I reckon would save me a ton of time. The code is as follows :

  


  VideoService.h

  


  #ifndef VIDEO_SERVICE_H&#xA;#define VIDEO_SERVICE_H&#xA;&#xA;extern "C" {&#xA;#include <libavcodec></libavcodec>avcodec.h>&#xA;#include <libavformat></libavformat>avformat.h>&#xA;#include <libavutil></libavutil>imgutils.h>&#xA;#include <libswscale></libswscale>swscale.h>&#xA;}&#xA;&#xA;class VideoService {&#xA;    public:&#xA;        void setup();&#xA;        void addImage(unsigned char* data, int lineSize, int width, int height, int align);&#xA;    private:&#xA;        AVCodecContext* context;&#xA;        AVFormatContext* formatContext;&#xA;        AVFrame* bgrFrame;&#xA;        AVFrame* yuvFrame;&#xA;        AVStream* videoStream;&#xA;        SwsContext* swsContext;&#xA;};&#xA;&#xA;#endif&#xA;

  


  VideoService.cpp

  


  #include "VideoService.h"
#include 

void FfmpegLogCallback(void *ptr, int level, const char *fmt, va_list vargs)
{
    FILE* f = fopen("ffmpeg.txt", "a");
    fprintf(f, fmt, vargs);
    fclose(f);
}

void VideoService::setup() {
    int result = 0;
    av_log_set_level(AV_LOG_VERBOSE);
    av_log_set_callback(FfmpegLogCallback);
    bgrFrame = av_frame_alloc();
    bgrFrame->width = 1920;
    bgrFrame->height = 1080;
    bgrFrame->format = AV_PIX_FMT_BGRA;
    bgrFrame->time_base.num = 1;
    bgrFrame->time_base.den = 60;
    result = av_frame_get_buffer(bgrFrame, 1);
    yuvFrame = av_frame_alloc();
    yuvFrame->width = 1920;
    yuvFrame->height = 1080;
    yuvFrame->format = AV_PIX_FMT_YUV420P;
    yuvFrame->time_base.num = 1;
    yuvFrame->time_base.den = 60;
    result = av_frame_get_buffer(yuvFrame, 1);
    const AVOutputFormat* outputFormat = av_guess_format("mp4", "video.mp4", "video/mp4");
    result = avformat_alloc_output_context2(
        &formatContext,
        outputFormat,
        "mp4",
        "video.mp4"
    );
    formatContext->oformat = outputFormat;
    const AVCodec* codec = avcodec_find_encoder(AVCodecID::AV_CODEC_ID_H264);
    result = avio_open2(&formatContext->pb, "video.mp4", AVIO_FLAG_WRITE, NULL, NULL);
    videoStream = avformat_new_stream(formatContext, codec);
    AVCodecParameters* codecParameters = videoStream->codecpar;
    codecParameters->codec_type = AVMediaType::AVMEDIA_TYPE_VIDEO;
    codecParameters->codec_id = AVCodecID::AV_CODEC_ID_HEVC;
    codecParameters->width = 1920;
    codecParameters->height = 1080;
    codecParameters->format = AVPixelFormat::AV_PIX_FMT_YUV420P;
    videoStream->time_base.num = 1;
    videoStream->time_base.den = 60;
    result = avformat_write_header(formatContext, NULL);
    
    codec = avcodec_find_encoder(videoStream->codecpar->codec_id);
    context = avcodec_alloc_context3(codec);
    context->time_base.num = 1;
    context->time_base.den = 60;
    avcodec_parameters_to_context(context, videoStream->codecpar);
    result = avcodec_open2(context, codec, nullptr);
    swsContext = sws_getContext(1920, 1080, AV_PIX_FMT_BGRA, 1920, 1080, AV_PIX_FMT_YUV420P, 0, 0, 0, 0);
}

void VideoService::addImage(unsigned char* data, int lineSize, int width, int height, int align) {
    int result = 0;
    result = av_image_fill_arrays(bgrFrame->data, bgrFrame->linesize, data, AV_PIX_FMT_BGRA, 1920, 1080, 1);
    sws_scale(swsContext, bgrFrame->data, bgrFrame->linesize, 0, 1080, &yuvFrame->data[0], yuvFrame->linesize); 
    result = avcodec_send_frame(context, yuvFrame);
    AVPacket *packet = av_packet_alloc();
    result = avcodec_receive_packet(context, packet);
    if (result != 0) {
        return;
    }
    result = av_interleaved_write_frame(formatContext, packet);
}


  


  My environment is windows 10, I'm building with clang++ 12.0.1, and using the FFMPEG 5.1 libs.

  


• Secure and track every change to your Piwik installation with the Activity Log plugin

  14 novembre 2017, par InnoCraft — Plugins

  Are you wondering how your colleagues are using Piwik ? Would you like to know if an unauthorized user got an access to your installation ? Would you like to remember the last actions you performed in Piwik some weeks ago ? At InnoCraft, we developed a plugin called “Activity Log”. With this feature you can easily track and check all major changes to your Piwik websites, for example : user permissions, goals, and funnels. In this article we will show you the different ways you can use it and explain why it is an invaluable plugin.

  Activity log for better security

  The activity log feature has been designed for security. Also referred to as “audit logging” or “audit trail”, with this plugin you will be able to :

  1. detect any suspicious actions
  2. detect hacker attacks
  3. help identify performance problems
  4. see clearly who did what, and when
  5. find out how people are using Piwik within your company

  1 – detect any suspicious actions

  With audit trail you can easily identify if a former employee still has access to your Piwik installation. You will then be able to know when he accessed it for the last time, and what changes she or he performed. If you got hacked, you will be able to find out if the user created, changed, or deleted any website, goals, or did anything else suspicious.

  2 – detect hacker attacks

  When an unregistered user is trying to access your Piwik, each failed login attempt is registered within the Activity Log report.

  3 – help identify performance problems

  Activity Log can help you identify performance problems by registering the sequence of each major action a user performed. For example, if a user updated or installed a third party plugin, and suddenly Piwik is getting performance problems, then it is likely that the plugin update caused it.

  4 – see clearly who did what, and when

  It is always challenging in an organization to know who did what and when. With Activity Log, you will know who were the employee(s) that accessed Piwik, created, updated, or deleted a goal, a funnel, a scheduled report, and much more.

  5- find out how people are using Piwik within your company

  By having a look at how people are using Piwik you will have an overview of how your colleagues use Piwik. For example, you can see who is creating Custom segments to analyse the audience in more details, who is creating funnels to learn where your users drop off. You will then be able to identify who has the knowledge and who needs training.

  Did you know ?

  You can help the Piwik core team make Piwik even better by sharing anonymously how you use Piwik on a day to day basis. You just need to install the following plugin : http://plugins.piwik.org/AnonymousPiwikUsageMeasurement

  What’s in it ?

  Once downloaded and installed from the marketplace, you will be able to access the activity log from the admin panel within the diagnostic section :

  

  If you are logged as a super user administrator, you will get an overview and a detailed report about who accessed Piwik and which actions they performed.

  Those reports are critical as they allow the super user to :

  • ensure users are following all documented procedures within your organization such as naming conventions for reports, using the right settings when adding measurables…
  • identify suspicious behavior. As those reports are gathering all major Piwik users activities it is easy to identify non conventional behavior.
  • replay the sequence some users went through in order to fix any potential issues.

  Activity log view report you can access through the admin panel

  So you will see in a second if an unusual user got access to Piwik and the different actions the user performed.
  It is also a good way to see the features that your users are using and identify potential misuse.

  As a regular user or admin, activity log is providing only the historical actions that this user performed :

  

  Actions listed in the log include any changes (add, edit, delete) to the following features (this is a non exhaustive list) :

  • Annotation
  • Custom Alert
  • Custom Dimension
  • Goal
  • Privacy settings
  • Scheduled report
  • Segment
  • User
  • Website
  • …

  This is a ideal to remember the actions they previously performed some weeks/months ago.

  Where can I start from here ?

  Activity log is a premium feature you can acquire through the Piwik marketplace. If you want to experience it before purchasing it, you can try it for free on our cloud infrastructure.

  I want to try the Activity Log plugin

  Activity log is just one out of the many great premium features developed by InnoCraft, the company founded by the creators of Piwik. Discover all their special plugins through the premium marketplace.