Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Azure Application Insights & #10646

Closed
shawnz42 opened this issue Aug 20, 2020 · 7 comments
Closed

Support Azure Application Insights & #10646

shawnz42 opened this issue Aug 20, 2020 · 7 comments
Labels
enhancement:request Enhancement request submitted by anyone from the community

Comments

@shawnz42
Copy link

shawnz42 commented Aug 20, 2020

I'm always frustrated when I want to use superset to explore my data in Azure Application Insights. I need to use its api to pull data into postgresql, and use superset connect postgresql, but when data amount get larger, it's very inefficient. I think if superset can directly connect to Azure Application Insights, it has api but use kusto sql, something differ from ansi sql.

Azure Application Insights docs: https://dev.applicationinsights.io/documentation/Overview
kusto sql: https://docs.microsoft.com/azure/data-explorer/kusto/query/
python lib: https://github.com/Azure/azure-kusto-python

I want to write a new connection to visit Azure Application Insights, is any guides or examples?

@shawnz42 shawnz42 added the enhancement:request Enhancement request submitted by anyone from the community label Aug 20, 2020
@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label #enhancement to this issue, with a confidence of 0.64. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@villebro
Copy link
Member

@zheya08 Based on this SQL to Kusto cheat sheet, Kusto (or KQL) is a subset of SQL but with different syntax than SQL. Instead of writing a custom connector that can only be used with Superset, have you considered authoring a Sql Alchemy connector for Kusto? In addition to being able to connect Superset to Azure Application Insights, it could be leveraged by the whole Python ecosystem.

@junlincc
Copy link
Member

🏷sources

@stale
Copy link

stale bot commented Oct 22, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

@stale stale bot added the inactive Inactive for >= 30 days label Oct 22, 2020
@junlincc junlincc removed the sources label Jan 3, 2021
@stale stale bot removed the inactive Inactive for >= 30 days label Jan 3, 2021
@junlincc
Copy link
Member

@villebro did pysuperset take us one step closer to supporting Azure application? or is it relevant?

@villebro
Copy link
Member

villebro commented Apr 7, 2021

It's not directly relevant I'm afraid. What's really needed is a Kusto SQLAlchemy connector.

@xneg
Copy link
Contributor

xneg commented Jan 10, 2022

Hi there! We added Kusto db_engine to Superset.

@apache apache locked and limited conversation to collaborators Feb 2, 2022
@geido geido converted this issue into discussion #18397 Feb 2, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
enhancement:request Enhancement request submitted by anyone from the community
Projects
None yet
Development

No branches or pull requests

4 participants