[Question]: <Consider involving metrics and tracing data to analyzer?>

[dearboll]

Checklist

• I've searched for similar issues and couldn't find anything matching
• I've included steps to reproduce the behavior

Affected Components

• K8sGPT (CLI)
• K8sGPT Operator

K8sGPT Version

No response

Kubernetes Version

No response

Host OS and its Version

No response

Steps to reproduce

Will the project consider involving more data to analyzer, like metrics / tracing / logs data?

Expected behaviour

some as above.

Actual behaviour

No response

Additional Information

No response

[three-foxes-in-a-trenchcoat]

Interesting feature idea! Integrating metrics, tracing, and logs data would significantly enhance k8sgpt's diagnostic capabilities. This would allow correlation between resource issues and actual runtime behavior/performance.

However, this represents a substantial architectural enhancement requiring:

• Integration with observability backends (Prometheus, Jaeger/Tempo, Loki/ES)
• New analyzer logic to correlate k8s resources with telemetry data
• Additional configuration/authentication for external data sources
• Potential performance implications

Recommendation: Backlog
This is valuable but requires significant design and implementation work. I'd suggest:

1. Creating a design document outlining the integration approach
2. Gathering community feedback on which observability platforms to prioritize
3. Considering this for a future major release

Would be great to see a more detailed proposal on specific use cases this would address!