The performance graphs present in NetEye are very useful for getting an immediate idea of the trend related to a service check, but they’re still limited to the metric being viewed.
Also, the “Show all graphs” option available from the Actions menu of each monitored Host can have different usage limits due to the presence of many service checks with performance graphs.
With the ITOA module and with some features of the NetEye web interface we can do much more.
In this blog post we’ll see how to display a custom dashboard for a limited family of hosts (Windows and Linux servers).
Have you ever tried Host and Service actions?
Host and Service actions are a rarely used feature, but they’ve got great potential. They can be managed by any NetEye user via the account settings and Navigation Items menu, and can help to extend NetEye functionality by contacting a URL (for example a wiki, a CRM or the NetEye ITOA module) which can be passed as a parameter a macro ($host.name$, $host.address$, …) and/or a custom property of the host or service check in use.
In the following example available in our online demo you’ll find several applications of extended Actions.
First of all you have to export and then import the two example Dashboards from our demo system to your NetEye Master node from the following URLs:
Now let’s create two Host actions that will allow us to open a custom Dashboard for all Windows hosts of the hostgroup “windows_servers”, and a different one for Linux hosts of the hostgroup “linux_servers”.
From our user’s account setting we need to select Navigation and then “Create a New Navigation Item”, choosing Host Action:
Later we’ll have to create two different Navigation Items: once for Windows servers and once for Linux Servers as follows.
For each Navigation Item you can define the following options:
Name: the name of the Navigation Item showed in the Actions section of the host/service
Shared: to share the Navigation Item with other users
Users: list of users to share the Navigation Item with (* for all)
Groups: list of groups to share the Navigation Item with (* for all)
Target: The target on which to open the Navigation Item URL
Url: the URL of the Navigation Item (where it’s possible to include macros and custom properties as in the following examples)
Windows URL: analytics/show?src=%2Fneteye%2Fanalytics%2Fgrafana%2Fd%2FNt1UMO4Vz%2Fserver-overview-windows%3ForgId%3D3%26var-hostname%3D$host.name$
Linux URL: analytics/show?src=%2Fneteye%2Fanalytics%2Fgrafana%2Fd%2FLy-IaVI4z%2Fserver-overview-linux%3ForgId%3D3%26var-hostname%3D$host.name$
Icon: the icon of the Navigation Item
Filter: to display the Action only for those objects matching this filter
In our examples, the filter is used to filter only Windows and Linux server hostgroups.
Grafana Window Dashboard Navigation item
Grafana Linux Dashboard Navigation item
Conclusions
At the end we should have the “Grafana Linux Dashboard” and “Grafana Windows Dashboard” Host Actions respectively for each host in the respective hostgroups, allowing you to open the dashboard with the metrics related to the selected host.
These Solutions are Engineered by Humans
Did you find this article interesting? Does it match your skill set? Our customers often present us with problems that need customized solutions. In fact, we’re currently hiring for roles just like this and others here at Würth Phoenix.
Hi everybody. I’m Giuseppe and I was born in Milan in 1979. Since the early years of university, I was attracted by the Open Source world and operating system GNU\Linux. After graduation I had the opportunity to participate in a project of a startup for the realization of an Internet Service Provider. Before joining Würth Phoenix (now Würth IT Italy) as SI consultant, I gained great experience as an IT consultant on projects related to business continuity and implementation of open source software compliant to ITIL processes of incident, change and service catalog management. My free time is completely dedicated to my wife and, as soon as possible, run away from Milan and his caotic time and trekking discover our beautiful mountain near Lecco for relax and lookup the (clean) sky.
Author
Giuseppe Di Garbo
Hi everybody. I’m Giuseppe and I was born in Milan in 1979. Since the early years of university, I was attracted by the Open Source world and operating system GNU\Linux. After graduation I had the opportunity to participate in a project of a startup for the realization of an Internet Service Provider. Before joining Würth Phoenix (now Würth IT Italy) as SI consultant, I gained great experience as an IT consultant on projects related to business continuity and implementation of open source software compliant to ITIL processes of incident, change and service catalog management. My free time is completely dedicated to my wife and, as soon as possible, run away from Milan and his caotic time and trekking discover our beautiful mountain near Lecco for relax and lookup the (clean) sky.
Today we continue our journey into monitoring automation in NetEye. In my previous post we discussed the possibility of automating Business Processes. As you may remember, for those of us working on NetEye Cloud monitoring dozens of clients, it's important Read More
When performance degradation occurs within a complex system, understanding the root cause can be extremely challenging. If the issue happens sporadically, this difficulty increases even more. This is because modern systems involve numerous components that interact in complex ways. For Read More
At first glance, rebuilding an RPM may sound like a purely mechanical task: take a patch, rebuild the package, ship it. In reality, that small fix goes through a much longer journey that touches reliability, security, trust, and long-term maintainability. Read More
Introduction to NetApp and S3 NetApp offers a unified data storage system. NetApp's ONTAP operating system supports a combination of file, block, and object protocols. We can use common storage (disk array), such as NetApp AFF or FAS, and operate Read More
A safer way to run privileged Windows checks with SystemRunner If you’ve been monitoring Windows for a while, you’ve probably seen this pattern: some checks must run as LocalSystem (S-1-5-18), and the “quick fix” is to run the Icinga Agent Read More