I read Configuring Analytics Workers as Active-Active in wso2 documentation and it was not clear for me.can anyone explain more clear for me ?(how to connect only one dashboard to 2 or more analytics workers?)
and another question : is it possible to have two dashboards connect to wso2 workers in Configuring Analytics Workers as Active-Active ?
The Analytics dashboard is stored as a sub-profile of the APIM analytics. You can configure a separate Analytics node as the dashboard for both worker nodes. You simply need to connect the dashboard to the required databases. The dashboard will read the statistics (published from the worker nodes) in the Analytics database and display the statistics on the dashboard. You can use the configurations mentioned in [1] to point to the same databases.
As the dashboard is used only to render the data, there is no active-active or active-passive concept. However, based on the High-availability (HA) requirement it can be configured as Active-Active or Active-Passive by defining the loadbalance configuration.
[1] - https://apim.docs.wso2.com/en/3.2.0/learn/analytics/configuring-apim-analytics/#step-42-configure-the-analytics-dashboard
Related
I installed managed Anthos on a GKE cluster. Anthos Service Mesh is working and is displaying my API. Thanks to that Services that are in Monitoring automatically detect my API. This is great as it enables me to easily set SLOs and Error Budget for my API.
However I would like to be able to easily set SLOs for individual endpoints in my api. Services(in Monitoring) detect only my API and not the endpoints within my API(my API is one pod/container + sidecar). I tried to add endpoints to Services in Monitoring but it looks like it is only possible to add Kubernetes Objects there.
Is there a way to use Services in Monitoring with endpoints? Is the only way to do so to break endpoints to separate microservices?
You can monitor your endpoints using Cloud Endpoints with OpenAPI, which allows you to monitor the health of APIs you own by using the logs and metrics Cloud Endpoints maintains for you automatically. When users make requests to your API, Endpoints logs information about the requests and responses and also tracks three of the four golden signals of monitoring: latency, traffic, and errors. These usage and performance metrics help you monitor your API.
The following URL Configuring Cloud Endpoints has the configuration process for Cloud Endpoints. Use this URL Monitoring your API as a reference on the monitoring process for your API, and this last URL for the Cloud Endpoint’s overview.
For multiple external tenants accessing Kafka, is there any issue with providing the same endpoint (ie. set of brokers, ports) to the multiple producers ?
what are the best practices wrt multiple tenants producing data on (Confluent) Kafka topics, Kafka being installed on GCP.
tia!
Here are Google's Best practices for enterprise multi-tenancy
Confluent Cloud is a fully managed Apache Kafka as a Service in the public cloud. Looks like you can register here to download the white paper that contain a guide to Kafka best practices.
As well you may find this presentation interesting.
Apache Kafka is available throw Google Market Place.
Confluent is a Google partner and you can reach out to them here by clicking on the Contact partner button and filling the form.
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
We are evaluating WSO2 Identity Server, and are trying to understand how WSO2 Identity Server scales across multiple nodes.
The document https://docs.wso2.com/display/CLUSTER44x/Clustering+Identity+Server+5.1.0+and+5.2.0 explains steps to follow to enable clustering, however the document links to database setup documentation that is common to the whole WSO2 suite, and not specifically for Identity Server.
I understand from the documentation that all WSO2 Identity Server nodes are required to share a set of clustered LDAP servers (when an LDAP server is in use).
Is each node in a WSO2 Identity Server cluster required to share a set of clustered SQL servers in addition to the above?
Alternatively, is it fine to have each node use a local database in the expectation that WSO2 Identity Server will communicate with other members of the cluster in order to keep all databases in sync?
When clustering wso2 products, you can use a local db for WSO2CarbonDB (This will be used to store instance-specific data) But you have to share registrydb, userdb among all the nodes.
AFAIK wso2 will not do the db syncing if you use separate db for each node.
We are designing wso2 apim 2.0 cluster deployment architecture, from 2.0 clustering, we just found distribution deployment description, so
Is the wso2 apim gateway 2.0 cluster same with 1.10?
Any recommendation for system CPU/MEMORY requirement?
wso2 apim 2.0 has traffic manager, how to cluster it?
For store/publisher, how to cluster them?
When integration with APIM Analytics, do we just need to config gateway workers?
1) There are configuration changes, and also new configs, in gateways. But gateway clustering has not been changed.
2) See Installation Prerequisites and Tuning Performance
3) There is no public document yet. It'll be there soon. Until now, you can cluster it in the same way gateways are clustered.
4) Store and publisher should be in the same cluster.
5) Gateway workers, store and publisher
Update:
About Dep-Sync: In gateway worker-manager setup, we only publish API synapse files to manager node, and then use dep-sync to copy those APIs to gateway workers. You can use anything that can sync artifacts between nodes instead of SVN based dep-sync. (eg. rsync)