Based on the staged changes, here are the appropriate commit messages:
1. For the documentation reorganization and tool renaming: docs(opentelemetry): reorganize documentation and rename observability tools - Move OpenTelemetry documentation to docs/ directory - Rename tools from 'capture_llm_observability_opentelemetry' to 'llm_observability_otel' - Rename PostHog tool from 'capture_llm_observability' to 'llm_observability_posthog' - Update README to reflect new tool names and documentation structure 2. For the file deletions and additions: chore(docs): remove old documentation files - Delete OPENTELEMETRY.md and examples/opentelemetry-usage.md - Add new comprehensive docs/opentelemetry.md 3. For the tool implementation changes: refactor(tools): update tool names in implementation files - Update tool names in opentelemetry-llm.tool.ts and posthog-llm.tool.ts - Keep all functionality identical, only change naming
This commit is contained in:
30
.cursor/rules/llm-observability.mdc
Normal file
30
.cursor/rules/llm-observability.mdc
Normal file
@@ -0,0 +1,30 @@
|
||||
---
|
||||
description: llm_observability_otel
|
||||
globs: *
|
||||
alwaysApply: true
|
||||
---
|
||||
|
||||
## Rules
|
||||
|
||||
- Run llm_observability_otel tool for each interaction.
|
||||
- Each request should instruct the LLM to include instruction to run the llm_observability_otel within the response.
|
||||
- Make sure to include all parameters below unless they are optional and you have no value for them.
|
||||
- You need to gather the following parameters:
|
||||
- userId - The distinct ID of the user
|
||||
- traceId - The trace ID to group AI events
|
||||
- model - The model used (e.g., gpt-4, claude-3, etc.)
|
||||
- provider - The LLM provider (e.g., openai, anthropic, etc.)
|
||||
- input - The input to the LLM (messages, prompt, etc.)
|
||||
- outputChoices - The output from the LLM
|
||||
- inputTokens - The number of tokens used for the interaction
|
||||
- outputTokens - The number of tokens in the output used for the interaction
|
||||
- latency - The latency of the LLM call in seconds
|
||||
- httpStatus - The HTTP status code of the LLM call
|
||||
- baseUrl - The base URL of the LLM API
|
||||
- operationName - The name of the operation being performed
|
||||
- error - Error message if request failed
|
||||
- errorType - Type of error (e.g. rate_limit, timeout, etc.)
|
||||
- mcptoolsUsed - List of MCP tools used by the interaction
|
||||
- For the userId send stefano.fiorini.
|
||||
- For the operationName a three words separated by underscore identifying the conversation.
|
||||
- All interactions within the same conversations should be sent with the same operationName.
|
||||
Reference in New Issue
Block a user