Need help on monitor Xenapp ICA sessions

[legends71]

Hi there,

I'm fairly new with Zabbix monitoring.
I just installed the Zabbix Appliance 2.04 en i want to monitor our Xenapp farm.
The standard counters are no problem but i would like to know if there is a way to monitor ICA serssion.
It can't be done with perf counters as far as i know.
I realy would like to know memory/cpu usage of a ICA session and/or which user has the higest CPU/mem.

Is there anyone who can point me to the right direction?

Kind Regards

[legends71]

Can anyone point me to the right directions?
Maybe a way to monitor process with userid cpu/mem?

[neilb]

Hi Legends
i setup up a couple of items for my xenapp servers which only allow ICA connections except by admins. Given the admin doesn't really log in, its mostly accurate.

items:
perf_counter["\Terminal Services\Active Sessions"]
perf_counter["\Terminal Services\Inactive Sessions"]
perf_counter[ "\Event Tracing for Windows\Total Number of Active Sessions"]

hope that helps.

N.

[neilb]

re usage, tackled this a different way.

set up counters to show me the iops, memory, usage count per defined application. Given i know which apps run on the farm, and as per previous post i know how many users i have on each machine, the data is sufficient for my needs. Yours may differ.

We're moving to XenDesktop 7 next, so the challenges will differ there.


eg
proc.num[xxx.exe]
proc_info[xxx.exe,io_read_op,avg]
proc_info[xxx.exe,io_read_op,avg]

then grouped this into logical graphs and then plugged into the respective screens.

interested to know if anyone has done better though.

N.

[steveboyson]

That seems to be quite tricky.
Zabbix relies somewhat on homogeneous and "all time available" items to perform it's checks.
Since XenApp sessions are highly dynamically, you need to work with discovery since you do not want to create items frequently but rather let zabbix do the job.

I would recommend - as mentioned by neilb - to monitor single processes rather than XenApp sessions.
But again, don't rely on PIDs as they are changing.

We monitor the number of published apps and their publishing status, besides general system parameter as CPU, memory and disk usage and license server usage (CCU).
We do not look into the user sessions.