You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Summary
Improve OpenTelemetry plugin stability and observability configuration. Closes#667
## Changes
- Fixed a potential nil pointer dereference in the chat request parameter conversion by adding a nil check for message content
- Enhanced Tempo configuration to use a multiplexed HTTP/gRPC port (3200) for better compatibility
- Improved Grafana configuration with additional trace visualization options:
- Added tracesToLogs, serviceMap, and search configurations
- Enabled nodeGraph visualization
- Reduced Grafana log verbosity by setting log level to "warn"
- Disabled feature toggles in Grafana for more stable behavior
## Type of change
- [x] Bug fix
- [x] Feature
- [ ] Refactor
- [ ] Documentation
- [ ] Chore/CI
## Affected areas
- [ ] Core (Go)
- [ ] Transports (HTTP)
- [ ] Providers/Integrations
- [x] Plugins
- [ ] UI (Next.js)
- [ ] Docs
## How to test
1. Start the OpenTelemetry stack with docker-compose:
```sh
cd plugins/otel
docker-compose up -d
```
2. Access Grafana at http://localhost:4000 and verify:
- Reduced log output in the Grafana container
- Improved trace visualization options in the Tempo data source
- Ability to navigate between traces, logs, and metrics
3. Test the nil pointer fix by sending a chat request with a null content field
## Breaking changes
- [ ] Yes
- [x] No
## Related issues
Fixes potential nil pointer panic in OpenTelemetry trace collection
## Security considerations
No security implications.
## Checklist
- [x] I read `docs/contributing/README.md` and followed the guidelines
- [x] I added/updated tests where appropriate
- [x] I updated documentation where needed
- [x] I verified builds succeed (Go and UI)
- [x] I verified the CI pipeline passes locally if applicable
0 commit comments