opentelemetry-collector-contrib: sqlserverreceiver@v0.71.0 failed to create perf counter with path \SQLServer:: The specified object was not found on the computer.

Component(s)

receiver/sqlserver

Describe the issue you’re reporting

Hi,

When I configure Open Telemetry Contrib to use the receiver for SQL Server on one of our database servers, during start a couple of warnings is shown (21 to be precise).

This is the general message: warn sqlserverreceiver@v0.71.0/scraper.go:66 failed to create perf counter with path \SQLServer:<CounterName>: The specified object was not found on the computer. The message is given 21 times, for different counters, see bottom of this post for all messages.

Although the otel-contrib agent continues running, it does not gather any SQL Server metrics.

Interestingly enough, all works fine on my laptop, but not on the server.

Main differences:

  • Laptop runs SQL Server version 19, Server runs outdated SQL Server 2008R2 (we’re stuck with that…😦 )
  • Laptop runs default instance, Server runs named instance (stuck with that as well…)
  • Laptop shows many SQL Server specific counters in Performance Monitor, Server doesn’t show any SQL Server counter in Performance Monitor.

I followed the steps on these pages to try to solve on our server, without any result:

Can anybody help me out?

Many thanks!

Arjan

Full list of warnings:

2023-02-28T17:36:07.269+0100    info    extensions/extensions.go:41     Starting extensions...
2023-02-28T17:36:07.344+0100    warn    sqlserverreceiver@v0.71.0/scraper.go:66 failed to create perf counter with path \SQLServer:General Statistics\User Connections: The specified object was not found on the computer.
        {"kind": "receiver", "name": "sqlserver", "data_type": "metrics"}
2023-02-28T17:36:07.345+0100    warn    sqlserverreceiver@v0.71.0/scraper.go:66 failed to create perf counter with path \SQLServer:SQL Statistics\Batch Requests/sec: The specified object was not found on the computer.
        {"kind": "receiver", "name": "sqlserver", "data_type": "metrics"}
2023-02-28T17:36:07.348+0100    warn    sqlserverreceiver@v0.71.0/scraper.go:66 failed to create perf counter with path \SQLServer:SQL Statistics\SQL Compilations/sec: The specified object was not found on the computer.
        {"kind": "receiver", "name": "sqlserver", "data_type": "metrics"}
2023-02-28T17:36:07.348+0100    warn    sqlserverreceiver@v0.71.0/scraper.go:66 failed to create perf counter with path \SQLServer:SQL Statistics\SQL Re-Compilations/sec: The specified object was not found on the computer.
        {"kind": "receiver", "name": "sqlserver", "data_type": "metrics"}
2023-02-28T17:36:07.349+0100    warn    sqlserverreceiver@v0.71.0/scraper.go:66 failed to create perf counter with path \SQLServer:Locks(_Total)\Lock Waits/sec: The specified object was not found on the computer.
        {"kind": "receiver", "name": "sqlserver", "data_type": "metrics"}
2023-02-28T17:36:07.349+0100    warn    sqlserverreceiver@v0.71.0/scraper.go:66 failed to create perf counter with path \SQLServer:Locks(_Total)\Average Wait Time (ms): The specified object was not found on the computer.
        {"kind": "receiver", "name": "sqlserver", "data_type": "metrics"}
2023-02-28T17:36:07.349+0100    warn    sqlserverreceiver@v0.71.0/scraper.go:66 failed to create perf counter with path \SQLServer:Buffer Manager\Buffer cache hit ratio: The specified object was not found on the computer.
        {"kind": "receiver", "name": "sqlserver", "data_type": "metrics"}
2023-02-28T17:36:07.349+0100    warn    sqlserverreceiver@v0.71.0/scraper.go:66 failed to create perf counter with path \SQLServer:Buffer Manager\Checkpoint pages/sec: The specified object was not found on the computer.
        {"kind": "receiver", "name": "sqlserver", "data_type": "metrics"}
2023-02-28T17:36:07.350+0100    warn    sqlserverreceiver@v0.71.0/scraper.go:66 failed to create perf counter with path \SQLServer:Buffer Manager\Lazy writes/sec: The specified object was not found on the computer.
        {"kind": "receiver", "name": "sqlserver", "data_type": "metrics"}
2023-02-28T17:36:07.350+0100    warn    sqlserverreceiver@v0.71.0/scraper.go:66 failed to create perf counter with path \SQLServer:Buffer Manager\Page life expectancy: The specified object was not found on the computer.
        {"kind": "receiver", "name": "sqlserver", "data_type": "metrics"}
