What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Multiple Channels from WMI

Votes:

0

I am trying to create a multi channel sensor from WMI on ta remote probe querying the local server The PerfCounter Custom fails when I give these strings

\\ServerName\refs(d:)\delete queue entries::#
\\ServerName\refs(d:)\dirty table list entries::#
\\ServerName\refs(d:)\dirty metadata pages::#
\\ServerName\refs(d:)\container move failure count ::#
\\ServerName\refs(d:)\compaction failure count::#
\\ServerName\refs(d:)\container moves failed due to ineligible container::#
\\ServerName\refs(d:)\container move retry count::#
\\ServerName\refs(d:)\compactions failed due to max fragmentation ::#
\\ServerName\refs(d:)\compactions failed due to ineligible container ::#
\\ServerName\refs(d:)\compacted container fill ratio (%) ::#
\\ServerName\refs(d:)\compaction write latency (100 ns)::#
\\ServerName\refs(d:)\compaction read latency (100 ns)::#
\\ServerName\refs(d:)\data compactions/sec::#
\\ServerName\refs(d:)\trim latency (100 ns)::#
\\ServerName\refs(d:)\log fill percentage ::#
\\ServerName\refs(d:)\current fast tier metadata fill percentage::#
\\ServerName\refs(d:)\current slow tier metadata fill percentage::#
\\ServerName\refs(d:)\log writes/sec::#
\\ServerName\refs(d:)\checkpoints/sec::#
\\ServerName\refs(d:)\tree updates/sec ::#
\\ServerName\refs(d:)\checkpoint latency (100 ns)::#
\\ServerName\refs(d:)\tree update latency (100 ns) ::#
\\ServerName\refs(d:)\fast tier destaged container fill ratio (%) ::#
\\ServerName\refs(d:)\slow tier destaged container fill ratio (%) ::#
\\ServerName\refs(d:)\fast tier destage write latency (100 ns) ::#
\\ServerName\refs(d:)\fast tier destage read latency (100 ns)::#
\\ServerName\refs(d:)\slow tier destage write latency (100 ns) ::#
\\ServerName\refs(d:)\slow tier destage read latency (100 ns)::#
\\ServerName\refs(d:)\current fast tier data fill percentage::#
\\ServerName\refs(d:)\current slow tier data fill percentage::#
\\ServerName\refs(d:)\container destages from fast tier/sec ::#
\\ServerName\refs(d:)\container destages from slow tier/sec ::#
\\ServerName\refs(d:)\allocation of data clusters on slow tier/sec::#
\\ServerName\refs(d:)\allocation of data clusters on fast tier/sec::#
\\ServerName\refs(d:)\allocation of metadata clusters on slow tier/sec::#
\\ServerName\refs(d:)\allocation of metadata clusters on fast tier/sec::#
\\ServerName\refs(d:)\data in place write clusters/sec::#

Or these

\refs(d:)\delete queue entries::#
\refs(d:)\dirty table list entries::#
\refs(d:)\dirty metadata pages::#
\refs(d:)\container move failure count ::#
\refs(d:)\compaction failure count::#
\refs(d:)\container moves failed due to ineligible container::#
\refs(d:)\container move retry count::#
\refs(d:)\compactions failed due to max fragmentation ::#
\refs(d:)\compactions failed due to ineligible container ::#
\refs(d:)\compacted container fill ratio (%) ::#
\refs(d:)\compaction write latency (100 ns)::#
\refs(d:)\compaction read latency (100 ns)::#
\refs(d:)\data compactions/sec::#
\refs(d:)\trim latency (100 ns)::#
\refs(d:)\log fill percentage ::#
\refs(d:)\current fast tier metadata fill percentage::#
\refs(d:)\current slow tier metadata fill percentage::#
\refs(d:)\log writes/sec::#
\refs(d:)\checkpoints/sec::#
\refs(d:)\tree updates/sec ::#
\refs(d:)\checkpoint latency (100 ns)::#
\refs(d:)\tree update latency (100 ns) ::#
\refs(d:)\fast tier destaged container fill ratio (%) ::#
\refs(d:)\slow tier destaged container fill ratio (%) ::#
\refs(d:)\fast tier destage write latency (100 ns) ::#
\refs(d:)\fast tier destage read latency (100 ns)::#
\refs(d:)\slow tier destage write latency (100 ns) ::#
\refs(d:)\slow tier destage read latency (100 ns)::#
\refs(d:)\current fast tier data fill percentage::#
\refs(d:)\current slow tier data fill percentage::#
\refs(d:)\container destages from fast tier/sec ::#
\refs(d:)\container destages from slow tier/sec ::#
\refs(d:)\allocation of data clusters on slow tier/sec::#
\refs(d:)\allocation of data clusters on fast tier/sec::#
\refs(d:)\allocation of metadata clusters on slow tier/sec::#
\refs(d:)\allocation of metadata clusters on fast tier/sec::#
\refs(d:)\data in place write clusters/sec::#
}}}

How can I use the XML Custom EXE/Script Sensor using powershell  

This query works 
(get-counter -Counter "\ReFS(D:)\*").CounterSamples | SELECT -Property Path, CookedValue

This is the output 
{{{
Path                                                                         CookedValue
----                                                                         -----------
\\ServerName\refs(d:)\delete queue entries                                              0
\\ServerName\refs(d:)\dirty table list entries                                          1
\\ServerName\refs(d:)\dirty metadata pages                                            496
\\ServerName\refs(d:)\container move failure count                                      0
\\ServerName\refs(d:)\compaction failure count                                          0
\\ServerName\refs(d:)\container moves failed due to ineligible container                0
\\ServerName\refs(d:)\container move retry count                                        0
\\ServerName\refs(d:)\compactions failed due to max fragmentation                       0
\\ServerName\refs(d:)\compactions failed due to ineligible container                    0
\\ServerName\refs(d:)\compacted container fill ratio (%)                                0
\\ServerName\refs(d:)\compaction write latency (100 ns)                                 0
\\ServerName\refs(d:)\compaction read latency (100 ns)                                  0
\\ServerName\refs(d:)\data compactions/sec                                              0
\\ServerName\refs(d:)\trim latency (100 ns)                                             0
\\ServerName\refs(d:)\log fill percentage                                               0
\\ServerName\refs(d:)\current fast tier metadata fill percentage                        0
\\ServerName\refs(d:)\current slow tier metadata fill percentage                        0
\\ServerName\refs(d:)\log writes/sec                                     12.9090557025754
\\ServerName\refs(d:)\checkpoints/sec                                                   0
\\ServerName\refs(d:)\tree updates/sec                                                  0
\\ServerName\refs(d:)\checkpoint latency (100 ns)                                       0
\\ServerName\refs(d:)\tree update latency (100 ns)                                      0
\\ServerName\refs(d:)\fast tier destaged container fill ratio (%)                       0
\\ServerName\refs(d:)\slow tier destaged container fill ratio (%)                       0
\\ServerName\refs(d:)\fast tier destage write latency (100 ns)                          0
\\ServerName\refs(d:)\fast tier destage read latency (100 ns)                           0
\\ServerName\refs(d:)\slow tier destage write latency (100 ns)                          0
\\ServerName\refs(d:)\slow tier destage read latency (100 ns)                           0
\\ServerName\refs(d:)\current fast tier data fill percentage                            0
\\ServerName\refs(d:)\current slow tier data fill percentage                            0
\\ServerName\refs(d:)\container destages from fast tier/sec                             0
\\ServerName\refs(d:)\container destages from slow tier/sec                             0
\\ServerName\refs(d:)\allocation of data clusters on slow tier/sec                      0
\\ServerName\refs(d:)\allocation of data clusters on fast tier/sec       43882.8453544777
\\ServerName\refs(d:)\allocation of metadata clusters on slow tier/sec                  0
\\ServerName\refs(d:)\allocation of metadata clusters on fast tier/sec   1.98600856962698
\\ServerName\refs(d:)\data in place write clusters/sec                                  0
\\ServerName\refs(d:)\total allocation of clusters/sec                   43884.8313630473

Any help would be appreciated. TIA

multichannel powershell prtg wmi

Created on Feb 2, 2019 8:05:27 AM

Last change on Feb 4, 2019 5:40:24 AM by Sven Roggenhofer [Paessler Technical Support]

Permalink

1 Reply

Votes:

0

Hi there,

Please note that PRTG requires a certain format to read channel names, values, limits and so on. You can find an explanation within your PRTG webinterface under "Setup > PRTG API > Custom Sensors".

Please also check the following site for additional information about PowerShell based Custom Sensors:
https://kb.paessler.com/en/topic/71356-guide-for-powershell-based-custom-sensors

Best regards.

Add comment

Created on Feb 4, 2019 11:17:29 AM by Dariusz Gorka [Paessler Support]

Permalink

Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.

What is this?

Top Tags

Multiple Channels from WMI

0

0