I have the following connectivity options in my Azure Data Studio setup:
How can I connect may Azure Data Studio to an Application Insight instance?
In Azure Portal, Create a Log Analytics workspace.
Copy the workspace ID which is useful for later to connect Azure DataStudio.
Create Application Insights
Select the Resource Mode as Workspace-based.
In Log Analytics Workspace, select the Workspace which we have created in the first step. Click on Review + create.
Open the Azure Data Studio => New Connection.
Provide the Workspace ID which we have copied from Portal => Log Analytics Workspace.
In Account => Add Account => Login with your Azure Subscription ID.
Click on Connect.
You can see the Azure Data Studio is now connected to our provided Log Analytics Workspace.
Now you can query the logs by using the New query option.
References taken from MSDoc.
Related
I am attempting to setup Synapse to access a Cosmos Db that has firewall rules set to only allow whitelisted IPs.
After a bit of research, I came across this article:
Securing Azure Synapse Workspaces? Beware of One Inescapable Networking Blocker | by Moussa Taifi PhD | Towards Dev
According to that post, the only option is to whitelist the entire range of IPs that might be used by the pool. Can someone let me know if this is indeed the case? I started looking at private endpoints as that seems like a perfect solution, but I can't get it to work. I tried the following multiple times:
Create new CosmosDb with Azure Synapse Link enabled
Restrict to Selected networks
Create a new DB and Container
Verify that I can’t add a new item
Add my IP
Add new item
Create a new Synapse Workspace, choosing Managed VNet
After creation, verify that the Integration Runtime is in the Managed VNet.
Create two new private endpoints for my Cosmos db. One for type Sql, and one for Analytical (I’m not sure which I need yet)
Go to the Private Link center and approve both end points
Data > Connect to External Data
Ensure that my runtime is in the Manage VNet
Select my DB
I waited 10 min, but the managed endpoint list is stuck at “Refreshing.” I continued to save anyway, but when I try to make a SQL call (after creating the credential), I get:
Resolving CosmosDB path has failed with error 'Access to the database account '*******' is forbidden.'.
The endpoints are permanently "Refreshing" in both the properties of the connection and also in the Manage Private Endpoints. The end point links are "approved" and show as such in Cosmos DB.
Can anyone let me know:
Are Private endpoints a method that I can use to connect my Synapse Workspace to my locked down Cosmos DB?
If so, what might I be doing wrong?
Thanks!
You should consider opening a support case in the case of misconfiguration in your settings.
There should be an option to allow access to Azure IPs. This is contained in documentation located here:
Add a managed private endpoint for Azure Cosmos DB analytical store
Sign into the Azure portal.
From the Azure portal, navigate to your Synapse Analytics workspace and open the Overview pane.
Launch Synapse Studio by navigating to Getting Started pane and select Open under Open Synapse Studio.
In the Synapse Studio, open the Manage tab.
Navigate to Managed private endpoints and select New
Create a new private endpoint for analytical store.
Select Azure Cosmos DB(SQL API) account type > Continue.
Select Azure Cosmos DB SQL API to create a private endpoint.
Fill out the New managed private endpoint form with the following details:
Name - Name for your managed private endpoint. This name cannot be updated after it's created.
Description - Provide a friendly description to identify your private endpoint.
Azure subscription - Select an Azure Cosmos DB account from the list of available accounts in your Azure subscriptions.
Azure Cosmos DB account name - Select an existing Azure Cosmos DB account of type SQL or MongoDB.
Target sub-resouce - Select one of the following options: Analytical: If you want to add the private endpoint for Azure Cosmos DB analytical store. Sql (or MongoDB): If you want to add OLTP or transactional account endpoint.
Note
You can add both transactional store and analytical store private endpoints to the same Azure Cosmos DB account in an Azure Synapse Analytics workspace. If you only want to run analytical queries, you may only want to map the analytical private endpoint.
Choose analytical for the target subresource.
After creating, go to the private endpoint name and select Manage approvals in Azure portal.
Navigate to your Azure Cosmos DB account, select the private endpoint, and select Approve.
Navigate back to Synapse Analytics workspace and click Refresh on the Managed private endpoints pane. Verify that private endpoint is in Approved state.
I am unable to endure clicking so many times in Azure Portal to get to AppInsights log analytics. Saving the URL to the analytics blade and returning to it also frequently fails to load the page due to what appear to be some authentication token expiration issues.
How can I run my Kusto queries on my AppInsights instance without using Azure Portal?
We are running a private preview of the ability to use the Azure Data Explorer tools such as Kusto Explorer and Kusto Web explorer to query Log analytics and Application Insights.
If you are interested to join, please send a mail to adxproxy alias (#microsoft.com).
https://learn.microsoft.com/en-us/azure/azure-monitor/app/export-power-bi. Power BI helps to analyze data and share insights. Continuous export is also an option. You can export app-insights data to blob storage and analyze data using stream analytics.
https://learn.microsoft.com/en-us/azure/azure-monitor/app/export-telemetry
I want to use datastore of google in my web app but do not want to host it in google app engine, I want to host it some other machine. So how i can use datastore in such web app ?
will it be more economical ?
You would need to follow the Accessing the Cloud Datastore API from another platform procedure:
This section shows how to activate and access the Cloud Datastore API
from an external application running on a platform outside of Google
Cloud.
Enable the Cloud Datastore API for the project. You can enable the API for an existing project, or create a new project and then enable
the API.
Enable the Cloud Datastore API
To use the Cloud Datastore API, your Cloud project requires an active App Engine application. Open the App Engine dashboard and
confirm your Cloud project has an active App Engine app.
Open the App Engine dashboard
Create an App Engine app if needed. The app must not be disabled.
Go to the Create service account key page.
Click the drop-down box below Service account, then click New service account.
Enter a name for the service account in Name.
Use the default Service account ID or generate a different one.
Select JSON in Key type.
Click Create.
Upon successful creation, your browser will download the private key. The Cloud Platform Console provides a prompt that displays the
private key file name. Note the file name so you can locate it, then
click Close to dismiss the prompt.
Your Service Account is the Email address displayed under the Service Account section.
Your Private Key is the file you just downloaded.
At this point all services and authorizations are configured for your
project and you can start writing code or exploring the API.
You don't actually need to write code for the GAE app and deploy it, see Is an App Engine instance required for accessing Datastore?
As for being more economical or not (I presume compared to running the app on GAE) - it depends a lot on the app's usage/scale, what the app does and how it does it.
Have a look at Cloud Endpoints
https://cloud.google.com/appengine/docs/java/endpoints/
I have created a subscription with Azure Germany, and now I am attempting to deploy my application topology there using the Azure Management API and a service principal.
Deployment works fine towards the "regular" Azure cloud, however when I attempt to deploy towards my subscription in Azure Germany, I get the following error message: The subscription '[...]' could not be found.
I am able to successfully acquire an authentication token using AuthenticationContext.AcquireTokenAsync(), and I am using "https://login.microsoftonline.de/[directoryId]" as authority and "https://management.core.cloudapi.de/" as resource. Additionally, I am using "Germany Northeast" as location/region.
The error occurs as soon as I attempt to perform a typical management task, such as creating a resource group.
I have checked the following things:
App registration settings
App permissions (Windows Azure Active
Directory + Windows Azure Service Management API)
Correctness of
subscription id, app id, and app secret/key
I am at a loss at what could be wrong. What could be causing this error message?
you should point your app to correct subscription first.
Try setting subscription using this link.
Add Microsoft Graph permissions to your Azure AD app.
I have signed up for the trial version of oracle cloud data base.
Where can I find the host URL that I need to use in my Java dynamic web project of eclipse?
Thanks in advance.
Basic knowledge about the trial request and details needed :
After you request a trial service from Oracle Cloud, you'll be provided with a few details: Identity Domain, Temporary password, and your username.
By using them you'll login to your trial cloud account from here:
[https://cloud.oracle.com/sign_in][1]
Accessing the service from Eclipse
When it comes to access your Database Cloud Service from Eclipse:
You need to add the Oracle Cloud plugin from the Eclipse Market (Help Menu->Eclipse Marketplace)
You'll add the Oracle Cloud connection window to the interface (Window Menu->Show View->Other)
Create a new connection where you follow the steps with the proper details you have about your account.