Error while adding monitoring configuration for SQL Data source extension

[susmita_k]

After deploying the SQL Data source extension successfully, we are trying to add monitoring configuration. and we see below error :

Failed to assign monitoring configuration to ActiveGate. Reason: Error in YAML or JSON configuration.

We are not able to see any further details/logs or events. Any help is really appreciated.

[mmevanson]

I would love to know how to fix this.  Anyone know yet?

[JamesKitson]

For something like this the specific extension YAML would need to be reviewed. All that can be told from that error is that something is wrong. There are some scenarios that aren't detected on the initial validation step but are when the data source actually tries to run it.

If you aren't using it, I suggest using the VS Code Add On for developing extensions which in addition to validating the schema for you will also help to identify some of these cases that only surface at this stage sooner.

[GerardJ]

I got this message with a SQL Data Source extension for log ingest. I'm using the VS Code add-on and can't find the cause of this error. 
Is there a log (activatable debug log ?) on the ActiveGate that could give more details about the "something is wrong" ?

[susmita_k]

You can run the diagnostic log for the active gate group which you configured for the monitoring configuration. That log normally provides more information about the error. 

[erh_inetum]

Hi @susmita_k and @mmevanson ,

Have you assign a group to Active Gate? Dynatrace uses a group to instruct the extension where it should run. And I would create a new group instead of using default group. 

I would also check that there isn´t any connectivity issues with Active Gate.

Hope it helps.

Regards,

Elena.

[brett_schubach1]

Hi @susmita_k and @mmevanson 

We have found that the Custom Extension Creator App adds a type count/gauge to the YAML.

When we used the  VS Code Add On for developing extensions as per @JamesKitson  and removed the type from each metric it worked and ran perfectly. We did this when we created it in the Creator and then loaded it up into Managed so not sure if it is doing it on SaaS as well. 

Regards,

Brett

[Peter_Youssef]

Hello @susmita_k 

Kindly validate the current setup against the provided documentations:

• https://docs.dynatrace.com/docs/shortlink/microsoft-sql-monitoring
• https://docs.dynatrace.com/docs/extend-dynatrace/extensions20/data-sources/sql/sql-reference#sql-dat...

Review the practical use case for validation:

• A Practical Guide to SQL Extensions with Dynatrace

KR,

Peter.

[Peter_Youssef]

Hi @susmita_k 

You can also verify if the extension is located properly in the target AG directories:

• https://docs.dynatrace.com/docs/shortlink/sgw-files

KR,

Peter.