2023-02-28T17:36:07.350+0100    warn    sqlserverreceiver@v0.71.0/scraper.go:66 failed to create perf counter with path \SQLServer:Buffer Manager\Page reads/sec: The specified object was not found on the computer.
        {"kind": "receiver", "name": "sqlserver", "data_type": "metrics"}
2023-02-28T17:36:07.350+0100    warn    sqlserverreceiver@v0.71.0/scraper.go:66 failed to create perf counter with path \SQLServer:Buffer Manager\Page writes/sec: The specified object was not found on the computer.
        {"kind": "receiver", "name": "sqlserver", "data_type": "metrics"}
2023-02-28T17:36:07.350+0100    warn    sqlserverreceiver@v0.71.0/scraper.go:66 failed to create perf counter with path \SQLServer:Access Methods(_Total)\Page Splits/sec: The specified object was not found on the computer.
        {"kind": "receiver", "name": "sqlserver", "data_type": "metrics"}
2023-02-28T17:36:07.351+0100    warn    sqlserverreceiver@v0.71.0/scraper.go:66 failed to create perf counter with path \SQLServer:Databases(*)\Log Bytes Flushed/sec: The specified object was not found on the computer.
        {"kind": "receiver", "name": "sqlserver", "data_type": "metrics"}
2023-02-28T17:36:07.351+0100    warn    sqlserverreceiver@v0.71.0/scraper.go:66 failed to create perf counter with path \SQLServer:Databases(*)\Log Flushes/sec: The specified object was not found on the computer.
        {"kind": "receiver", "name": "sqlserver", "data_type": "metrics"}
2023-02-28T17:36:07.351+0100    warn    sqlserverreceiver@v0.71.0/scraper.go:66 failed to create perf counter with path \SQLServer:Databases(*)\Log Flush Waits/sec: The specified object was not found on the computer.
        {"kind": "receiver", "name": "sqlserver", "data_type": "metrics"}
2023-02-28T17:36:07.351+0100    warn    sqlserverreceiver@v0.71.0/scraper.go:66 failed to create perf counter with path \SQLServer:Databases(*)\Log Growths: The specified object was not found on the computer.
        {"kind": "receiver", "name": "sqlserver", "data_type": "metrics"}
2023-02-28T17:36:07.351+0100    warn    sqlserverreceiver@v0.71.0/scraper.go:66 failed to create perf counter with path \SQLServer:Databases(*)\Log Shrinks: The specified object was not found on the computer.
        {"kind": "receiver", "name": "sqlserver", "data_type": "metrics"}
2023-02-28T17:36:07.352+0100    warn    sqlserverreceiver@v0.71.0/scraper.go:66 failed to create perf counter with path \SQLServer:Databases(*)\Percent Log Used: The specified object was not found on the computer.
        {"kind": "receiver", "name": "sqlserver", "data_type": "metrics"}
2023-02-28T17:36:07.352+0100    warn    sqlserverreceiver@v0.71.0/scraper.go:66 failed to create perf counter with path \SQLServer:Databases(*)\Transactions/sec: The specified object was not found on the computer.
        {"kind": "receiver", "name": "sqlserver", "data_type": "metrics"}
2023-02-28T17:36:07.352+0100    warn    sqlserverreceiver@v0.71.0/scraper.go:66 failed to create perf counter with path \SQLServer:Databases(*)\Write Transactions/sec: The specified object was not found on the computer.
        {"kind": "receiver", "name": "sqlserver", "data_type": "metrics"}
2023-02-28T17:36:07.352+0100    info    service/service.go:157  Everything is ready. Begin running and processing data.

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 16 (7 by maintainers)

Most upvoted comments

@djaglowski , I’m a database specialist and can develop in SQL related languages like T-SQL and pgSQL, but not the “real languages”. I don’t think that’s enough for contributing in this receiver… 😉 Apart from that, I’m part of an Operations team. We prefer to spend time in convincing our developers to move away from these old versions instead of endlessly spending time on keeping this old stuff running … The fact that this receiver doesn’t work for these specific servers, is a perfect additional argument… 😄

I’ll close the ticket, thanks for your help!

@JonathanWamsley Thanks. To be honest, I don’t know how to get it from the main branch into something I can run. I’m a Data-, Database and SQL specialist, not a proper developer. I’ll probably wait for v0.75.0… 😉 (unless I can get a colleague to help me out here)