Register Now

Confirm Password *

Terms * By registering, you agree to the terms of service and Privacy Policy .

Lost Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Install and configure Zabbix Agent on Windows

Install and configure Zabbix Agent on Windows

In this post, we will look at how to install and configure Zabbix Agent on the Windows platform.

Table of Contents

1. Download Windows Zabbix Agent

1. Download the Windows Zabbix Agent from officially Zabbix website. Below is an example for x64 machine with no encryption. Here is the direct download link https://www.zabbix.com/download_agents and select the following from the given options.

2. You will see the Zabbix Release options as below and usually, you would go for the latest release and click on download.

task manager zabbix

3. Downloaded file will be a zip file and unzip the file, you will see the below content.

task manager zabbix

  • bin folder has the following files

task manager zabbix

  • conf folder has the configuration file

task manager zabbix

2. Move files on the target endpoint

For this example, my target endpoint is Windows Server 2019 OS (TEKNEX-CA01).

1 . Create zabbix folder in the Windows root directory c:\zabbix

task manager zabbix

2. Copy below files to newly created zabbix folder

  • bin\zabbix_agentd.exe
  • conf\zabbix_agentd.conf

task manager zabbix

3. Prepare Windows firewall

By default, Zabbix agent communicates over 10050 port, and I am sticking with the default port.

1. Add port TCP 10050 in the allow list for inbound communication. You could use GUI to achieve this, however, it is easier to run the following PowerShell command. This will add TCP port 10050 in the inbound allow list. Ensure you apply to the correct profile, TEKNEX-CA01 is part of the domain and this is why I am applying inbound to the Domain profile only. Run the following one-line command in PowerShell as administrator.

task manager zabbix

To add this firewall rule to all profiles, you can use the following command. This command will allow inbound port 10050 on Domain, Private and Public profile.

2. Confirm the rule has been added by running the following command.

task manager zabbix

4. Update Zabbix configuration file

Open zabbix_agentd.conf with any editor, even Windows built-in notepad will do the job. Uncomment the following and update accordingly. Save the file once you make changes.

  • Server Provide Zabbix server IP address

task manager zabbix

  • ListenPort Keep this default as 10050, unless you changed it

task manager zabbix

  • Hostname Enter the hostname if your Zabbix does not resolve the hostname to IP address. If your DNS is functioning correctly, you can use the variable system.name . To keep things simple, I will just provide hostname manually.

task manager zabbix

5. Install and Start Zabbix service

1. Browse to zabbix folder on Windows endpoint

task manager zabbix

2. Select File in the Navigation pane > hover over Windows PowerShell > click Open Windows PowerShell as administrator

task manager zabbix

3. Run the below command to install Zabbix.

You will see this message when you run the above command

task manager zabbix

4. Run the following command to start Zabbix service or you could start the service from the Task Manager

task manager zabbix

4. Verify Zabbix agent service in the Task Manager

task manager zabbix

6. Create a new Group on Zabbix Server

To add a host, we need to create a host group first. If you already have a group then you can skip this part.

1. Login to Zabbix front end > Extend Configuration > Click on Host groups

task manager zabbix

2. Click on Create host group on the top right hand corner

task manager zabbix

3. Give a name to new host group and click Add

task manager zabbix

7. Add a host on Zabbix Server

1. Login to Zabbix front end > Extend Configuration > Click on Hosts

task manager zabbix

2. Click on Create host on the top right hand corner

task manager zabbix

3. Enter the following information and click on Add

task manager zabbix

You will see something like following once you add a host under Configuration > Hosts

task manager zabbix

8. Link a template with the host

A host must have a template linked so that Zabbix Agent can report back to Zabbix Server with the requested data. In this step, let’s link a template with our newly added host TEKNEX-CA01.

1. Go to Configuration > Hosts

task manager zabbix

2. Click on newly added host TEKNEX-CA01

task manager zabbix

4. On the TEKNEX-CA01 host page, click on Templates

task manager zabbix

5. Next to Link new templates click on select

task manager zabbix

6. In the Host group search, type operating systems and click on Templates/Operating Systems

This image has an empty alt attribute; its file name is image-66.png

7. Check Template OS Windows by Zabbix Agent and click on Select

task manager zabbix

8. Click on update to save changes

task manager zabbix

9. Check availability

It can take a couple of minutes for the Zabbix server to initiate an initial communication with the endpoint. Once you attach a template, communication might not start straight away and you will see something like below under Configuration > Hosts

task manager zabbix

Once the communication has initiated, ZBX will turn into green and you would see something like below.

task manager zabbix

10. Troubleshooting

If you have waited long enough and ZBX did not turn into green, this indicates that there is something not right. Check the following:

  • Inbound port 10500 is opened for the required profile. In the above example, I used Domain Profile because the endpoint is part of a domain.
  • Ping endpoint from the Zabbix server and it should ping successfully
  • Check the log file on the endpoint located in the Windows root directory and it can indicate you if there is an issue

task manager zabbix

Your feedback is very important. Let me know how did you go in the comments below.

task manager zabbix

About Jay Singh

Related posts, importing assets in snipe-it, zabbix 5.4 installation on ubuntu server, snipe-it installation on ubuntu server (nginx), snipe-it installation on ubuntu server, snipe-it installation on windows server.

guest

Can you explain the need to create a local folder on the root of C: and manually config the agent instead of running the Windows installer?

Jay Singh

As you may have noticed that we have changed a bit in the configuration file here and then specified the configuration file in our command. Running the installer directly will miss the configuration and it would not use settings from the config file.

akk

I hope this article can be use on Windows server 2019

 Previous post

Next post 

Stack Exchange Network

Stack Exchange network consists of 183 Q&A communities including Stack Overflow , the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Zabbix low-level discovery - CPU usage per process - two items with identical keys

I'm trying to use Zabbix for monitoring CPU usage by different processes on Windows Server. Processes to monitor are not determined upfront. I want to use LLD to monitor top 3 CPU demanding processes.

Currently I've created a discovery rule that returns top 3 CPU demanding processes at given moment, for example:

Then I've created macros using json paths and item prototype and that's where i started to experience problems. I'm using earlier created LLD macro for item name and I'm using system.run command for obtaning a value in key field. Item name is supposed to process name and item key, value is supposed the CPU usage by that process. [enter image description here][1] [1]: https://i.stack.imgur.com/HuNbd.png

When testing discovery rule and item prototype everything runs fine, but when i try to run that discovery rule I get an error

