DX Application Performance Management

  • Private Community
 View Only

  • 1.  PHP Agent instance name

    Posted Jun 09, 2015 11:03 AM

    Hi all folks,

    we start using the new PHP Agent for PHP 5.4 in some test environments for testing/evaluating purpose.

    In general the PHP Agent works like suggested, nice to see.

    But we are starting several instances of one apache enviroment on our Linux systems and I don't know how to specify a unique name for the PHP Agents.

     

    You can specify something like this only,

    introscope.remoteagent.probe.agent.name = {program}

    but the Apache program is the same all the time, we are using different httpd.conf files only for each instance.

    And

    introscope.agent.agentName=SI00E.pc.as97246

    is the name used by the collector only.

     

    Today I get a name like

    D100STUL0361

    + Collector

      + SI00E.pc.as97246

    + php

      + /usd/as97246a/soft/apache-3.10.0/httpd/bin/httpd

    all the time. But the httpd program path is not a unique/useful name.

     

    Does someone know how to specify the PHP Agent names?

     

    Bye, Lutz



  • 2.  Re: PHP Agent instance name
    Best Answer

    Posted Jun 15, 2015 10:33 AM

    Hi Lutz,

     

    The PHP Probe uses Shared Memory to maintain a common cache between the different Apache child processes.

     

    So unfortunately, using the Agent to monitor several Apache instances on the same server will not work, and you will get invalid data, it doesn’t seem to be documented well enough, I’ll make sure we highlight this.

     

    A question to you: Do you run several Apache instances on the same server in production?

     

    Regs,

     

    Florian.



  • 3.  Re: PHP Agent instance name

    Posted Jun 16, 2015 09:18 AM

    Hi Florian, sorry, yes we do.

    The PHP Probe uses Shared Memory to maintain a common cache between the different Apache child processes.

     

    So unfortunately, using the Agent to monitor several Apache instances on the same server will not work, and you will get invalid data, it doesn’t seem to be documented well enough, I’ll make sure we highlight this.

     

    A question to you: Do you run several Apache instances on the same server in production?

    For internal production systems we start several Apache instances based on the same Apache installation.

     

    For external Production Systems we start some Apache instances based on the same Apache installation but in general we use several User environments with its own Apache installation to start several Apache Server on the same Linux System/box.

     

    In general a system looks like this.

    Linux box

    + User environment

      + Used Data

      + Apache

    + User environment

      + Used Data

      + Apache

        + httpd.conf listen on 8081

        + httpd.conf listen on 8080

     

    An User environment contain all used resources, programms and data include a hostname in general. All Applications inside a User enviroment get access to the (own) User filesystem and the System Filesystem only. And we are able to move this User enviroments between Linux boxes for backup purpose.

     

    This is the next problem, the new APM Agent used by the PHP Agent bind to "localhost" and I don't know how to handle this in the future.

    If I understand your explanation from the past, the new APM Agent should have write access to the Filesystem used by the installed Agents. But this is an other story.

     

    Bye, Lutz