Exception-Reporter/lib/Exception/Reporter/Sender/Dir.pm
use strict;
use warnings;
package Exception::Reporter::Sender::Dir 0.015;
# ABSTRACT: a report sender that writes to directories on the filesystem
use parent 'Exception::Reporter::Sender';
#pod =head1 SYNOPSIS
#pod
#pod my $sender = Exception::Reporter::Sender::Dir->new({
#pod root => '/var/error/my-app',
#pod });
#pod
#pod =head1 OVERVIEW
#pod
#pod This report sender writes reports to the file system. Given a report with
#pod bunch dumpable items, the Dir sender will make a directory and write each item
#pod to a file in it, using the ident when practical, and a generated filename
#pod otherwise.
#pod
#pod =cut
use Digest::MD5 ();
use JSON ();
use Path::Tiny;
use String::Truncate;
use Try::Tiny;
sub new {
my ($class, $arg) = @_;
my $root = $arg->{root} || Carp::confess("missing 'root' argument");
use Path::Tiny;
$root = path($root);
if (-e $root && ! -d $root) {
Carp::confess("given root <$root> is not a writable directory");
}
$root->mkpath unless -e $root;
return bless {
root => $root,
}, $class;
}
#pod =head2 send_report
#pod
#pod $dir_reporter->send_report(\@summaries, \%arg, \%internal_arg);
#pod
#pod This method makes a subdirectory for the report and writes it out.
#pod
#pod C<%arg> is the same set of arguments given to Exception::Reporter's
#pod C<report_exception> method. Arguments that will have an effect include:
#pod
#pod reporter - the name of the program reporting the exception
#pod handled - if true, the reported exception was handled and the user
#pod saw a simple error message; adds C<< "handled":true >>
#pod to the JSON body of the report
#pod
#pod C<%internal_arg> contains data produced by the Exception::Reporter using this
#pod object. It includes the C<guid> of the report and the C<caller> calling the
#pod reporter.
#pod
#pod The return value of C<send_report> is not defined.
#pod
#pod =cut
my $JSON;
sub send_report {
my ($self, $summaries, $arg, $internal_arg) = @_;
# ?!? Presumably this can't really happen, but... you know what they say
# about zero-summary incidents, right? -- rjbs, 2012-07-03
Carp::confess("can't report a zero-summary incident!") unless @$summaries;
# We always use this file for internal use.
my %manifest = ('report.json' => { description => 'report metadata' });
my %report = (
guid => $internal_arg->{guid},
manifest => \%manifest,
);
my $n = 1;
my $safename = sub {
my ($name) = @_;
# Surely this is sub-optimal: -- rjbs, 2016-07-19
$name =~ s{\.\.}{DOTDOT}g;
$name =~ s{/}{BACKSLASH}g;
$name =~ s{[^-_0-9a-z.]}{-}gi;
my $base = $name;
$name = "$base-" . $n++ while $manifest{$name};
return $name;
};
my $root = $self->{root}->child($internal_arg->{guid});
$root->mkpath;
my @parts;
GROUP: for my $summary (@$summaries) {
my @these_parts;
my $t_path = \&path;
if (@{ $summary->[1] } > 1) {
my $name = $safename->($summary->[0]);
$manifest{$name} = { ident => $summary->[0] };
$root->child($name)->mkpath;
my $target_path = path($name);
$t_path = sub { $target_path->child($_[0]) };
}
for my $inner (@{ $summary->[1] }) {
my $file = $t_path->(
$safename->( $inner->{filename} || 'inner' )
);
$manifest{$file} = {
filename => $inner->{filename},
content_type => $inner->{mimetype},
(($inner->{body_is_bytes} && $inner->{charset})
? (charset => $inner->{charset})
: ()),
};
my $method = $inner->{body_is_bytes} ? 'spew_raw' : 'spew_utf8';
$root->child($file)->$method($inner->{body});
}
}
if ($arg->{handled}) {
$report{handled} = \1;
}
my ($package, $filename, $line) = @{ $internal_arg->{caller} };
$report{reporter} = $arg->{reporter};
$report{caller} = "$filename line $line ($package)";
$JSON ||= JSON->new->canonical->pretty;
my $json = $JSON->encode(\%report);
$root->child('report.json')->spew_utf8($json);
return;
}
1;
__END__
=pod
=encoding UTF-8
=head1 NAME
Exception::Reporter::Sender::Dir - a report sender that writes to directories on the filesystem
=head1 VERSION
version 0.015
=head1 SYNOPSIS
my $sender = Exception::Reporter::Sender::Dir->new({
root => '/var/error/my-app',
});
=head1 OVERVIEW
This report sender writes reports to the file system. Given a report with
bunch dumpable items, the Dir sender will make a directory and write each item
to a file in it, using the ident when practical, and a generated filename
otherwise.
=head2 send_report
$dir_reporter->send_report(\@summaries, \%arg, \%internal_arg);
This method makes a subdirectory for the report and writes it out.
C<%arg> is the same set of arguments given to Exception::Reporter's
C<report_exception> method. Arguments that will have an effect include:
reporter - the name of the program reporting the exception
handled - if true, the reported exception was handled and the user
saw a simple error message; adds C<< "handled":true >>
to the JSON body of the report
C<%internal_arg> contains data produced by the Exception::Reporter using this
object. It includes the C<guid> of the report and the C<caller> calling the
reporter.
The return value of C<send_report> is not defined.
=head1 PERL VERSION
This module should work on any version of perl still receiving updates from
the Perl 5 Porters. This means it should work on any version of perl released
in the last two to three years. (That is, if the most recently released
version is v5.40, then this module should work on both v5.40 and v5.38.)
Although it may work on older versions of perl, no guarantee is made that the
minimum required version will not be increased. The version may be increased
for any reason, and there is no promise that patches will be accepted to lower
the minimum required perl.
=head1 AUTHOR
Ricardo Signes <cpan@semiotic.systems>
=head1 COPYRIGHT AND LICENSE
This software is copyright (c) 2010 by Ricardo Signes.
This is free software; you can redistribute it and/or modify it under
the same terms as the Perl 5 programming language system itself.
=cut