Wmi exporter prometheus windows

In this article we will monitor windows server with prometheus wmi_exporter. With linux server, you can read my following article.

Recommended Reading: Monitor linux server with Prometheus node exporter

Install wmi_exporter on windows server

First, you need to check the version to install at this link. The current version is v0.13.0.

Log in to the windows server you need to monitor, download the msi installation package with the link below.

https://github.com/prometheus-community/windows_exporter/releases/download/v0.13.0/windows_exporter-0.13.0-amd64.msi

After downloading, install the software like you install other software. Double click on the installation file and next until finished.

Then, open Task Manager and go to the Processes tab, find the windows_exporter process and see if it is running. If the process is running, it is ok.

Картинка с сайта: devopslite.com

Now the windows exporter will run on port 9182. You need to open the firewall on the windows server to allow access to port 9182.

Set up prometheus configuration

And now, we will set up prometheus to call the windows exporter on the windows server.

You open the configuration file.

nano /etc/prometheus/prometheus.yml

You add the content below at the end of the file.

  - job_name: 'wmi_exporter'
    metrics_path: /metrics
    scrape_interval: 5s
    static_configs:
    - targets:
      - hostname-winserver:9182

Next, find the paragraph below and declare the rule alert file path for the windows server.

# Load rules once and periodically evaluate them according to the global 'evaluation_interval'.
rule_files:
  # - "first_rules.yml"
  # - "second_rules.yml"
    - "/etc/prometheus/rules/windows.yml"

After editing, save the file but do not reload or restart the prometheus service.

Set up the alert server windows rule file

As you can see above, we set up prometheus to call a file containing alert rules for the windows server.

Now you create the file as below.

nano /etc/prometheus/rules/windows.yml

Then you use the rule structure as below to add it to the file.

groups:
- name: Windows Server
  rules:
  - alert: Server Windows Down
    expr: up{job="wmi_exporter"} == 0
    for: 10s
    labels:
      severity: "Critical"
    annotations:
      Summary: 'Server "{{ $labels.instance }}" down.'

You can download the full rule file for windows server at my gitlab link.

Now you have reloaded the prometheus service.

systemctl reload prometheus

Set up the Grafana monitor server windows dashboard

You can import and use the dashboard with ID 10467. However, this dashboard is displayed in Chinese.

If you want to use English, you can download the json file from my gitlab and import it.

Conclusion

Very fast and simple, isn’t it? You can now set up monitor server windows easily. Grafana provides you with a complete interface to view resources on the server. Alertmanager will ensure to send you notifications when the server has resource problems.

In this article we are going to cover How Install Install Prometheus and Grafana on Windows with WMI Exporter, Configure Prometheus as Grafana DataSource.

What is prometheus?

• Prometheus is a open source Linux Server Monitoring tool mainly used for metrics monitoring, event monitoring, alert management, etc.
• Prometheus has changed the way of monitoring systems and that is why it has become the Top-Level project of Cloud Native Computing Foundation (CNCF).
• Prometheus uses a powerful query language i.e. “PromQL”.
• In Prometheus tabs are on and handles hundreds of services and microservices.
• Prometheus use multiple modes used for graphing and dashboarding support.

Why we used prometheus?

• A multi-dimensional data model with time series data identified by metric name and key/value pairs
• PromQL, a flexible query language to leverage this dimensionality
• Pushing time series is supported via an intermediary gateway
• Multiple modes of graphing and dashboarding support

Prometheus Architecture 

Картинка с сайта: www.fosstechnix.com

• As above we can see an architecture of Prometheus monitoring tool.
• We made a basic design to understand it easily for you people.

Now lets understand the Prometheus components one-by-one

Prometheus Components

1. Prometheus Server

• Prometheus server is a first component of Prometheus architecture.
• Prometheus server is a core of Prometheus architecture which is divided into several parts like Storage, PromQL, HTTP server, etc.
• In Prometheus server data is scraped from the target nodes and then stored in the database.

1.a. Storage

• Storage in Prometheus server has a local on disk storage.
• Prometheus has many interfaces that allow integrating with remote storage systems.

1.b. PromQL

• Prometheus uses its own query language i.e. PromQL which is a very powerful querying language.
• PromQL allows the user to select and aggregate the data.

2. Service Discovery

