We have setup WSO2 API-M v2.1.0 with API-M Analytics v2.1.0 with Postgresql and HAProxy on CentOS. The API analytics reports are being shown as expected from the Publisher and the Store side and even the api availability from the Admin Portal.
This is a distributed set-up comprising separate publisher, store, key manager, traffic manager, gateway manager/worker and analytics. Consul service discovery is providing local DNS resolution.
On the gateway worker we have enabled log analyzer; also HAProxy is forwarding /portal and /shindig to the Admin Portal publisher node.
Also note the publisher was started on its api-publisher product profile, however this resulted in missing alert configurations, see
jira issue.
This is easily resolved by reverting to the default profile; still none of the log analyzer links are being populated when logged into the Admin Portal application.
When attempting any of the Log analyzer links from the Admin Portal the browsers javascript console is displaying the following errors :
"Failed to preload gadget https://<HOSTNAME>/portal/store/carbon.super/fs/gadget/LiveLogViewer/index.xml."
and
"Detailed error: 503 Unable to retrieve spec for https://<HOSTNAME>/portal/store/carbon.super/fs/gadget/LiveLogViewer/index.xml. HTTP error 503"
From the analytics carbon console I can validate my gateway log analzyer configuration from the data explorer seen here
The docs seem to suggest the need to edit js code for the log analyzer??
Related
I am trying to implement WSO2 API manager with the Analytics solution in K8s (local machine- Docker K8s)
I am using the APIM 3.2.0 image the same version image for analytics
Both the API manager and the analytics solution is getting deployed and I could access the analytics dashboard, publisher and devportal. I can create and call APIs from publisher and devportal. However, the analytics solution doesn't hold any of my API data.
I have deployed the Worker, then the API manager, and then the dashboard in the same order as suggested here
After the analytics server is started
I cannot see the below message in the Analytics worker
INFO {org.wso2.carbon.databridge.core.DataBridge} - user admin connected
I have enabled the apim.analytics in my deployment.toml file (as a config map).
[apim.analytics]
enable = true
store_api_url = "https://localhost:7444"
Please throw some insights on the missing part
I am not able to see following statictics like
API USAGE OF APPLICATION
TOP APPLICATION USERS
FAULTY INVOCATIONS PER APPLICATION in Dashboard for APIM Developer statistics.
Only details of "REGISTERED APPLICATION USERS" are shown.
I am using the default H2 database and done "quick setup" of analytics dashboard.
I am using 3.1.0 version for both WSO2 API-M and WSO2 Analytics Dashboard and also enabled the analytics in delployment file in APIM.
check below pointers
is your analytics and APIM 3.1 is under the same folder
start components in order analytics worker -> wso2 APIM -> dashboard
check that in APIM deployment.toml files analytics is enabled
login with the same user in APIM and dashboard
Using WSO2 Api-M On-Prem v3.1.0.
I have set up an API in Publisher with different endpoints for Production and Sandbox.
Using API Key as Application Level Security.
Enabled Security for my GET resource.
In DevPortal I created an Application and set up an subscription for my API.
Generated Sandbox API Key and used "Try Out" in DevPortal.
I can select Key Type "Production" and enter my Sandbox Key, I get OK response from Production endpoint.
Try-Out screenshot
If I change Key Type to Sandbox, I still get response from Production endpoint.
I see in http_access_.YYYY-MM-DD log that both requests are sent to my production endpoint.
Why isn't my request sent to Sandbox when I use Sandbox API-Key as described in documentation:
https://apim.docs.wso2.com/en/3.0.0/learn/api-gateway/maintaining-separate-production-and-sandbox-gateways/
I reproduced this issue in API Manager version 3.1.0. This is a bug and needs to be fixed. I have created a GitHub issue for this. Please check [1].
As a workaround for your scenario, please enable OAuth2 Application level security as well under the Runtime Configurations of your API in Publisher. So both OAuth2 and API Key needs to be selected.
[1] https://github.com/wso2/product-apim/issues/8483
All of my calls to the following Google APIs have started failing:
Provisioning
Profiles
Reporting
Reporting Visualization
Admin Audit
Email Migration (v1)
Documents List
Has something changed?
All the API listed were shut down as of April 20, 2015 as per the deprecation policies of the Admin SDK and Documents List API.
Please see the following migration guides for more information on how to migrate:
Provisioning API to Admin SDK Directory API
Profiles API to Admin SDK Directory API
Reporting API to Admin SDK Reports API
Admin Audit API to Admin SDK Reports API
Email Migration API (v1) to Gmail API
Documents List API to Drive API
If the shutdown has impacted a business critical application, please contact Google for Work Support.
All of my calls to the following Google APIs have started failing:
Provisioning
Profiles
Reporting
Reporting Visualization
Admin Audit
Email Migration (v1)
Documents List
Has something changed?
All the API listed were shut down as of April 20, 2015 as per the deprecation policies of the Admin SDK and Documents List API.
Please see the following migration guides for more information on how to migrate:
Provisioning API to Admin SDK Directory API
Profiles API to Admin SDK Directory API
Reporting API to Admin SDK Reports API
Admin Audit API to Admin SDK Reports API
Email Migration API (v1) to Gmail API
Documents List API to Drive API
If the shutdown has impacted a business critical application, please contact Google for Work Support.