|
| 1 | +--- |
| 2 | +title: OpenTelemetry Demo 1.6 released |
| 3 | +linkTitle: Demo 1.6 Released |
| 4 | +date: 2023-11-07 |
| 5 | +author: '[Austin Parker](https://github.com/austinlparker)' |
| 6 | +--- |
| 7 | + |
| 8 | +The OpenTelemetry Demo has been updated to version 1.6, and introduces alpha |
| 9 | +support for the OpenTelemetry [Log signal](/docs/concepts/signals/logs/)! |
| 10 | + |
| 11 | +## Our thoughts on logs |
| 12 | + |
| 13 | +Why are we considering logging support to be in alpha? There are a few reasons. |
| 14 | +The most important is that this is the first time we've shipped the demo with a |
| 15 | +logging database. We chose [OpenSearch](https://opensearch.org/) as the storage |
| 16 | +backend for logs because it's a popular option that aligns with the project's |
| 17 | +license. It's worth noting that the demo doesn't require application-level logs |
| 18 | +— everything you care about is available as a span. |
| 19 | + |
| 20 | +Where logs shine is in bridging the gap between application traces and |
| 21 | +infrastructure, and over the next few releases, we plan to enhance this story by |
| 22 | +collecting Kubernetes, Envoy, and other logs relevant to the demo. |
| 23 | + |
| 24 | +If this sounds like an interesting problem, we'd love to have you as a |
| 25 | +[contributor](https://github.com/open-telemetry/opentelemetry-demo/blob/main/CONTRIBUTING.md)! |
| 26 | +We'd also appreciate any feedback you might have on how our support for logging |
| 27 | +can improve. |
| 28 | + |
| 29 | +## Other changes |
| 30 | + |
| 31 | +This release also includes some nice additions on the Kubernetes side -- you'll |
| 32 | +be able to increase the number of replicas per service, for instance. We've |
| 33 | +updated many dependencies throughout the project as well. |
| 34 | + |
| 35 | +## What's next? |
| 36 | + |
| 37 | +With the addition of logging, the demo is mostly feature-complete. However, |
| 38 | +there's more that can be done, and we're looking at a few major areas over the |
| 39 | +next months: |
| 40 | + |
| 41 | +- Increase the number of documented scenarios to demonstrate how OpenTelemetry |
| 42 | + can be used to solve real-world problems. |
| 43 | +- Ensure that the demo reflects the OpenTelemetry feature matrix and that we're |
| 44 | + showing off everything you can do with the project. |
| 45 | +- Improve our dashboards and add alerts, SLOs, and other observability features |
| 46 | + to the demo. |
| 47 | +- Support other clients and front-end RUM features as they're released. |
| 48 | + |
| 49 | +As always, we'd love to hear your feedback on the demo, and if you're looking |
| 50 | +for a place to start contributing, the demo is a great place to get involved! |
| 51 | + |
| 52 | +Check out the |
| 53 | +[demo repository](https://github.com/open-telemetry/opentelemetry-demo) for more |
| 54 | +information, and to find the latest release. |
0 commit comments