Grafana application hosted on linux server, when trying to establish a connection from Grafana web application page to log analytics getting below error
successfully queried the Azure Monitor Service. 2.Azure log analytics: Bad Gateway: Cannot connect to Azure Log Analytics REST API
Related
I am facing connection issues with Google Bigquery connector version 1.0.0 newly launched by MuleSoft in Mar 2022.
I've created a service account as well as an OAuth web application in Google Cloud Platform(GCP) and used values from the JSON file generated by GCP.
Test Connection is getting failed but the application deployed successfully and when the flow reaches any BigQuery connector operation, error raised! (Please see attached images)
I failed to connect using "JWT Connection" as well as "Oauth2 Connection".
Can someone guide how to connect to the Google Bigquery connector?
JWT Connection Image
OAuth Connection Image
I am creating a Linked Service to connect to Google Cloud Storage and i am using following JSON file for Service account that has access on the Google Cloud Storage
I am using private_key_id as Access Key ID and private_key value as Secret Access Key and Service URL as https://storage.googleapis.com:
Linked Service is failing with following error:
How to create a Linked Service using this JSON file to connect to Google Cloud Storage?
Does this documentation help? https://learn.microsoft.com/en-us/azure/data-factory/connector-google-cloud-storage?tabs=data-factory#linked-service-properties
I use WSO2 as an identity server to log in / log out of an application. To analyze some data, I want to use Grafana's dashboards.
I want to perform OAuth Authentication on grafana using WSO2.
I want to access Grafana using the WSO2 user credentials which I also use to access my application.
Is it possible?
Grafana uses the standard openid connect approch. So you can easily connect Grafana with OAuth/OpenID connect inbound protocol. You can create a OpenID connect App is WSO2 Identity Server side and get client id and secrets and configure them in Grafana side. So you can login to Grafana using WSo2 Identity Server side.
Refer : https://is.docs.wso2.com/en/latest/learn/configuring-oauth2-openid-connect-single-sign-on/
You can find WSO2 Identity Server openID connect endpoints from the discovery endpoint:
https://is.docs.wso2.com/en/latest/learn/openid-connect-discovery/#openid-connect-discovery
I'm not able to expose a local rest API through API connect on cloud.
API Connect on Cloud : error
I created a Rest API in my laptop using IIS, and I want to expose it through API Connect on IBM Cloud. Since the "Push Rest API" option in IIB Web Admin is not working, I used the swagger.json file to get the API details manually to APIC on Cloud. I followed the following steps:
In IBM Cloud created resources for API Connect and Secure Gateway cloud foundry services
Created a Secure Gateway Destination and have the SG client running in my laptop
Created a simple Rest API using IIB V10 and deployed it to my local Integration Node.
Tried to push the Rest API using the IIB Web admin by giving host as api.us-south.apiconnect.appdomain.cloud and my IBM Cloud account username/pwd, but it failed saying unable to connect:
Unable to connect to IBM API Connect at host 'api.us-south.apiconnect.appdomain.cloud' port '443'
Then I tried to create an API manually using the swagger.json file available in the IIB RestAPI project. I used the option to create new API using "from file or URL" option in the APIC on IBM Cloud.
I gave my laptop IP as the "Host" value in APIC designer
In the "Assembly", I included a "Proxy" policy and updated its Target URL to cap-sg-prd-2.securegateway.appdomain.cloud:17041
When I try to test the above, I get the following error:
<httpMessage>Internal Server Error</httpMessage>
<moreInformation>Backside URL invalid</moreInformation>
Can you please help to resolve it?
You're missing one or both of the following:
1) The "Target URL" must be a valid URL. Looks like you just entered a hostname, so likely you need https://cap-sg-prd-2.securegateway.appdomain.cloud:17041 Doing that and republishing the API should resolve the "Backside URL invalid" error.
Once you do that, you may find that you still can't reach the backend due to either a timeout or connection refused error.
If so:
2) Did you allow access to the secure gateway destination via the client on your local machine? You have to intentionally set an ACL on the client to allow traffic to the host/port on your network.
After creating a new HDInsight Cluster, I am receiving the following error when I provide the authentication information and try to access the HDInsight web portal at https://{Cluster Name}.azurehdinsight.net/
403 - Forbidden: Access is denied.
Have tried recreating clusters, different browsers, clearing browser cache but have not been able to login. Pls suggest.
The interactive console has been discontinued and the team now recommends the usage of Windows Azure PowerShell
http://www.windowsazure.com/en-us/documentation/articles/hdinsight-submit-hadoop-jobs-programmatically/
You mention clearing browser cache, have you also tried clearing cookies as well? I have had this problem after a failed login to the HDInsight portal and needed to clear cookies and cache.
Also if you have an active directory integration and are trying to login with a domain account, try logging in with the cluster user that you created at deployment instead.
Use windows azure management portal instead, https://manage.windowsazure.com.