SOLVED

Enable 'sql_request' plugin in Log Analytics

%3CLINGO-SUB%20id%3D%22lingo-sub-179400%22%20slang%3D%22en-US%22%3EEnable%20'sql_request'%20plugin%20in%20Log%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-179400%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20trying%20to%20use%20the%20'evaluate%20sql_request'%20command%20within%20Log%20Analytics%2C%20but%20I%20get%20a%20message%20returned%20saying%20%22%3CSPAN%3EPlugin%20'sql_request'%20is%20disabled%22.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3ECan%20anyone%20help%20me%20identify%20where%20I%20go%20to%20enable%20plugins%20for%20Log%20Analytics%3F%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%3CBR%20%2F%3EThanks.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-179400%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EQuery%20Language%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-180746%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20'sql_request'%20plugin%20in%20Log%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-180746%22%20slang%3D%22en-US%22%3E%3CP%3EAh%2C%20thank%20you%20for%20the%20response!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-180471%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20'sql_request'%20plugin%20in%20Log%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-180471%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Brandon%2C%3CBR%20%2F%3EThis%20plugin%20is%20disabled%20intentionally%20as%20a%20precaution%2C%20as%20a%20safe%20guard%20and%20to%20prevent%20misuse%20on%20public%20services%20as%20Log%20Analytics.%20We%20will%20remove%20the%20relevant%20article%20from%20our%20docs.%3CBR%20%2F%3EWe%20examine%20this%20decision%20from%20time%20to%20time%2C%20you%20can%20track%20coming%20changes%20through%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.loganalytics.io%2Fdocs%2FLanguage-Reference%2FChange-log%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Echange%20log%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%2C%3C%2FP%3E%0A%3CP%3ENoa%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1205349%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20'sql_request'%20plugin%20in%20Log%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1205349%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F54923%22%20target%3D%22_blank%22%3E%40Noa%20Kuperberg%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20getting%20this%20same%20error%20at%20the%20moment%20when%20I%20try%20to%20run%20a%20sql%20request%20from%20within%20Azure%20Logs.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%3EPlugin%20'sql_request'%20is%20disabled%3CBR%20%2F%3EIf%20issue%20persists%2C%20please%20open%20a%20support%20ticket.%3CBR%20%2F%3ERequest%20id%3A%2081b3f20d-c1a6-496a-9106-5a1c3c67f4b5%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThese%20queries%20worked%20up%20until%20last%20week.%3CBR%20%2F%3EPlease%20advise%20ASAP%20as%20we%20are%20on%20a%20tight%20deadline%20for%20these%20analytics.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EMany%20thanks%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1209073%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20'sql_request'%20plugin%20in%20Log%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1209073%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F572703%22%20target%3D%22_blank%22%3E%40AnnieMcC%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%0A%3CP%3EThis%20plugin%20should've%20been%20blocked%20on%20Log%20Analytics%20from%20the%20get%20go%2C%20but%20we%20recently%20found%20that%20specific%20LA%20clusters%20allowed%20it%2C%20by%20mistake.%20I%20found%20now%20that%20these%20cluster%20have%20been%20fixed%20to%20block%20it.%3C%2FP%3E%0A%3CP%3Eonly%20ADX%20should%20allow%20running%20it...%3C%2FP%3E%0A%3CP%3EI%20do%20apoligize%20you've%20taken%20a%20dependency%20on%20this%20plugin%2C%20Log%20Analytics%20will%20not%20be%20supporting%20it%20in%20the%20near%20future.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1210365%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20'sql_request'%20plugin%20in%20Log%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1210365%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F54923%22%20target%3D%22_blank%22%3E%40Noa%20Kuperberg%3C%2FA%3E%26nbsp%3Bthanks%20for%20your%20quick%20reply.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYes%2C%20that's%20a%20bit%20of%20a%20pain%20as%20I%20have%20written%20some%20analytics%20reports%20that%20use%20our%20Azure%20SQL%20DB%20tables%20as%20%22lookups%22.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3ECan%20you%20point%20me%20towards%20some%20documentation%20on%20how%20to%20now%20achieve%20this%3F%3C%2FP%3E%3CP%3EMy%20end%20goal%20is%20a%20Power%20BI%20report%20where%20the%202%20data%20sources%20will%20be%20combined%20-%20Log%20Analytics%20%26amp%3B%20the%20SQL%20DB%20data.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethanks%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1210794%22%20slang%3D%22en-US%22%3ERe%3A%20Enable%20'sql_request'%20plugin%20in%20Log%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1210794%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F572703%22%20target%3D%22_blank%22%3E%40AnnieMcC%3C%2FA%3E%26nbsp%3B%20there%20is%20no%20exact%20replacement%20for%20this%20plugin%2C%20and%20the%20limitation%20is%20basically%20on%20connecting%20to%20external%20data%20sources%20that%20could%20be%20abused.%3C%2FP%3E%0A%3CP%3ESo%3A%3C%2FP%3E%0A%3CP%3E1.%20If%20the%20content%20is%20static%20and%20short%2C%20you%20can%20use%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fkusto%2Fquery%2Fdatatableoperator%3Fpivots%3Dazuremonitor%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Edatatable%20operator%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E2.%20If%20the%20content%20is%20static%20but%20longer%2C%20export%20from%20SQL%20to%20a%20file%2C%20and%20ingest%20to%20Log%20Analytics%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Fazure-monitor%2Fplatform%2Fdata-sources-custom-logs%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Eas%20a%20custom%20log%3C%2FA%3E.%20Then%20you%20can%20reference%20it%20in%20your%20query.%3C%2FP%3E%0A%3CP%3E3.%20Probably%20best%20option%20-%20query%20both%20LA%20in%20SQL%20through%20PowerBI%2C%20which%20you%20plan%20to%20use%20anyway.%20To%20do%20that%2C%20create%20the%20query%20you%20want%20for%20only%20your%20LA%20data%20in%20the%20Azure%20portal%2C%20and%20then%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fazure%2Fazure-monitor%2Fplatform%2Fpowerbi%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Echoose%20to%20Export%20to%20Power%20BI%3C%2FA%3E.%20This%20is%20really%20easy%2C%20and%20converts%20your%20query%20to%20the%20Power%20BI%20M%20language%2C%20so%20you%20can%20run%20it%20over%20there%2C%20and%20cross-query%20SQL%20in%20Power%20BI%20itself.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHTH%3C%2FP%3E%3C%2FLINGO-BODY%3E
Deleted
Not applicable