• Next and very important component of Prometheus Server is the Service Discovery.
• With the help of Service discovery the services are identified which need to be scraped.
• To Pull metrics, identification of services and finding the targets are compulsory needed.
• Through Service discovery we monitor the entities and can also locate its targets.

3. Scrape Target

• Once the services are identified and the targets are ready then we can pull metrics from it and can scrape the target.
• We can export the data of the end point using node exporters.
• Once the metrics or other data is pulled, Prometheus stores it in a local storage.

4. Alert Manager

• Alert Manager handles the alerts which may occurs during the session.
• Alert manager handles all the alerts which are sent by the Prometheus server.
• Alert manager is one of the very useful components of the Prometheus tool.
• If in case any big error or any issue occurs, alert manager manage those alerts and contact with human via E-mail, Text Messages, On-call, or any other chat application service.

5. User Interface

• User interface is also an important component as it builds a bridge between the user and the system.
• In Prometheus, user interfaces are note that much user friendly and can be used till graph queries.
• For good exclusive dashboards Prometheus works together with Grafana (visualization tool).
• Using Grafana over Prometheus to visualize properly we can use custom dashboards.
• Grafana dashboards display via pie charts, line charts, tables, good data graphs of CPU usage, RAM utilization, network load, etc with indicators.
• Grafana supports and run with Prometheus by querying language i.e. PromQL.
• To fetch data from Prometheus and to display the results on Grafana dashboards PromQL is used.

What is Grafana ?

• Grafana is a free and open source visualization tool mostly used with Prometheus to which monitor metrics.
• Grafana provides various dashboards, charts, graphs, alerts for the particular data source.
• Grafana allows us to query, visualize, explore metrics and set alerts for the data source which can be a system, server, nodes, cluster, etc.
• We can also create our own dynamic dashboard for visualization and monitoring.
• We can save the dashboard and can even share with our team members which is one of the main advantage of Grafana.

What is WMI Exporter?

• It is same like Node Exporter but Node Exporter for Linux and WMI Exporter for Windows
• WMI Exporter is an exporter utilized for windows servers to collects metrics like CPU usage, memory, and Disk usage.
• It is open-source which can be installed on Windows servers using the .msi installer

Prerequisite: 

• Good internet connectivity 
• Security Groups Configured properly
• Any web Browser

Security Groups Configured on EC2 Instances

• Port 9090 — Prometheus Server
• Port 9182—-WMI Exporter
• Port 3000 — Grafana

#1. Download Prometheus for windows

Now we will download the latest version of Prometheus. We can copy the download link as per our Operating System from Prometheus download page

Using the below command we can download Prometheus, here we are downloading Prometheus 2.32.1 version, you use the above link to download specific version.

Картинка с сайта: www.fosstechnix.com

We have to install prometheus service but in windows we can not installl prometheus as a service for that here im using NSSM package to install Prometheus service 

Open your command prompt run as administrator 

Paste the directory path like below command:

cd c:\users\Administrator\Downloads\nssm-2.24\nssm-2.24\win64

dir

nssm.exe install prometheus<<and your prometheus application directory path>> \prometheus

Картинка с сайта: www.fosstechnix.com

Now Prometheus is successfully installed in your machine

So let’s check the status in prometheus service on windows.

Картинка с сайта: www.fosstechnix.com

For now Prometheus is stop after changing in configuration file we will start prometheus

After installation now we are going to install Grafana on Window

#2. Install Grafana on Windows

Now we will download the latest version of Grafana.from official page of Grafana select window operating system and download .msi installer

Картинка с сайта: www.fosstechnix.com

After download of grafana we will install grafana on window

Картинка с сайта: www.fosstechnix.com

After installation of Grafana go to C:<<Program Files<<GrafanaLabs<<Grafana<< conf<<defaults

In default change the smtp enabled false replace with true you can check the below image

Картинка с сайта: www.fosstechnix.com

To access Grafana Dashboard open your favorite browser, type server IP or Name followed by grafana default port 3000.

http://localhost:3000

Here you can see Login page of Grafana now you will have to login with below Grafana default UserName and Password.

Username – admin

Password – admin

Картинка с сайта: www.fosstechnix.com

It is always a good practice to change your login credentials.

Картинка с сайта: www.fosstechnix.com

Provide your New Password and click on Change Password

Now here you can see Home Dashboard page of Grafana

Картинка с сайта: www.fosstechnix.com

#3. Install WMI Exporter on Windows

For Windows hosts, you are going to use the Windows exporter.

