You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to get MS Exchange Server 2016 Queues monitoring, i have installed windows_exporter on my exchange server using config.yaml. Using OS Windows Server 2019 and Exchange Server 2016.
but i am unable to get TransportQueues metrics at “localhost:9182/metrics”.
I am getting following metrics here
windows_exchange_http_proxy
windows_exchange_ldap
windows_exchange_workload
and some windows_iis_current_application_pool_state{app="MSExchangeAutodiscoverAppPool",state="Delete Pending"} 0
i have added MSExchangeTransport Queues in Windows Performance Monitor Counter.
I have followed a blog post [https://bidhankhatri.com.np/monitoring/windows-machine-monitoring/] but to no avail.
Thanks in advance.
Environment
windows_exporter Version: v0.30.4
Windows Server Version: Windows Server 2019
The text was updated successfully, but these errors were encountered:
Problem Statement
I am trying to get MS Exchange Server 2016 Queues monitoring, i have installed windows_exporter on my exchange server using config.yaml. Using OS Windows Server 2019 and Exchange Server 2016.
example configuration file for windows_exporter
collectors:
enabled: cpu,cpu_info,exchange,iis,logical_disk,logon,memory,net,os,performancecounter,process,remote_fx,service,system,tcp,time,terminal_services,textfile
collector:
service:
include: "windows_exporter"
log:
level: warn
but i am unable to get TransportQueues metrics at “localhost:9182/metrics”.
I am getting following metrics here
windows_exchange_http_proxy
windows_exchange_ldap
windows_exchange_workload
and some windows_iis_current_application_pool_state{app="MSExchangeAutodiscoverAppPool",state="Delete Pending"} 0
i have added MSExchangeTransport Queues in Windows Performance Monitor Counter.
I have followed a blog post [https://bidhankhatri.com.np/monitoring/windows-machine-monitoring/] but to no avail.
Thanks in advance.
Environment
The text was updated successfully, but these errors were encountered: