-
Notifications
You must be signed in to change notification settings - Fork 158
[LLM Observability] Add new landing page #782
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+80
−0
Merged
Changes from all commits
Commits
Show all changes
33 commits
Select commit
Hold shift + click to select a range
ee50689
Add new LLM obs page
alaudazzi d9c6011
Edits
alaudazzi 6149699
Add links to integrations pages
alaudazzi 746261f
Add links to otel distros
alaudazzi bedaf9f
More edits
alaudazzi 8f64355
Add image for the first use case
alaudazzi df0544e
Add more images for use cases
alaudazzi c2f23af
Merge branch 'main' into llm-observability
alaudazzi e4160d3
Merge branch 'main' into llm-observability
alaudazzi c10ad22
Add integrations and instrumentaions tables
alaudazzi 399a4ca
Merge branch 'llm-observability' of github.com:elastic/docs-content i…
alaudazzi 0162235
Update solutions/observability/apps/llm-observability.md
alaudazzi fc7cb75
Update solutions/observability/apps/llm-observability.md
alaudazzi f9f41eb
Update opentelemtry link
alaudazzi e001d45
Integrate Daniela's suggestions
alaudazzi 6511d42
Integrate Christoph's suggestion
alaudazzi d676101
Merge branch 'main' into llm-observability
alaudazzi f3f9d96
Merge branch 'main' into llm-observability
alaudazzi c684a86
Merge branch 'main' into llm-observability
alaudazzi d5a83b5
Update link to quickstart
alaudazzi 47a0230
Merge branch 'main' into llm-observability
alaudazzi 94770d0
Merge branch 'main' into llm-observability
alaudazzi 873f16c
Integrate Daniela's feedback
alaudazzi 252433d
Merge branch 'main' into llm-observability
alaudazzi 08b482b
Update AWS Boto link
alaudazzi 0e9f4f9
Update solutions/observability/apps/llm-observability.md
alaudazzi d268c0d
Change heading level for GS
alaudazzi c07b0a4
Merge branch 'main' into llm-observability
alaudazzi 88c5646
Replace table with link to supported technologies
alaudazzi b63caed
Merge branch 'llm-observability' of github.com:elastic/docs-content i…
alaudazzi b38951a
Merge branch 'main' into llm-observability
alaudazzi a26136b
Merge branch 'main' into llm-observability
alaudazzi 13bbc39
Add links to the source column
alaudazzi File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,78 @@ | ||
--- | ||
navigation_title: "LLM Observability" | ||
alaudazzi marked this conversation as resolved.
Show resolved
Hide resolved
|
||
--- | ||
|
||
# LLM Observability | ||
|
||
While LLMs hold incredible transformative potential, they also bring complex challenges in reliability, performance, and cost management. Traditional monitoring tools require an evolved set of observability capabilities to ensure these models operate efficiently and effectively. | ||
To keep your LLM-powered applications reliable, efficient, cost-effective, and easy to troubleshoot, Elastic provides a powerful LLM observability framework including key metrics, logs, and traces, along with pre-configured, out-of-the-box dashboards that deliver deep insights into model prompts and responses, performance, usage, and costs. | ||
Elastic’s end-to-end LLM observability is delivered through the following methods: | ||
|
||
- Metrics and logs ingestion for LLM APIs (via [Elastic integrations](https://www.elastic.co/guide/en/integrations/current/introduction.html)) | ||
- APM tracing for LLM Models (via [instrumentation](https://elastic.github.io/opentelemetry/)) | ||
|
||
## Metrics and logs ingestion for LLM APIs (via Elastic integrations) | ||
|
||
Elastic’s LLM integrations now support the most widely adopted models, including OpenAI, Azure OpenAI, and a diverse range of models hosted on Amazon Bedrock and Google Vertex AI. Depending on the LLM provider you choose, the following table shows which source you can use and which type of data -- log or metrics -- you can collect. | ||
|
||
| **LLM Provider** | **Source** | **Metrics** | **Logs** | | ||
|--------|------------|------------| | ||
| [Amazon Bedrock](https://www.elastic.co/guide/en/integrations/current/aws_bedrock.html)| [AWS CloudWatch Logs] [impl-bedrock](https://github.com/elastic/integrations/tree/main/packages/aws_bedrock#compatibility) | ✅ | ✅ | | ||
| [Azure OpenAI](https://www.elastic.co/guide/en/integrations/current/azure_openai.html)| [Azure Monitor and Event Hubs] [impl-azure](https://github.com/elastic/integrations/tree/main/packages/azure_openai#azure-openai-integration) | ✅ | ✅ | | ||
| [GCP Vertex AI](https://www.elastic.co/guide/en/integrations/current/gcp_vertexai.html) | [GCP Cloud Monitoring] [impl-vertexai](https://github.com/elastic/integrations/tree/main/packages/gcp_vertexai#overview) | ✅ | 🚧 | | ||
| [OpenAI](https://www.elastic.co/guide/en/integrations/current/openai.html) | [OpenAI Usage API] [openai-usage](https://platform.openai.com/docs/api-reference/usage) | ✅| 🚧 | | ||
|
||
## APM tracing for LLM models (via instrumentation) | ||
|
||
Elastic offers specialized OpenTelemetry Protocol (OTLP) tracing for applications leveraging LLM models hosted on OpenAI, Azure, and Amazon Bedrock, providing a detailed view of request flows. This tracing capability captures critical insights, including the specific models used, request duration, errors encountered, token consumption per request, and the interaction between prompts and responses. Ideal for troubleshooting, APM tracing allows you to find exactly where the issue is happening with precision and efficiency in your LLM-powered application. | ||
|
||
You can instrument the application with one of the following Elastic Distributions of OpenTelemetry (EDOT): | ||
|
||
- [Python](https://github.com/elastic/elastic-otel-python) | ||
- [Node.js](https://github.com/elastic/elastic-otel-node) | ||
- [Java](https://github.com/elastic/elastic-otel-java) | ||
|
||
EDOT includes many types of instrumentation. This [table](https://elastic.github.io/opentelemetry/use-cases/llm/#supported-technologies) lists the supported technologies. | ||
|
||
### Getting started | ||
|
||
Check [these instructions](https://elastic.github.io/opentelemetry/use-cases/llm/) on how to setup and collect OpenTelemetry data for your LLM applications. | ||
|
||
## Use cases | ||
|
||
### Understand LLM performance and reliability | ||
|
||
For an SRE team optimizing a customer support system powered by Azure OpenAI, Elastic’s [Azure OpenAI integration](https://www.elastic.co/guide/en/integrations/current/azure_openai.html) provides critical insights. They can quickly identify which model variants experience higher latency or error rates, enabling smarter decisions on model deployment or even switching providers based on real-time performance metrics. | ||
|
||
:::{image} ../../../images/llm-performance-reliability.png | ||
:alt: LLM performance and reliability | ||
:screenshot: | ||
::: | ||
|
||
### Troubleshoot OpenAI-powered applications | ||
|
||
Consider an enterprise utilizing an OpenAI model for real-time user interactions. Encountering unexplained delays, an SRE can use OpenAI tracing to dissect the transaction pathway, identify if one specific API call or model invocation is the bottleneck, and monitor a request to see the exact prompt and response between the user and the LLM. | ||
|
||
:::{image} ../../../images/llm-openai-applications.png | ||
:alt: Troubleshoot OpenAI-powered applications | ||
:screenshot: | ||
::: | ||
|
||
### Addressing cost and usage concerns | ||
|
||
For cost-sensitive deployments, being acutely aware of which LLM configurations are more cost-effective is crucial. Elastic’s dashboards, pre-configured to display model usage patterns, help mitigate unnecessary spending effectively. You can use out-of-the-box dashboards for metrics, logs, and traces. | ||
|
||
:::{image} ../../../images/llm-costs-usage-concerns.png | ||
:alt: LLM cost and usage concerns | ||
:screenshot: | ||
::: | ||
|
||
### Understand compliance with guardrails in Amazon Bedrock | ||
|
||
With the Elastic Amazon Bedrock integration for Guardrails, SREs can swiftly address security concerns, like verifying if certain user interactions prompt policy violations. Elastic's observability logs clarify whether guardrails rightly blocked potentially harmful responses, bolstering compliance assurance. | ||
|
||
:::{image} ../../../images/llm-amazon-bedrock-guardrails.png | ||
:alt: Elastic Amazon Bedrock integration for Guardrails | ||
:screenshot: | ||
::: | ||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.