Do you have Citrix or Windows RDP servers, and your users keep calling you because of problems? The first problem is to see which server the user was connected to. I solved this problem by monitoring the user connections on Windows Terminal Servers (including Citrix Servers), so that you know how many users are connected or disconnected, and how long they stay on any of your servers.
The plugin check_nrpe_windows_users gets all connected/disconnected Windows users and splits them by type, including Citrix/RDB (connected). The plugin connects over the NRPE protocol to the Windows server, where in NSClient++ you have to insert the following external command to get the Windows users:
[/settings/external scripts/scripts]
get_users=query user
Query User is a standard Windows command and is always available.
The above plugin should be scheduled by your monitoring daemon in this way:
This gets the Windows user via an NRPE executed query user command and shows the results. The parameters are:
-H|–host … host/IP on which to see users
-L|–ldap … host/IP of an LDAP server to be able to resolve names from logins
–verbose … list all users found and their state
–warning … warning threshold that will be triggered when value >= warning
–critical … critical threshold that will be triggered when found value >= critical
As seen above, you can also pass the LDAP server host/credentials so that the login names may be resolved into real names. You should do that only if you use the –verbose switch. Otherwise this is not needed.
The output of your verbose monitoring check will then look something like this:
I have over 20 years of experience in the IT branch. After first experiences in the field of software development for public transport companies, I finally decided to join the young and growing team of Würth Phoenix. Initially, I was responsible for the internal Linux/Unix infrastructure and the management of CVS software. Afterwards, my main challenge was to establish the meanwhile well-known IT System Management Solution WÜRTHPHOENIX NetEye. As a Product Manager I started building NetEye from scratch, analyzing existing open source models, extending and finally joining them into one single powerful solution. After that, my job turned into a passion: Constant developments, customer installations and support became a matter of personal. Today I use my knowledge as a NetEye Senior Consultant as well as NetEye Solution Architect at Würth Phoenix.
Author
Juergen Vigna
I have over 20 years of experience in the IT branch. After first experiences in the field of software development for public transport companies, I finally decided to join the young and growing team of Würth Phoenix. Initially, I was responsible for the internal Linux/Unix infrastructure and the management of CVS software. Afterwards, my main challenge was to establish the meanwhile well-known IT System Management Solution WÜRTHPHOENIX NetEye. As a Product Manager I started building NetEye from scratch, analyzing existing open source models, extending and finally joining them into one single powerful solution. After that, my job turned into a passion: Constant developments, customer installations and support became a matter of personal. Today I use my knowledge as a NetEye Senior Consultant as well as NetEye Solution Architect at Würth Phoenix.
When using Kibana in environments that require a proxy to reach external services, you might encounter issues with unrecognized SSL certificates. Specifically, if the proxy is exposed with its own certificate and acts as an SSL terminator, requests made by Read More
In a previous post we went through the configuration of Elastic Universal Profiling in NetEye, seeing how we can profile applications written in programming languages that do not compile to native code (for example Python, PHP, Perl, etc.) But what Read More
Elastic 8.16, which comes with NetEye 4.39, made Elastic Universal Profiling generally available for self-hosted installations. This means that NetEye SIEM installations will now be able to take advantage of the continuous profiling solution by Elastic. In this blog post Read More
In the first part of this series, we explored how Jira Service Management (JSM) helps streamline Incident Management, aligning with ITIL v4 best practices. Incident Management aims to restore normal service operation as quickly as possible after a disruption, ensuring Read More
Hello everyone! Today, I'd like to briefly discuss an improvement to the update and upgrade procedures that we've started to adopt with NetEye 4.39! What we wanted to improve One aspect that made quite an impact was that whenever the Read More