NAME

Plack::App::ServiceStatus - Check and report status of various services needed by your app

VERSION

version 0.900

SYNOPSIS

  # using Plack::Builder with Plack::App::URLMap
  use Plack::Builder;
  use Plack::App::ServiceStatus;

  my $status_app = Plack::App::ServiceStatus->new(
      app           => 'your app',
      DBIC          => $schema,
      Elasticsearch => $es, # instance of Search::Elasticsearch
  );

  builder {
    mount "/_status" => $status_app;
    mount "/" => $your_app;
  };


  # using OX
  router as {
      mount '/_status' => 'Plack::App::ServiceStatus' => (
          app                     => literal(__PACKAGE__),
          Redis                   => 'redis',
          '+MyApp::ServiceStatus' => literal("foo"),
      );
      route '/some/endpoint' => 'some_controller.some_action';
      # ...
  };


  # checking the status
  curl http://localhost:3000/_status  | json_pp
  {
     "app" : "Your app",
     "started_at" : 1465823638,
     "uptime" : 42,
     "checks" : [
        {
           "status" : "ok",
           "name" : "Your app"
        },
        {
           "name" : "Elasticsearch",
           "status" : "ok"
        },
        {
           "name" : "DBIC",
           "status" : "ok"
        }
     ]
  }

DESCRIPTION

Plack::App::ServiceStatus implements a small Plack application that you can use to get some status info on your application and the services needed by it.

You can then use some monitoring software to periodically check if your app is running and has access to all needed services.

Checks

The following checks are currently available:

• Plack::App::ServiceStatus::DBIC

• Plack::App::ServiceStatus::Redis

• Plack::App::ServiceStatus::Elasticsearch

Each check consists of a name and a status. The status can be ok or nok. A check might also contain a message, which should be some description of the error or problem if the status is nok.

You can add your own checks by specifying a name starting with a + sign, for example +My::App::SomeStatusCheck.

Weirdness

The slightly strange way Plack::App::ServiceStatus is initiated is caused by the way OX works.

Plack::App::ServiceStatus is not implemented as a middleware on purpose. While middlewares are great for a lot of use cases, I think that here an embedded app is the better fit.

TODO

• proper documentation

• tests

• make sure the app is only initiated once when running in OX

THANKS

Thanks to

• validad.com for funding the development of this code.

AUTHOR

Thomas Klausner <domm@cpan.org>

COPYRIGHT AND LICENSE

This software is copyright (c) 2016 by Thomas Klausner.

This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.