Ad Widget

Collapse

Zabbix 6.4.x - Apache by Zabbix Agent 6.4.0 Template - apache.proc.num

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Mounting1050
    Junior Member
    • Oct 2023
    • 1

    #1

    Zabbix 6.4.x - Apache by Zabbix Agent 6.4.0 Template - apache.proc.num

    Hello,
    I'm new i this forum, but i have a problem with apache2 monitoring and I don't know how to fix it, i'm just started some months ago evaluation Zabbix for different kind of monitoring so i'm far away from being an expert.

    So my problem is the following, i try to monitor an Apache2 on an Debian 11.8 with zabbix_agent (6.4.7) installed, and attached Template Apache by Zabbix Agent.

    Most of the Time it works fine, but then and now it seems the Apache Discovery has a problem and detect apache2ctl instead of apache2 as value for apache.proc.num.

    So when i look up Latest Data for the Host i have two entries of Apache: Number of running processes
    One with - Key: apache.proc.num[apache2ctl] (wrong) and one with Key: apache.proc.num[apache2] (correct)

    And now i'm getting a warning apache2 process not running, from the apache.proc.num[apache2ctl], but yes apache i running fine only the wrong process is monitored as it was identified wrong.

    How could i prevent from happening that the apache2ctl is found as apache2 process ?

    Thank you for any hint.
  • socha
    Junior Member
    • Feb 2024
    • 1

    #2
    Hello,

    Have you found a solution to your problem? I have exactly the same issue on one of my servers.

    Comment

    • dominicpratt
      Junior Member
      • Dec 2018
      • 14

      #3
      I had the same problem only with different process names. In my case the culprit was
      Code:
      libapache2-mod-*
      The Apache process on my system is called
      Code:
      apache2
      I solved the problem by adapting the macro in the template. From
      Code:
      (httpd|apache2)
      to
      Code:
      (httpd|^apache2$)
      I then removed the faulty items from the host, ran the discovery again and the faulty items did not reappear... maybe this will help someone.

      I think this should be implemented in the template - I see no harm here... Can someone from the team perhaps adjust this in the repository?

      Comment


      • TéJi
        TéJi commented
        Editing a comment
        Thank You Very Much, it was exactly my problem, your solution seems to work for me too ! THANKS !
    Working...