Mismatch in Aria Orchestrator Heap Dump filename and the date/time of creation.

Products

• VMware Aria Suite

Issue/Introduction

We could see that when the heap dump is generated automatically there is a mismatch found in the date/time of creation and also the date within the filename.

As per the below screenshot the heap dump filename is "vco_2024-07-02_07:01_heap_dump.hprof" , but the date/time is recorded as "Jul 14 07:02"

Environment

Aria Orchestrator 8.x

Resolution

This is an expected behavior as per the current design. 
When a heap dump is generated automatically, the date/time is not set to the current moment when that happens, but is the date/time when the Orchestrator is started.

For example, if the Orchestrator is started on 2024-10-10_16-05, this is the date/time that will be in the filename.

Manually generated Aria Orchestrator heap dump file date/time is matching with the file name date/time.

The steps below can be followed to generate an Aria Orchestrator Heap dump manually.

> Log ino Aria Orchestrator using SSH.

> Run the below command to generate the Heap Dump manually:

for VCO_APP in $(kubectl get pod -n prelude -l app=vco-app -o jsonpath="{.items[*].metadata.name}"); do kubectl -n prelude exec -it $VCO_APP -c vco-server-app -- bash -c "jcmd 1 GC.heap_dump /var/log/collected-logs/heapdump-$( date '+%Y-%m-%d_%H:%M' ).hprof"; done

Note : The dump will be generated in: /var/log/services-logs/prelude/vco-app/file-logs/

Reference screenshot