I'd like to have a website explaining the benefits and best practices for production apps' diagnostics suite.

It would also include usage examples for various frameworks and a catalog of available checks.

Create ZendDiagnostics\Runner used to run a bundle of Checks and return a collection of results.

Hello!

Please look at https://github.com/queue-interop/queue-interop project. Using interfaces from it allows us reuse some implementations like enqueue, which supports a lot of transports. You can outsource some code

I require checking an service that uses authentication.

Using http://user:[email protected] as the host does not work. Is this something that can be added to the current HttpService?

I have created a Guzzle version of HttpService that works. I can make a PR to add if the current HttpService cannot handle.

There is a Link in the README announcing the usage of ZendDiagnostics with Symfony 2 with the LiipMonitorBundle. What exactly is missing/WIP to make this final?

Or is it just a readme adjustment to be done?

/cc @weierophinney @Thinkscape

https://github.com/zendframework/ZendDiagnostics/blob/d27aa064c5185c5830e917ffe48284b0995eed13/src/ZendDiagnostics/Runner/Reporter/BasicConsole.php#L254

https://www.perpetual-beta.org/weblog/php-from-the-command-line.html#exit-codes

Add please new tag

Some tests are being marked as Risky: https://travis-ci.org/zendframework/ZendDiagnostics/jobs/42644540#L111

Running the tests with -v displays the following messages:

There were 4 risky tests:

1) ZendDiagnosticsTest\BasicConsoleReporterTest::testUnknownSymbols
Test code or tested code did not (only) close its own output buffers

2) ZendDiagnosticsTest\BasicConsoleReporterTest::testProgressDotsNoGutter
Test code or tested code did not (only) close its own output buffers

3) ZendDiagnosticsTest\BasicConsoleReporterTest::testProgressOverflow
Test code or tested code did not (only) close its own output buffers

4) ZendDiagnosticsTest\BasicConsoleReporterTest::testProgressOverflowMatch
Test code or tested code did not (only) close its own output buffers

I am not sure how to fix these...

• Check view_manager template_map and template_path_stack
  • Check for existence
  • Check for readability
  • Lint the PHP code
• Check Zend\Db connection availability
• Generic Zend\Cache\Adapter check, optionally probing for capabilities and checking that too.
• Generic Zend\Session\Adapter check.
• Try to instantiate all SM services found in configuration and catch exceptions.
• Is module installed ? (request)

Is anyone open for improvements to the test setup? E.g. phpunit as require-dev, a Makefile etc.? I'll PR it then.

zendframework/ZFTool#66

each PHP version tests fails since 17days ago
https://travis-ci.org/zendframework/ZendDiagnostics/builds

Currently the repository name is: zendframework/zenddiagnostics.
Can we rename it to zendframework/zend-diagnostics (with dash) to match naming convention in ZF repo names?

See:

• https://packagist.org/packages/zendframework/zenddiagnostics

Without this file, redistribution of this library in any project will be impossible with violating the BSD license term:

* Redistributions of source code must retain the above copyright
  notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright
  notice, this list of conditions and the following disclaimer in the
  documentation and/or other materials provided with the distribution.

Also see: https://fedoraproject.org/wiki/Packaging:LicensingGuidelines#License_Text

so as liip/LiipMonitorBundle#41 is about to get merged, it would be good to tag a first release. so it would like to know what is the process here? to at least get a development release. but also for getting a stable release ..

/cc @Thinkscape @weierophinney

I'm having an issue because I cannot test a http services that is supposed to receive a json on the body, here is the problem:

https://github.com/zendframework/ZendDiagnostics/blob/d27aa064c5185c5830e917ffe48284b0995eed13/src/ZendDiagnostics/Check/GuzzleHttpService.php#L105

This line will have to say:

array('headers' => $this->headers, 'json' => $this->body, 'exceptions' => false),

Maybe there should be a way to specify the type of body that we want to pass, something like:

$body = ['body' => $this->body];
if($this->body['json']) $body = ['json' => $this->body['json'] ];
array('headers' => $this->headers, $body, 'exceptions' => false),

Hello, the ZendDiagnostics\Check\ProcessRunning::check doesn't work in small cli windows.

A Solution would be to add -ww to the ps command.

exec('ps -efww | grep ' . escapeshellarg($this->processName) . ' | grep -v grep', $output, $return);

ps manual:

-w Wide output. Use this option twice for unlimited width.

Hi...

I found a error when run diagnostics.

In this loop $alias always will be 0, if $checkAlias is not null
https://github.com/zendframework/ZendDiagnostics/blob/master/src/ZendDiagnostics/Runner/Runner.php#L112

Problem in this line of code:
https://github.com/zendframework/ZendDiagnostics/blob/master/src/ZendDiagnostics/Runner/Runner.php#L106
For example, this will solve this problem:
$checks = $checkAlias ? new ArrayObject(array($checkAlias => $this->getCheck($checkAlias))) : $this->getChecks();

This is a continuation of discussion from zendframework/ZFTool#39

Like https://packagist.org/packages/beberlei/assert or https://packagist.org/packages/peridot-php/leo

I would be happy to provide a PR if you accept such a contribution.

It seems that coveralls is not enabled for the library:
https://coveralls.io/github/zendframework/zend-diagnostics?branch=master
but in travis we try upload the coverage and the whole coveralls configuration is present in the library.

Can we please enable it to see the proper coverage badge on the main page, please?

Declaration of ZendDiagnostics\Result\Collection::offsetSet($index, $checkResult) must be compatible with SplObjectStorage::offsetSet($object, $inf = NULL)

is this a php72 side effect?

liip/LiipMonitorBundle#157

[2017-12-05 17:56:35] request.CRITICAL: Uncaught PHP Exception Symfony\Component\Debug\Exception\FatalErrorException: "Compile Error: Declaration of ZendDiagnostics\Result\Collection::offsetSet($index, $checkResult) must be compatible with SplObjectStorage::offsetSet($object, $inf = NULL)" at /private/var/www/system/var/vendor/zendframework/zenddiagnostics/src/ZendDiagnostics/Result/Collection.php line 219 {"exception":"[object] (Symfony\Component\Debug\Exception\FatalErrorException(code: 0): Compile Error: Declaration of ZendDiagnostics\Result\Collection::offsetSet($index, $checkResult) must be compatible with SplObjectStorage::offsetSet($object, $inf = NULL) at /private/var/www/system/var/vendor/zendframework/zenddiagnostics/src/ZendDiagnostics/Result/Collection.php:219)"} []
[2017-12-05 17:56:35] request.INFO: Matched route "_wdt". {"route":"_wdt","route_parameters":{"_controller":"web_profiler.controller.profiler:toolbarAction","token":"007c14","_route":"_wdt"},"request_uri":"https://system.m/_wdt/007c14","method":"GET"} []