I am trying to use the 'evaluate sql_request' command within Log Analytics, but I get a message returned saying "Plugin 'sql_request' is disabled".

 

Can anyone help me identify where I go to enable plugins for Log Analytics?


Thanks.

6 Replies
Best Response
Solution

Hi Brandon,
This plugin is disabled intentionally as a precaution, as a safe guard and to prevent misuse on public services as Log Analytics. We will remove the relevant article from our docs.
We examine this decision from time to time, you can track coming changes through the change log.

 

Thanks,

Noa

Ah, thank you for the response!

Hi @Noa Kuperberg,

 

I'm getting this same error at the moment when I try to run a sql request from within Azure Logs.

Plugin 'sql_request' is disabled
If issue persists, please open a support ticket.
Request id: 81b3f20d-c1a6-496a-9106-5a1c3c67f4b5

 

These queries worked up until last week.
Please advise ASAP as we are on a tight deadline for these analytics.

 

Many thanks

Hi @AnnieMcC ,

This plugin should've been blocked on Log Analytics from the get go, but we recently found that specific LA clusters allowed it, by mistake. I found now that these cluster have been fixed to block it.

only ADX should allow running it...

I do apoligize you've taken a dependency on this plugin, Log Analytics will not be supporting it in the near future. 

@Noa Kuperberg thanks for your quick reply.

 

Yes, that's a bit of a pain as I have written some analytics reports that use our Azure SQL DB tables as "lookups".

Can you point me towards some documentation on how to now achieve this?

My end goal is a Power BI report where the 2 data sources will be combined - Log Analytics & the SQL DB data.

 

thanks 

@AnnieMcC  there is no exact replacement for this plugin, and the limitation is basically on connecting to external data sources that could be abused.

So:

1. If the content is static and short, you can use the datatable operator.

2. If the content is static but longer, export from SQL to a file, and ingest to Log Analytics as a custom log. Then you can reference it in your query.

3. Probably best option - query both LA in SQL through PowerBI, which you plan to use anyway. To do that, create the query you want for only your LA data in the Azure portal, and then choose to Export to Power BI. This is really easy, and converts your query to the Power BI M language, so you can run it over there, and cross-query SQL in Power BI itself.

 

HTH