You can download the latest version of windows installer from here

Картинка с сайта: www.fosstechnix.com

When the download is done, simply click on the MSI file and start running the installer.

Картинка с сайта: www.fosstechnix.com

After Installation of WMI Exporter lets check its successfully installed or not

So go to services and search windows exporter.

Make sure windows exporter service is running.

Картинка с сайта: www.fosstechnix.com

Now that your exporter is running, it should start exposing metrics on

http://localhost:9182/metrics

So let’s check

Картинка с сайта: www.fosstechnix.com

#4. Update Prometheus Configuration file

Go to the Prometheus file and open Prometheus.yml file and 

Update config file with below code:

 - job_name: "WMI Exporter"

    # metrics_path defaults to '/metrics'
    # scheme defaults to 'http'.

    static_configs:
      - targets: ["Host_ip:9182"]

Now save the file and exit

After changing in config file you need to start prometheus server 

So go the services and start the Prometheus Server

Картинка с сайта: www.fosstechnix.com

Hit the URL in your web browser to check weather our target is successfully scraped by Prometheus or not

https://localhost:9090/targets

Картинка с сайта: www.fosstechnix.com

#4. Configure Prometheus as Grafana DataSource

Once you logged into Grafana Now first Navigate to Settings Icon ->> Configuration ->> data sources

Картинка с сайта: www.fosstechnix.com

Now lets click on Add Data sources and select Prometheus

Картинка с сайта: www.fosstechnix.com

Now configure Prometheus data source by providing Prometheus URL

Картинка с сайта: www.fosstechnix.com

As per your requirement you can do other changes or you can also keep remaining configuration as default.

Now click on Save & test so it will prompt a message Data Source is working.

Картинка с сайта: www.fosstechnix.com

#5.Creating Grafana Dashboard to monitor Windows server

Now lets build a dashboard in Grafana so then it will able to reflect the metrics of the Windows system.

So we will use 14510 to import Grafana.com, Lets come to Grafana Home page and you can see a “+” icon. Click on that and select “Import”

Картинка с сайта: www.fosstechnix.com

On the next window, simply enter the dashboard ID in the corresponding field 

Картинка с сайта: www.fosstechnix.com

Now provide the name and select the Prometheus Datasource and click on Import.

Картинка с сайта: www.fosstechnix.com

There you are done with the setup. Now your Dashboard is running up!.

Картинка с сайта: www.fosstechnix.com

Conclusion:

In this article we have covered How Install Install Prometheus and Grafana on Windows with WMI Exporter, Configure Prometheus as Grafana DataSource.

Related Articles:

• Install Prometheus and Grafana on Ubuntu 20.04 LTS
• Kubernetes cluster Monitoring with Prometheus and Grafana.
• How to Install Nagios Core on CentOS 7

Guys who are working as a DevOps engineer or a Site Reliability Engineer should aware of various techniques to monitor their Windows servers. If you are familiar with such tasks then you can easily solve your windows server down issues.

You may get some random doubts whenever your serves go down like Is it due to the high CPU usage on one of the processes? Is the RAM used too much on my Windows server? or Is the server having some memory issues?

To clarify all these queries today we have come up with a new interesting tutorial ie., Windows Server Monitoring using Prometheus and WMI Exporter.

If you are not having an overview of Prometheus Monitoring, check out this Definitive Guide by clicking on the link and start learning about the monitoring of windows servers with Prometheus and WMI Exporter.

Are you ready to monitor your Windows Servers? If yes, then go through these direct links for quick access to the main concept of this tutorial.

• Windows Server Monitoring Architecture
• Installing Prometheus
• Installing the WMI Exporter
  • a – Downloading the WMI Exporter MSI
  • b – Running the WMI installer
  • c – Observing Windows Server metrics
  • d – Binding Prometheus to the WMI exporter
• Building an Awesome Grafana Dashboard
  • a – Importing a Grafana dashboard
• Raising alerts in Grafana on high CPU usage
  • a – Creating a Slack webhook
  • b – Set Slack as a Grafana notification channel
  • c – Building a PromQL query
  • d – Creating a Grafana alert

What is WMI Exporter?

WMI Exporter is an exporter utilized for windows servers to collects metrics like CPU usage, memory, and Disk usage.

It is open-source which can be installed on Windows servers using the .msi installer

Prerequisites

If you want to follow this tutorial, then you require the following stuff:

