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
I discussed this briefly yesterday with some of the team. On some deployments we do not have access to the deployment server and so we cannot use k9s for debugging. That makes it trickier to quickly infer the source of deployment issues. Making logs available somewhere on QHub would be very helpful.
@aktech suggested a combination of fluentd and Elasticsearch to provide a convenient interface for the user...
The text was updated successfully, but these errors were encountered:
@leej3 this is a complicated issue I think this question is generally about how you would like more insight into what is happening on the Kubernetes cluster. Logging is only part of this. There are solutions out there for log aggregation and on the cloud providers e.g. gcp, aws, and others they actually already aggregate logs for you and expose them via their own monitoring tools.
Ideally your team should be given read only access to the qhub deployment namespace and then you can view much more than just logs.
Description
I discussed this briefly yesterday with some of the team. On some deployments we do not have access to the deployment server and so we cannot use k9s for debugging. That makes it trickier to quickly infer the source of deployment issues. Making logs available somewhere on QHub would be very helpful.
@aktech suggested a combination of fluentd and Elasticsearch to provide a convenient interface for the user...
The text was updated successfully, but these errors were encountered: