I have registered in Pivotal Web Services and do not see the Kafka service there. Is it available for a free trial plan ? How to use Kafka message broker with Pivotal Web Services?
At the time of me writing this, there is no Kafka service in the Pivotal Web Services marketplace. You can see the list of services that are publicly available here.
https://docs.run.pivotal.io/marketplace/services/
If you want to use Kafka with your apps, you'd need to bring your own service or use a third party service provider that's outside of the marketplace.
https://community.pivotal.io/s/article/Am-I-restricted-to-using-service-providers-that-are-in-the-Marketplace
Related
We currently deployed our Spring Boot Application in GKE(Google Kubernetes Engine) and we are currently using cloud endpoint to secure our web services. We have 11 web service developed which will be consumed by external clients. Is there any way i check the SLO (times, performance) of a webservice in cloud endpoint or in stackdriver.
You might want to check:
Spring sleuth
Jaeger operator
Jaeger is a opentracing standard and can help understand the values, and sleuth is a tool to integrate with spring, there are several options, you might want also to consider opencensus
First you need to expose metrics from your applications. Spring Sleuth is a great choice if you're using Spring Boot.
Then you need to collect the metrics and visualize them. Google provides a tool for that called Stackdriver Trace. It can also do metric-based alerts. You can find a sample setup for your use case here.
There are other performance monitoring services such as Dynatrace or Datadog.
If you want a self-hosted solution, you can use Zipkin which is inspired by an internal Google system called Dapper.
Have you looked at Google cloud console UI? Its "Endpoints" tag should show all services your project is running.
I want to call Spring cloud eureka application from TIBCO BE and BW for registering the tibco applications in Eureka service registry.
If you're running TIBCO BusinessWorks Container Edition, you can easily connect to Spring Cloud services by setting a few environment variables. The documentation on the TIBCO Docs website will explain which variables you need to set, depending on where you're running your apps (either CloudFoundry or Docker based). Specifically for CloudFoundry based environments, there are samples that will help guide you through deploying apps.
For the HTTP Connector you can refer to this doc page on how and what to set.
IBM Provide APM as SaaS service to monitor the application performance end to end with insights to code and transaction. It require its collection agent to be installed in various application component to collect the metrics. I can see one o the application template supported in the IBM Cloud (Bluemix) application. I like to use the same to monitor my IBM Cloud native application. Application being in cloud, I am assuming that all the collection agents are automatically installed or I can configure them somehow. Once that is done, APM should help me connect to these application and start monitoring them. While This is my understanding, I do not see any document/article which can provide me the steps to configure the IBM Cloud application for APM integration and connection. Can anyone has experience in monitoring such a application ? Can anyone share article to steps to achieve the same ?
Thanks
Manoj
Seems like the details of monitoring Liberty-based applications are described pretty well in the APM manual:
Configuring WebSphere® Applications monitoring involves configuring a
data collector for your application servers. The data collector can be
either stand-alone or embedded with the WebSphere Applications agent.
https://www.ibm.com/support/knowledgecenter/en/SSMKFH/com.ibm.apmaas.doc/install/was_config_dc_all.htm
Configuring the data collector for WebSphere Applications agent The
WebSphere Applications agent does not need any configuration after
agent installation, unless you want to change the default port.
However, you must configure the data collector, which is a component
of the agent, to set up monitoring for your WebSphere environment.
Configuring the Liberty data collector for on-premises applications To
monitor the Liberty profile on Linux for System x, you can directly
deploy a stand-alone data collector to your local Liberty directory
without installing WebSphere Applications agent.
Configuring the Liberty data collector for IBM Cloud applications To
monitor a Liberty profile running in the IBM Cloud environment, you
must download the data collector package from IBM Marketplace, deploy
the data collector to your local application files, and then push the
updates to IBM Cloud.
I'm wondering if an external app could 'talk' to Bluemix app using IBM MQ?
Thanks in advance!
A slight clarification on MQ Light in the previous answer.
An MQ Light application in Bluemix can communicate with IBM MQ in your datacenter (via the SecureGateway), but if you are running an instance of the MQ LIght service in Bluemix, the service itself cannot be connected to IBM MQ.
Bluemix currently offers the MQ Light service which can be used for messaging to IBM MQ (formerly WebSphere MQ)
MessageHub also allows you to use the MQ Light APIs via Bluemix to do messaging.
Using Mule ESB I noticed that you can connect (via anypoint connectors) applications, databases, web services etc.
Since I am making a comparison between different ESB (Enterprise Service Bus) I ran into WSO2 ESB and reading the documentation it seems that allows to interact only web services (through SOAP communications).
Someone confirms what I wrote? Or WSO2 ESB is flexible as Mule ESB and I'm wrong (if so what are the differences)?
WSO2 ESB also has the concept of connectors which you can use to connect to external applications, databases, file systems and web services hosted in cloud or in internal networks. Here is a webinar which you can follow to get more information.
http://wso2.com/library/webinars/2014/09/esb-connectors-for-on-premise-and-cloud-integration-solutions/
I can't help as my knowledge of WSO2 is limited. What I could do is to recommend you the book open source ESB in action, although outdated its data, the introduction is amazing and the comparison methodology is also good. You could follow the same approach with the state of the art today.
Most of the connectivity to applications, databases, different protocols are already available with wso2 ESB and wso2 product stack out of the box. However there are some connectors that will support integration with on-premises legacy systems and additional protocols. eg: ejb, is08583, kafka, etc.