• One Linux server set up
• Prometheus 2.x installed on your server, including the Prometheus Web UI.
• Check out your Prometheus version by running the Prometheus -version command. The output comprises your Prometheus version as well as build information.

Windows Server Monitoring Architecture

Before installing the WMI exporter, let’s have a quick look at what our final architecture looks like.

As a reminder, Prometheus is constantly scraping targets.

Targets are nodes that are exposing metrics on a given URL, accessible by Prometheus.

Such targets are equipped with “exporters”: exporters are binaries running on a target and responsible for getting and aggregating metrics about the host itself.

If you were to monitor a Linux system, you would run a “Node Exporter“, which would be responsible for gathering metrics about the CPU usage or the disk I/O currently in use.

• MongoDB Monitoring with Grafana & Prometheus | Mongodb Prometheus Grafana Dashboard
• How To Install Prometheus with Docker on Ubuntu 18.04
• Complete Node Exporter Mastery with Prometheus | Monitoring Linux Host Metrics WITH THE NODE EXPORTER

For Windows hosts, you are going to use the WMI exporter.

The WMI exporter will run as a Windows service and it will be responsible for gathering metrics about your system.

In short, here is the final architecture that you are going to build.

Картинка с сайта: www.junosnotes.com

Installing Prometheus

The complete Prometheus installation for Linux was already covered in one of our previous articles. Check out our Prometheus tutorials main page or else click on this direct link How To Install Prometheus with Docker on Ubuntu 18.04

Ensure to read it extensively to have your Prometheus instance up and running.

To verify it, head over to http://localhost:9090 (9090 being the default Prometheus port).

You should see a Web Interface similar to this one.

If this is the case, it means that your Prometheus installation was successful.

Картинка с сайта: www.junosnotes.com

Great!

Now that your Prometheus is running, let’s install the WMI exporter on your Windows Server.

Installing the WMI Exporter

The WMI exporter is an awesome exporter for Windows Servers.

It will export metrics such as CPU usage, memory, and disk I/O usage.

The WMI exporter can also be used to monitor IIS sites and applications, the network interfaces, the services, and even the local temperature!

If you want a complete look at everything that the WMI exporter offers, have a look at all the collectors available.

In order to install the WMI exporter, head over to the WMI releases page on GitHub.

a – Downloading the WMI Exporter MSI

As of August 2019, the latest version of the WMI exporter is 0.8.1.

Картинка с сайта: www.junosnotes.com

On the releases page, download the MSI file corresponding to your CPU architecture.

In my case, I am going to download the wmi_exporter-0.8.1-amd64.msi file.

b – Running the WMI installer

When the download is done, simply click on the MSI file and start running the installer.

This is what you should see on your screen.

Картинка с сайта: www.junosnotes.com

Windows should now start configuring your WMI exporter.

You should be prompted with a firewall exception. Make sure to accept it for the WMI exporter to run properly.

The MSI installation should exit without any confirmation box. However, the WMI exporter should now run as a Windows service on your host.

To verify it, head over to the Services panel of Windows (by typing Services in the Windows search menu).

In the Services panel, search for the “WMI exporter” entry in the list. Make sure that your service is running properly.

Картинка с сайта: www.junosnotes.com

c – Observing Windows Server metrics

Now that your exporter is running, it should start exposing metrics on

Open your web browser and navigate to the WMI exporter URL. This is what you should see in your web browser.

Some metrics are very general and exported by all the exporters, but some of the metrics are very specific to your Windows host (like the wmi_cpu_core_frequency_mhz metric for example)

Картинка с сайта: www.junosnotes.com

Great!

Now, Windows Server monitoring is active using the WMI exporter.

If you remember correctly, Prometheus scrapes targets.

As a consequence, we have to configure our Windows Server as a Prometheus target.

This is done in the Prometheus configuration file.

d – Binding Prometheus to the WMI exporter

As you probably saw from your web browser request, the WMI exporter exports a lot of metrics.

As a consequence, there is a chance that the scrape request times out when trying to get the metrics.

This is why we are going to set a high scrape timeout in our configuration file.

If you want to keep a low scrape timeout, make sure to configure the WMI exporter to export fewer metrics (by specifying just a few collectors for example).

Head over to your configuration file (mine is located at /etc/prometheus/prometheus.yml) and edit the following changes to your file.

