SQL Server Data source for Custom Database Extension

[tvannamuthu]

Trying to migrate queries from Custom DB queries to Custom Database Extension. Created an extension for a query.

During execution, the extension provides the following warning - Connection exists but no metrics have been produced for endpoints: But I know data is available at the endpoint as the same query when run separately provides the desired output. What might be causing this error? Appreciate any insights.

[Miguel_RinconG]

Hi @tvannamuthu ,

Please shared your extension code. This is a query example:

  - group: User
    featureSet: User
    interval:
      minutes: 5
    query: >
      SELECT count(CustomerID) as UserCount,
      Region
      FROM Customers    
      where Region is not Null
      Group by Region
    dimensions:
      - key: custom.customquery.region
        value: col:Region
    metrics:
      - key: custom.customquery.sql.user
        value: col:UserCount

[tvannamuthu · Accepted solution]

Hello Miguel_RinconG,

I was able to fix the issue by adding the database name in the monitoring configuration. It was mentioned as optional so did not add that initially but after adding the Database name extension started to fetch metrics.

Thanks for your reply.

[ashafingilutfi]

Hi @tvannamuthu,

How you add database name ? it is using connection string ? because the prompt is showing only service name/SID

[tvannamuthu]

Hi @ashafingilutfi ,

Please see the screen shot below. Here is where database name was added.

When you try to add monitoring configuration from an SQL Server extension you get this view.

Hope this helps.

[chaitanya]

Hi there,
I have added DB name correctly and syntax also correct but sometime queries throw same error as above.
do we have any other solutions?

thanks

[moin_DT1]

Hi All,

We are having the same error, even though we have added Database name and other fields correctly.

Does anyone have update? @tvannamuthu @chaitanya @ashafingilutfi @Miguel_RinconG 

Thanks in advance,

Moin

[PDivya]

Hi All, 

We are also having same error, provided DB name and all details, as with the same details it is working extension 1.0.

Does anyone have update?

Thanks

Divya