" Cannot create item: item with the same key "system.run[powershell.exe -nolog -command "(Get-Process | Sort-Object CPU -desc | Select-Object -index 0 | Format-Table -Aut...]" already exists. "

Firstly, there is no other item with the same key.

Secondly, when my discovery rule will detect other processes, there will have to be created other items with the same key. Other names, but the same key

Is it even possible to create processes CPU usage monitoring using LLD? I don't want to be stuck with predefined processes, I would like to have them dynamicly added with LLD.

maar's user avatar

2 Answers 2

Zabbix requires keys be unique for a single host, so you'll run into problems when there is more than one of the same named process if you store processes by name ( https://www.zabbix.com/documentation/current/manual/config/items/item )

Process names don't need to be unique, so Get-Process returns objects with duplicate ProcessName values.

You can add -Unique to the select cmdlet to drop duplicates. This might hide data you want to log.

The Zabbix team looks like they provided a workaround to this problem here: https://support.zabbix.com/browse/ZBXNEXT-164

UserParameter=top,top -n 1 -b|head -20

Garrett's user avatar

  • 1 I've discovered that Get-Process command does not provide current CPU usage (as seen in task manager), I've decided to use Get-Counter command which provides necessary data. More over I'm using javasript to process data and it's working quite nice. I'm still looking forward into improvements of processes monitoring and LLD in zabbix. –  Paweł Zimny Jul 15, 2020 at 13:57

For each item that you've create, you have to create a new keyitem, for example get.top.proccess.[{#Name}]. This way each item has a different keyitem becase the variable changes.

Kevin Yan's user avatar

You must log in to answer this question.

Not the answer you're looking for browse other questions tagged windows powershell monitoring process zabbix ..

  • The Overflow Blog
  • Climbing the GenAI decision tree sponsored post
  • Diverting more backdoor disasters
  • Featured on Meta
  • New Focus Styles & Updated Styling for Button Groups
  • Upcoming initiatives on Stack Overflow and across the Stack Exchange network

Hot Network Questions

  • PNP transistor not pulling up completely : what is wrong in my schematic?
  • Addplot messes with axis coordinate system?
  • Choose and snooze
  • What is a word for battery "longevity"?
  • How Probable is the Philosophical Significance of Numerical Patterns in Religious Texts?
  • Insurance for expeditions
  • Was cuneiform ever 'written'?
  • How to execute a command on all files whose names match a pattern and whose contents match a pattern?
  • Is there an overarching purpose for philosophy?
  • How can we infallibly know that the Catholic Church is infallible?
  • Haste creature under The Akroan War chapter 2 ability
  • How can I keep my brakes centered?
  • Why is this plane flying in circles
  • Why is remote desktop very slow when host monitor is off unless HDMI cable is used?
  • FizzFizzFizzBuzz!
  • Professor Rackbrane: Count the triangles
  • Expand a 2d curve into a 3d path curve with a fixed axis of rotation?
  • Are my skin and hair colors believable?
  • Differences Between `/dev/null` and Devices Under `null_blk` Driver
  • In the Wallace and Gromit movies we see 'Electronics for Dogs.' Do we ever see any other 'books for Dogs' in-universe?
  • Far future robot historian or archeologist. There are no longer humans in the known universe. It describes meeting one of the last humans
  • How to simulate low-rank hamiltonian?
  • What measures have been proposed to assess geopolitical instability over time?
  • Beginner: Solder won’t flow onto thermostat tabs

task manager zabbix

IP/DNS/network mask list of servers to be remotely queried (default is 127.0.0.1).

Port of server to be remotely queried (default is 10051).

The maximum number of seconds that Zabbix proxy has not been seen.

The time threshold after which statistics are considered unavailable. Used in trigger expression.

The master item of Zabbix server statistics.

The master item of Zabbix proxies' statistics.

**Preprocessing**

JSON Path: `$.data.proxy`

The number of monitored items in the queue, which are delayed at least by 10 minutes.

JSON Path: `$.queue`

The number of monitored items in the queue, which are delayed at least by 6 seconds.

The average percentage of the time during which the alert manager processes have been busy for the last minute.

JSON Path: `$.data.process['alert manager'].busy.avg`

⛔️Custom on fail: Set error to: `No "alert manager" processes started.`

The average percentage of the time during which the alert syncer processes have been busy for the last minute.

JSON Path: `$.data.process['alert syncer'].busy.avg`

⛔️Custom on fail: Set error to: `No "alert syncer" processes started.`

The average percentage of the time during which the alerter processes have been busy for the last minute.

JSON Path: `$.data.process['alerter'].busy.avg`

⛔️Custom on fail: Set error to: `No "alerter" processes started.`

The average percentage of the time during which the availability manager processes have been busy for the last minute.

JSON Path: `$.data.process['availability manager'].busy.avg`

⛔️Custom on fail: Set error to: `No "availability manager" processes started.`

The average percentage of the time during which the configuration syncer processes have been busy for the last minute.

JSON Path: `$.data.process['configuration syncer'].busy.avg`

⛔️Custom on fail: Set error to: `No "configuration syncer" processes started.`

The average percentage of the time during which the escalator processes have been busy for the last minute.

JSON Path: `$.data.process['escalator'].busy.avg`

⛔️Custom on fail: Set error to: `No "escalator" processes started.`

The average percentage of the time during which the history poller processes have been busy for the last minute.

JSON Path: `$.data.process['history poller'].busy.avg`

⛔️Custom on fail: Set error to: `No "history poller" processes started.`

The average percentage of the time during which the ODBC poller processes have been busy for the last minute.

JSON Path: `$.data.process['odbc poller'].busy.avg`

The average percentage of the time during which the history syncer processes have been busy for the last minute.

JSON Path: `$.data.process['history syncer'].busy.avg`

⛔️Custom on fail: Set error to: `No "history syncer" processes started.`

The average percentage of the time during which the housekeeper processes have been busy for the last minute.

JSON Path: `$.data.process['housekeeper'].busy.avg`

⛔️Custom on fail: Set error to: `No "housekeeper" processes started.`

The average percentage of the time during which the http poller processes have been busy for the last minute.

JSON Path: `$.data.process['http poller'].busy.avg`

⛔️Custom on fail: Set error to: `No "http poller" processes started.`

The average percentage of the time during which the icmp pinger processes have been busy for the last minute.

JSON Path: `$.data.process['icmp pinger'].busy.avg`

⛔️Custom on fail: Set error to: `No "icmp pinger" processes started.`

The average percentage of the time during which the ipmi manager processes have been busy for the last minute.

JSON Path: `$.data.process['ipmi manager'].busy.avg`

⛔️Custom on fail: Set error to: `No "ipmi manager" processes started.`

The average percentage of the time during which the ipmi poller processes have been busy for the last minute.

JSON Path: `$.data.process['ipmi poller'].busy.avg`

⛔️Custom on fail: Set error to: `No "ipmi poller" processes started.`

The average percentage of the time during which the java poller processes have been busy for the last minute.

JSON Path: `$.data.process['java poller'].busy.avg`

⛔️Custom on fail: Set error to: `No "java poller" processes started.`

The average percentage of the time during which the lld manager processes have been busy for the last minute.

JSON Path: `$.data.process['lld manager'].busy.avg`

⛔️Custom on fail: Set error to: `No "LLD manager" processes started.`

The average percentage of the time during which the lld worker processes have been busy for the last minute.

JSON Path: `$.data.process['lld worker'].busy.avg`

⛔️Custom on fail: Set error to: `No "LLD worker" processes started.`

The average percentage of the time during which the connector manager processes have been busy for the last minute.

JSON Path: `$.data.process['connector manager'].busy.avg`

⛔️Custom on fail: Set error to: `No "connector manager" processes started.`

The average percentage of the time during which the connector worker processes have been busy for the last minute.

JSON Path: `$.data.process['connector worker'].busy.avg`

⛔️Custom on fail: Set error to: `No "connector worker" processes started.`

The average percentage of the time during which the discovery manager processes have been busy for the last minute.

JSON Path: `$.data.process['discovery manager'].busy.avg`

⛔️Custom on fail: Set error to: `No "discovery manager" processes started.`

The average percentage of the time during which the discovery worker processes have been busy for the last minute.

JSON Path: `$.data.process['discovery worker'].busy.avg`

⛔️Custom on fail: Set error to: `No "discovery worker" processes started.`

The average percentage of the time during which the poller processes have been busy for the last minute.

JSON Path: `$.data.process['poller'].busy.avg`

⛔️Custom on fail: Set error to: `No "poller" processes started.`

The average percentage of the time during which the preprocessing worker processes have been busy for the last minute.

JSON Path: `$.data.process['preprocessing worker'].busy.avg`

⛔️Custom on fail: Set error to: `No "preprocessing worker" processes started.`

The average percentage of the time during which the preprocessing manager processes have been busy for the last minute.

JSON Path: `$.data.process['preprocessing manager'].busy.avg`

⛔️Custom on fail: Set error to: `No "preprocessing manager" processes started.`

The average percentage of the time during which the proxy poller processes have been busy for the last minute.

JSON Path: `$.data.process['proxy poller'].busy.avg`

⛔️Custom on fail: Set error to: `No "proxy poller" processes started.`

The average percentage of the time during which the report manager processes have been busy for the last minute.

JSON Path: `$.data.process['report manager'].busy.avg`

⛔️Custom on fail: Set error to: `No "report manager" processes started.`

The average percentage of the time during which the report writer processes have been busy for the last minute.

JSON Path: `$.data.process['report writer'].busy.avg`

⛔️Custom on fail: Set error to: `No "report writer" processes started.`

The average percentage of the time during which the self-monitoring processes have been busy for the last minute.

JSON Path: `$.data.process['self-monitoring'].busy.avg`

⛔️Custom on fail: Set error to: `No "self-monitoring" processes started.`

The average percentage of the time during which the snmp trapper processes have been busy for the last minute.

JSON Path: `$.data.process['snmp trapper'].busy.avg`

⛔️Custom on fail: Set error to: `No "snmp trapper" processes started.`

The average percentage of the time during which the task manager processes have been busy for the last minute.

JSON Path: `$.data.process['task manager'].busy.avg`

⛔️Custom on fail: Set error to: `No "task manager" processes started.`

The average percentage of the time during which the timer processes have been busy for the last minute.

JSON Path: `$.data.process['timer'].busy.avg`

⛔️Custom on fail: Set error to: `No "timer" processes started.`

The average percentage of the time during which the service manager processes have been busy for the last minute.

JSON Path: `$.data.process['service manager'].busy.avg`

⛔️Custom on fail: Set error to: `No "service manager" processes started.`

The average percentage of the time during which the trigger housekeeper processes have been busy for the last minute.

JSON Path: `$.data.process['trigger housekeeper'].busy.avg`

⛔️Custom on fail: Set error to: `No "trigger housekeeper" processes started.`

The average percentage of the time during which the trapper processes have been busy for the last minute.

JSON Path: `$.data.process['trapper'].busy.avg`

⛔️Custom on fail: Set error to: `No "trapper" processes started.`

The average percentage of the time during which the unreachable poller processes have been busy for the last minute.

JSON Path: `$.data.process['unreachable poller'].busy.avg`

⛔️Custom on fail: Set error to: `No "unreachable poller" processes started.`

The average percentage of the time during which the vmware collector processes have been busy for the last minute.

JSON Path: `$.data.process['vmware collector'].busy.avg`

⛔️Custom on fail: Set error to: `No "vmware collector" processes started.`

The average percentage of the time during which the agent poller processes have been busy for the last minute.

JSON Path: `$.data.process['agent poller'].busy.avg`

⛔️Custom on fail: Set error to: `No "agent poller" processes started.`

The average percentage of the time during which the http agent poller processes have been busy for the last minute.

JSON Path: `$.data.process['http agent poller'].busy.avg`

⛔️Custom on fail: Set error to: `No "http agent poller" processes started.`

The average percentage of the time during which the snmp poller processes have been busy for the last minute.

JSON Path: `$.data.process['snmp poller'].busy.avg`

⛔️Custom on fail: Set error to: `No "snmp poller" processes started.`

The availability statistics of Zabbix configuration cache. The percentage of used data buffer.

JSON Path: `$.data.rcache.pused`

The effectiveness statistics of Zabbix trend function cache. The percentage of cached items calculated from the sum of cached items plus requests.

Low percentage most likely means that the cache size can be reduced.

JSON Path: `$.data.tcache.pitems`

⛔️Custom on fail: Set error to: `Not supported in this version.`

The effectiveness statistics of Zabbix trend function cache. The percentage of cache misses.

JSON Path: `$.data.tcache.pmisses`

The availability statistics of Zabbix value cache. The percentage of used data buffer.

JSON Path: `$.data.vcache.buffer.pused`

The effectiveness statistics of Zabbix value cache. The number of cache hits (history values taken from the cache).

JSON Path: `$.data.vcache.cache.hits`

  • Change per second

The effectiveness statistics of Zabbix value cache. The number of cache misses (history values taken from the database).

JSON Path: `$.data.vcache.cache.misses`

The operating mode of the value cache.

JSON Path: `$.data.vcache.cache.mode`

Average quantity of values written to the database, recalculated once per minute.

JSON Path: `$.data.vps.written_total`

A version of Zabbix server.

JSON Path: `$.data.version`

Discard unchanged with heartbeat: `1d`

The availability statistics of Zabbix vmware cache. The percentage of used data buffer.

JSON Path: `$.data.vmware.pused`

The statistics and availability of Zabbix write cache. The percentage of used history buffer.

The history cache is used to store item values. A high number indicates performance problems on the database side.

JSON Path: `$.data.wcache.history.pused`

The statistics and availability of Zabbix write cache. The percentage of used history index buffer.

The history index cache is used to index values stored in the history cache.

JSON Path: `$.data.wcache.index.pused`

The statistics and availability of Zabbix write cache. The percentage of used trend buffer.

The trend cache stores the aggregate of all items that have receive data for the current hour.

JSON Path: `$.data.wcache.trend.pused`

The statistics and availability of Zabbix write cache.

The total number of values processed by Zabbix server or Zabbix proxy, except unsupported items.

JSON Path: `$.data.wcache.values.all`

The number of processed float values.

JSON Path: `$.data.wcache.values.float`

The number of processed log values.

JSON Path: `$.data.wcache.values.log`

The number of times the item processing resulted in an item becoming unsupported or keeping that state.

JSON Path: `$.data.wcache.values['not supported']`

The number of processed character/string values.

JSON Path: `$.data.wcache.values.str`

The number of processed text values.

JSON Path: `$.data.wcache.values.text`

The count of values enqueued in the low-level discovery processing queue.

JSON Path: `$.data.lld_queue`

The count of values enqueued in the preprocessing queue.

JSON Path: `$.data.preprocessing_queue`

The count of values enqueued in the connector queue.

JSON Path: `$.data.connector_queue`

⛔️Custom on fail: Set error to: `No "connector" processes started. Please check "StartConnectors" parameter in the server configuration file.`

The count of values enqueued in the discovery queue.

JSON Path: `$.data.discovery_queue`

⛔️Custom on fail: Set error to: `No "discoverer" processes started. Please check "StartDiscoverers" parameter in the server configuration file.`

The number of processed numeric (unsigned) values.

JSON Path: `$.data.wcache.values.uint`

The `zabbix[stats,{$ZABBIX.SERVER.ADDRESS},{$ZABBIX.SERVER.PORT},queue,10m]` item collects data about the number of items that have been missing the data for more than 10 minutes.

Consider increasing `CacheSize` in the `zabbix_server.conf` configuration file.

Zabbix has not received statistics data for {$ZABBIX.SERVER.NODATA_TIMEOUT}.

Consider increasing `ValueCacheSize` in the `zabbix_server.conf` configuration file.

Once the low memory mode has been switched on, the value cache will remain in this state for 24 hours, even if the problem that triggered this mode is resolved sooner.

Zabbix server version has changed. Acknowledge to close the problem manually.

Consider increasing `VMwareCacheSize` in the `zabbix_server.conf` configuration file.

Consider increasing `HistoryCacheSize` in the `zabbix_server.conf` configuration file.

Consider increasing `HistoryIndexCacheSize` in the `zabbix_server.conf` configuration file.

Consider increasing `TrendCacheSize` in the `zabbix_server.conf` configuration file.

LLD rule with item and trigger prototypes for the proxy discovery.

The statistics for the discovered proxy.

JSON Path: `$.[?(@.name=="{#PROXY.NAME}")].first()`

The mode of Zabbix proxy.

JSON Path: `$.passive`

JavaScript: `return value === 'false' ? 0 : 1`

Discard unchanged with heartbeat: `12h`

The encryption status for connections from a proxy.

JSON Path: `$.unencrypted`

JSON Path: `$.psk`

JSON Path: `$.cert`

The compression status of a proxy.

JSON Path: `$.compression`

The number of enabled items on enabled hosts assigned to a proxy.

JSON Path: `$.items`

The number of enabled hosts assigned to a proxy.

JSON Path: `$.hosts`

A version of Zabbix proxy.

JSON Path: `$.version`

The time when a proxy was last seen by a server.

JSON Path: `$.last_seen`

Version of proxy compared to Zabbix server version.

Possible values:

0 - Undefined;

1 - Current version (proxy and server have the same major version);

2 - Outdated version (proxy version is older than server version, but is partially supported);

3 - Unsupported version (proxy version is older than server previous LTS release version or server major version is older than proxy major version).

JSON Path: `$.compatibility`

The required performance of a proxy (the number of values that need to be collected per second).

JSON Path: `$.requiredperformance`

Zabbix proxy is not updating the configuration data.

Zabbix proxy version is older than server version, but is partially supported. Only data collection and remote execution is available.

Zabbix proxy version is older than server previous LTS release version or server major version is older than proxy major version.

LLD rule with item and trigger prototypes for the node discovery.

JSON Path: `$.data.ha`

Provides the statistics of a node.

JSON Path: `$.data.ha[?(@.id=="{#NODE.ID}")].first()`

The IPv4 address of a node.

JSON Path: `$.address`

Last access time.

JSON Path: `$.lastaccess`

The time between the database's `unix_timestamp()` and the last access time.

JSON Path: `$.lastaccess_age`

The status of a node.

JSON Path: `$.status`

The state of the node has changed. Acknowledge to close the problem manually.

Search code, repositories, users, issues, pull requests...

Provide feedback.

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly.

To see all available qualifiers, see our documentation .

  • Notifications

Uploaded image for project: 'ZABBIX BUGS AND ISSUES'

  • ZABBIX BUGS AND ISSUES

Task manager process for closing events fails if related events were deleted before task was processed

Icon: Problem report

  • Resolution: Fixed
  • Fix Version/s: 3.2.8rc1
  • Affects Version/s: 3.2.6
  • Component/s: Server (S)
  • Labels: None
  • Team: Team C
  • Sprint: Sprint 10, Sprint 11, Sprint 12, Sprint 13
  • Story Points: 3

Description

Doing bulk ack from Problems page to close all problems, tasks are added to database and processed by task manager.

In case if we ack a lot problems it is possible that related events will be deleted by housekeeper and when task manager will try to process it, it will fail.

If query output IS NULL

And these tasks remain in database.

Attachments

Unassigned

IMAGES

  1. zabbix_agentd.exe Windows Prozess

    task manager zabbix

  2. zabbix_agentd.exe Windows process

    task manager zabbix

  3. memory utilized by service monitored by Zabbix, not matching with task manager

    task manager zabbix

  4. [ZBX-16433] CPU Cores ("system.cpu.num") reporting incorrect data

    task manager zabbix

  5. Task Scheduler Monitoring

    task manager zabbix

  6. Windows, Zabbix e etc: [Sobre o Windows 10] Gerenciador de Tarefas: 10 dicas para usar o Task

    task manager zabbix

VIDEO

  1. Task manager is the ultimate #pcgaming

  2. How to get into to task manager on windows/alienware

  3. Task Manager, End Task

  4. 1- Installing Zabbix using Ubuntu Server LAB1

  5. task manager? #windows

  6. Cloudstack + Zabbix + Incident manager 連携デモ

COMMENTS

  1. Zabbix task manager processes more than 75% busy

    We upped our ICMP Pollers to the maximum and the issue has been resolved. We were clearly trying to run too many ICMP polls concurrently. go_to_ellipsis-1. Zabbix 5.4.7 Proxy Server (PSQL) keeps throwing the trigger "Zabbix task manager processes more than 75% busy" There is only one host monitored by this proxy.

  2. Install and configure Zabbix Agent on Windows

    Open zabbix_agentd.conf with any editor, even Windows built-in notepad will do the job. Uncomment the following and update accordingly. ... Verify Zabbix agent service in the Task Manager. 6. Create a new Group on Zabbix Server. To add a host, we need to create a host group first. If you already have a group then you can skip this part.

  3. Zabbix low-level discovery

    Zabbix requires keys be unique for a single host, ... I've discovered that Get-Process command does not provide current CPU usage (as seen in task manager), I've decided to use Get-Counter command which provides necessary data. More over I'm using javasript to process data and it's working quite nice. I'm still looking forward into improvements ...

  4. Tutorial Zabbix

    Learn how to use Zabbix to monitor a Windows process. Our tutorial will teach you all the steps required to monitor the status of a Windows process.

  5. Zabbix

    | |Remote Zabbix server: Utilization of task manager internal processes, in %| The average percentage of the time during which the task manager processes have been busy for the last minute. |Dependent item|process.task_manager.avg.busy **Preprocessing** JSON Path: `$.data.process['task manager'].busy.avg`

  6. How to monitor windows "running" process in zabbix? : r/zabbix

    Zabbix is the ultimate enterprise-level software designed for real-time monitoring of millions of metrics collected from tens of thousands of servers, virtual machines and network devices. ... When this .exe stops responding and shows that window popup, I realized going to details under task manager, it always shows 48k in memory column .

  7. system.cpu.util shows different value than Task Manager on ...

    We are monitoring Windows servers with Zabbix agent. In some cases (not all) we see that the values collected by system.cpu.util are different from the Performance charts of the task manager and also when collecting the same value from the performance counters. Environment: Zabbix agent: 5.0.17; Zabbix server and proxy: 5.0.21 Steps to reproduce:

  8. zabbix/server_tasks.c at master · zabbix/zabbix · GitHub

    Real-time monitoring of IT components and services, such as networks, servers, VMs, applications and the cloud. - zabbix/server_tasks.c at master · zabbix/zabbix

  9. Task manager process for closing events fails if related ...

    In case if we ack a lot problems it is possible that related events will be deleted by housekeeper and when task manager will try to process it, it will fail. ... Powered by a free Atlassian Jira open source license for SIA Zabbix. Try Jira - bug tracking software for your team.

  10. Zabbix

    0. We fixed this on Zabbix 5.0 by Administration > General > Housekeeping (drop down) and changing all the 365 data storage periods to 183. That changed peak utilisation from 100% to 59% and average utilisation (housekeeping runs again an hour after it finished) from 6.7% to 0.56%.

  11. zabbix 5.0.5 perf_counter cpu utilization : r/zabbix

    Apparently the Windows 8+ and Server 2012+ includes a performance monitor counter named "% Processor Utility". And this is the one, that is shown in the Task Manager of Win 8+, and Win Server 2012+ as CPU Utilization. This counter unlike "% Processor Time", which is usually used to display the CPU usage, takes into account the balanced CPU speed.

  12. PDF Tips and Tricks on using useful features of Zabbix in large scale

    Task manager 90% Timer 50% Trapper 95% ipmp manager 95% icmp pinger 95% Unreachable poller 80% We initially thought that the auto-close mechanism might be the cause. Because process "task manager" seemed very busy. (near 100%) What problem occurred. Proposed to stop the mechanism of "Automatic close PROBLEM events".

  13. Zabbix 5.4: Report manager is disabled

    The URL should be in format <host>:<port>/report. Default port is 10053. /report path is mandatory and hardcoded, and so can not be changed. Next, Frontend URL parameter must be set. Go to Administration → General → Other parameters, and specify the full URL of the Zabbix web interface in the Frontend URL parameter.

  14. Challenges & Proposed Solution RCSTF PJM Reserve Requirements: April 17

    www.pjm.com | Public 2 PJM © 2024 Introduction •Overview of operational needs during normal days and actions that need to be taken during Conservative Operations days