scrape_configs:
# The job name is added as a label `job=<job_name>` to any timeseries scraped from this config.
  - job_name: 'prometheus'

    # Careful, the scrape timeout has to be lower than the scrape interval.
    scrape_interval: 6s
    scrape_timeout: 5s
    static_configs:
            - targets: ['localhost:9090', 'localhost:9216']

Save your file, and restart your Prometheus service.

$ sudo systemctl restart prometheus
$ sudo systemctl status prometheus

Head back to the Prometheus UI, and select the “Targets” tab to make sure that Prometheus is correctly connected to the WMI exporter.

Картинка с сайта: www.junosnotes.com

If you are getting the following error, “context deadline exceeded”, make sure that the scrape timeout is set in your configuration file.

Great! Our Windows Server monitoring is almost ready.

Now it is time for us to start building an awesome Grafana dashboard to monitor our Windows Server.

Building an Awesome Grafana Dashboard

Complete MySQL dashboard with Grafana & Prometheus and MongoDB Monitoring with Grafana & Prometheus are some of our previous guides on Prometheus & Grafana installation. Make sure to configure your Grafana properly before moving to the next section.

If you are looking to install Grafana on Windows, here is another guide for it.

Prometheus should be configured as a Grafana target and accessible through your reverse proxy.

a – Importing a Grafana dashboard

In Grafana, you can either create your own dashboards or you can use pre-existing ones that contributors already crafted for you.

In our case, we are going to use the Windows Node dashboard, accessible via the 2129 ID.

Head over to the main page of Grafana (located at http://localhost:3000 by default), and click on the Import option in the left menu.

In the next window, simply insert the dashboard ID in the corresponding text field.

Картинка с сайта: www.junosnotes.com

From there, Grafana should automatically detect your dashboard as the Windows Node dashboard. This is what you should see.

Картинка с сайта: www.junosnotes.com

Select your Prometheus datasource in the “Prometheus” dropdown, and click on “Import” for the dashboard to be imported.

Картинка с сайта: www.junosnotes.com

Awesome!

An entire dashboard displaying Windows metrics was created for us in just one click.

As you can see, the dashboard is pretty exhaustive.

You can monitor the current CPU load, but also the number of threads created by the system, and even the number of system exceptions dispatched.

Картинка с сайта: www.junosnotes.com

On the second line, you have access to metrics related to network monitoring. You can for example have a look at the number of packets sent versus the number of packets received by your network card.

It can be useful to track anomalies on your network, in case of TCP flood attacks on your servers for example.

Картинка с сайта: www.junosnotes.com

On the third line, you have metrics related to the disk I/O usage on your computer.

Those metrics can be very useful when you are trying to debug applications (for example ASP.NET applications). Using those metrics, you can see if your application consumes too much memory or too much disk.

Картинка с сайта: www.junosnotes.com

Finally, one of the greatest panels has to be memory monitoring. RAM has a very big influence on the overall system performance.

Consequently, it has to be monitored properly, and this is exactly what the fourth line of the dashboard does.

Картинка с сайта: www.junosnotes.com

That’s an awesome dashboard, but what if we want to be alerted whenever the CPU usage is too high for example?

Wouldn’t it be useful for our DevOps teams to know about it in order to see what’s causing the outage on the machine?

This is what we are going to do in the next section.

Raising alerts in Grafana on high CPU usage

As discussed in the previous section, you want alerts to be raised when the CPU usage is too high.

Grafana is equipped with an alerting system, meaning that whenever a panel raises an alert it will propagate the alert to “notification channels“.

Notification channels are Slack, your internal mailing system of PagerDuty for example.

In this case, we are going to use Slack as it is a pretty common team productivity tool used in companies.

a – Creating a Slack webhook

For those who are not familiar with Slack, you can create webhooks that essentially address for external sources to reach Slack.

As a consequence, Grafana will post the alert to the Webhook address, and it will be displayed in your Slack channel.

To create a Slack webhook, head over to your Slack apps page.

Картинка с сайта: www.junosnotes.com

Click on the name of your app (“devconnected” here). On the left menu, click on “Incoming Webhooks”.

On the next page, simply click on “Add New Webhook to Workspace“.

Картинка с сайта: www.junosnotes.com

On the next screen, choose where you want your alert messages to be sent. In this case, I will choose the main channel of my Slack account.

Картинка с сайта: www.junosnotes.com

Click on “Allow”. From there, your Slack Webhook URL should be created.

Картинка с сайта: www.junosnotes.com

b – Set Slack as a Grafana notification channel

Copy the Webhook URL and head over to the Notifications Channels window of Grafana. This option is located in the left menu.

Click on the option, and you should be redirected to the following window.

Картинка с сайта: www.junosnotes.com

Click on “Add channel”. You should be redirected to the notification channel configuration page.

Copy the following configuration, and change the webhook URL with the one you were provided with in the last step.

Картинка с сайта: www.junosnotes.com

When your configuration is done, simply click on “Send Test” to send a test notification to your Slack channel.

Картинка с сайта: www.junosnotes.com

Great! Your notification channel is working properly.

Let’s create a PromQL query to monitor our CPU usage.

c – Building a PromQL query

If you are not familiar with PromQL, there is a section dedicated to this language in my Prometheus monitoring tutorial.

When taking a look at our CPU usage panel, this is the PromQL query used to display the CPU graph.

Картинка с сайта: www.junosnotes.com

First, the query splits the results by the mode (idle, user, interrupt, DPC, privileged). Then, the query computes the average CPU usage for a five minutes period, for every single mode.

In the end, the modes are displayed with aggregated sums.

In my case, my CPU has 8 cores, so the overall usage sums up to 8 in the graph.

If I want to be notified when my CPU usage peaks at 50%, you essentially want to trigger an alert when the idle state goes below 4 (as 4 cores are going to be fully used).

To monitor our CPU usage, we are going to use this query

sum by (mode) (rate(wmi_cpu_time_total{instance=~"localhost:9182", mode="idle"}[5m]))

I am not using a template variable here for the instance as they are not supported by Grafana for the moment.

This query is very similar to the one already implemented in the panel, but it specifies that we specifically want to target the “idle” mode of our CPU.

Replace the existing query with the query we just wrote.

This is what you should now have in your dashboard.

Картинка с сайта: www.junosnotes.com

Now that your query is all set, let’s build an alert for it.

d – Creating a Grafana alert

In order to create a Grafana alert, click on the bell icon located right under the query panel.

In the rule panel, you are going to configure the following alert.

Every 10 seconds, Grafana will check if the average CPU usage for the last 10 seconds was below 4 (i.e using more than 50% of our CPU).

If it is the case, an alert will be sent to Slack, otherwise, nothing happens.

Картинка с сайта: www.junosnotes.com

Finally, right below this rule panel, you are going to configure the Slack notification channel.

Картинка с сайта: www.junosnotes.com

Now let’s try to bump the CPU usage on our instance.

Картинка с сайта: www.junosnotes.com

As the CPU usage goes below the 4 thresholds, it should set the panel state to “Alerting” (or “Pending” if you specified a “For” option that is too long).

From there, you should receive an alert in Slack.

Картинка с сайта: www.junosnotes.com

As you can see, there is even an indication of the CPU usage (73% in this case).

Great! Now our DevOps is aware that there is an issue on this server and they can investigate what’s happening exactly.

Conclusion

As you can see, monitoring Windows servers can easily be done using Prometheus and Grafana.

With this tutorial, you had a quick overview of what’s possible with the WMI exporter. So what’s next?

From there, you can create your own visualizations, your own dashboards, and your own alerts.

Our monitoring section contains a lot of examples of what’s possible and you can definitely take some inspiration from some of the dashboards.

Until then, have fun, as always.

Уровень сложностиПростой

Время на прочтение3 мин

Количество просмотров9.9K

Картинка с сайта: habr.com

Авторы: Никита Зубарев — DevOps Team Leader компании Hostkey, Айрат Сягитов — специалист отдела DevOps компании Hostkey 

Картинка с сайта: habr.com

Ранее мы рассказали о том, как выполняется мониторинг Linux-систем. Теперь рассмотрим, как настроить Windows Server.

В одной из прошлых статей мы говорили об интеграции FreeIPA с Active Directory. В процессе разработки решения, описанного в этой статье, у нас возникла потребность снимать метрики с серверов Windows-инфраструктуры. В данной статье мы рассмотрим, как можно наладить мониторинг для серверов с ОС Windows, используя существующую систему, построенную на связке Prometheus + Grafana + Alertmanager. Собирать будем общие системные метрики: cpu, ram, hdd. 

Экспортер WMI также можно использовать для мониторинга сайтов и приложений IIS, сетевых интерфейсов, служб и даже локальной температуры.

Установка Windows Exporter для мониторинга служб Windows

Для установки Windows Exporter необходимо выполнить несколько действий:

1. Скачать последнюю версию Windows Exporter с GitHub, выбрав архив .zip или .tar.gz.

2. Создать папку с именем «Prometheus» на диске C или в другом месте. 

3. Распаковать скачанный архив Windows Exporter. В нем находится файл windows_exporter.exe.

4. Скопировать windows_exporter.exe в папку “Prometheus”.

Затем необходимо создать конфигурационный файл YAML для Windows Exporter. Он позволит указать службы, которые необходимо поставить на мониторинг.

В нашем примере это сервис LicenseManager.

Картинка с сайта: habr.com

Windows Exporter можно запустить двумя способами: вручную и в качестве службы Windows.

1. Для запуска вручную необходимо:

• Открыть командную строку от имени администратора.

• Перейти в папку с windows_exporter.exe, например: cd C:\Prometheus.

• Запустить Windows Exporter с указанием конфигурационного файла с помощью команды: .\windows_exporter.exe —config.windowsconfig=»kms.yml».

• Теперь Windows Exporter будет работать в режиме мониторинга в текущей сессии.

2. Для настройки как службы Windows необходимо:

• Открыть командную строку от имени администратора.

• Создать службу Windows Exporter командой:

 sc create WindowsExporter binPath= "C:\Prometheus\windows_exporter.exe --config.windowsconfig=C:\Prometheus\kms.yml" start= auto.

• Запустить службу командой sc start WindowsExporter:

A:\Windows\system32>sc create WindowsExporter binpath= "C:\Prometheus\windows_exporter.exe --config.windowsconfig=C:\Prometheus\windows_exporter.yml"=auto
[SC] CreateService: success

A:\Windows\system32>sc start WindowsExporter

Подробную информацию о средстве экспорта WMI можно посмотреть на GitHub.

После установки необходимого экспортера следует перейти в панель «Службы Windows» (достаточно просто ввести «Службы» в меню поиска Windows) и найти в списке запись WMI exporter. Далее необходимо проверить, что сервис работает правильно.

Картинка с сайта: habr.com

Если экспортер запущен, он должен начать предоставлять метрики на http://localhost:9182/metrics, по аналогии с Node Exporter. Остается подключить сбор метрик в Prometheus, добавить дашборд и настроить алертинг:

Картинка с сайта: habr.com

Добавить в prometheus.yml:

  - job_name: 'Windows_Infra'
    static_configs:
      - targets: ['”localhost”:9182'] 

Добавить Grafana dashboard, который отслеживает отображение информационной панели, подключает и оптимизирует вывод подробной сводки ресурсов. В результате получаем визуальную панель по каждому хосту:

Картинка с сайта: habr.com

Осталось описать rule_files, добавив необходимые метрики:

groups:
- name: Windows_Infra
  rules:
  - alert: InstanceDown
    expr: up{job="Windows_Infra"} == 0
    for: 5m
    labels:
      severity: page
    annotations:
      summary: "Instance {{ .instance }} down"
      description: "{{ .instance }} of job {{ .job }} has been down for more than 5 minutes."

  - alert: DiskSpaceUsage
    expr: 100.0 - 100 * (windows_logical_disk_free_bytes{job="Windows_Infra"} / windows_logical_disk_size_bytes{job="Windows_Infra"}) > 90
    for: 10m
    labels:
      severity: high
    annotations:
      summary: "Disk Space Usage (instance {{ $labels.instance }})"
      description: "Disk Space on Drive is used more than 90%\n  VALUE = {{ $value }}\n  LABELS: {{ $labels }}"

Аналогичным образом добавляем другие необходимые параметры. При настроенном Alertmanager сообщения нотификаций автоматически будут приходить в подключенные системы.

Как видите, мониторинг серверов Windows можно легко выполнить с помощью Prometheus и Grafana. Это решение значительно упрощает процесс управления большим парком машин и позволяет оперативно решать проблемы, возникающие при администрировании серверного оборудования в нашей компании.В следующих статьях рассмотрим задачу подключения служб Windows.

Арендуйте выделенные и виртуальные серверы с моментальным деплоем в надежных дата-центрах класса TIER III в Москве и Нидерландах. Принимаем оплату за услуги HOSTKEY в Нидерландах в рублях на счет российской компании. Оплата с помощью банковских карт, в том числе и картой МИР, банковского перевода и электронных денег.