summaryrefslogtreecommitdiff
path: root/app/services/clusters/applications
diff options
context:
space:
mode:
authorThong Kuah <tkuah@gitlab.com>2019-03-04 16:28:28 +1300
committerThong Kuah <tkuah@gitlab.com>2019-04-04 17:40:52 +1300
commit5eb2d6ea02631608095847647e02cd899613b8e1 (patch)
treeb71c81f8e04d8d8318f2a5bcebaa03e96e6ad2e9 /app/services/clusters/applications
parentd0a0d3d3d5043d1497a5cd42e6c6bc073f6a5b58 (diff)
downloadgitlab-ce-5eb2d6ea02631608095847647e02cd899613b8e1.tar.gz
Show backtrace when logging to kubernetes.log
Just the error message and error class alone makes it hard to determine the full context of any errors, so we need to know where the error is occuring as well.
Diffstat (limited to 'app/services/clusters/applications')
-rw-r--r--app/services/clusters/applications/base_helm_service.rb3
1 files changed, 2 insertions, 1 deletions
diff --git a/app/services/clusters/applications/base_helm_service.rb b/app/services/clusters/applications/base_helm_service.rb
index c38b2656260..9619cba533c 100644
--- a/app/services/clusters/applications/base_helm_service.rb
+++ b/app/services/clusters/applications/base_helm_service.rb
@@ -19,7 +19,8 @@ module Clusters
app_id: app.id,
project_ids: app.cluster.project_ids,
group_ids: app.cluster.group_ids,
- message: error.message
+ message: error.message,
+ backtrace: Gitlab::Profiler.clean_backtrace(error.backtrace)
}
logger.error(meta)