For the web application to deliver its traces, it needs to callout to the OpenTelemetry Collector and it tries to do so at localhost port 4318 You will not however find traces from within the frontend application. This will produce metrics and traces that you can inspect in Jager (8080-gitpodURL/jaeger/ui) and Grafana (8080-gitpodURL/grafana).Īnd details for an individual span showing the SQL statement issued against the PostgreSQL database The webstore web application launches in the browser preview (at port 8080) and you can start browsing, shopping and buying. When done initializing, more than a dozen containers are running – for each of the microservices and the front end application and for the OpenTelemetry Collector, Jaeger, Grafana, PostgreSQL and Redis. When the workspace runs, it downloads the OpenTelemetry Demo and runs it through docker compose. Instructions for running and accessing the OpenTelemetry Demo This workspace definition is provided trough this GitHub repo and could be opened on Gitpod with. I have created a simple Gitpod workspace definition that allows you to have this demo running in a few minutes tops. The application architecture for the demo stack looks like this:Ī front end web application – a web store for astronomy products – interacts directly and indirectly with different services – each implemented in different technologies.Īll of these obviously have been instrumented in the OpenTelemetry way and therefore interactions in the web store result in end to end traces being produced, gathered and published. Recently the OpenTelemetry project launched a demo application that demonstrates many aspects of instrumentation, metrics and trace gathering, providing insight across multi-service, multi-technology application stacks and in general how to leverage OpenTelemetry.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |