OpenTelemetry (OTEL) Instruments in BusinessWorks (BW)

OpenTelemetry (OTEL) Instruments in BusinessWorks (BW)

book

Article ID: KB0137963

calendar_today

Updated On:

Products Versions
TIBCO ActiveMatrix BusinessWorks 6.12.0

Description

 

  • UpDownCounters : These instruments have been implemented in BW for job-level data, such as total job counts, scheduled job counts, faulted job counts, etc.
  • Gauge: For system, process, and activity-related data—such as active thread counts per app node, total used memory, recent execution time, CPU uptime, CPU percentage, etc.—Gauge has been used as the instrument to hold the metric data.

Meters Created for Engine Side:-

Imetrics / Job Data Meters (Counters)

Aggregated meter –
"com_tibco_bw_lmetrics"
"job_status" is the actual attribute for job status
Below are different values for the "job_status" attribute

System Data Meters (Gauges)

(Below are the meters)

Process & Activity Data Meters (Gauges)

(Below are the meters)
com_tibco_bw_process_metrics – get the number of executions of each process
com_tibco_bw_process_metrics – get the number of executions of each activity (failed/completed)

completed.jobs

(job completed including sub-process)

 

com_tibco_bw_used_memory_percent

(Percentage used memory per appnode)

 

 

com_tibco_bw_process_max_execution_time / com_tibco_bw_activity_max_execution_time

(Maximum time taken among done process/activity since it started and completed)

 

 

faulted.jobs

( job faulted including sub-process)

 

 

com_tibco_bw_used_memory

(Used memory per appnode)

 

com_tibco_bw_process_recent_execution_time com_tibco_bw_activity_recent_execution_time

(Recently time taken by process/activity)

 

com_tibco_bw_used_heap_memory

(used heap memory)

 

com_tibco_bw_process_min_elapsed_time / com_tibco_bw_activity_min_elapsed_time

(Minimum elapsed time among activities/processes))

 

com_tibco_bw_used_cpu_percent

(CPU percentage used)

 

 

paged.jobs

(job paged including sub-process)

 

com_tibco_bw_total_heap_memory

(Total heap memory)

 

com_tibco_bw_process_recent_elapsed_time / com_tibco_bw_activity_recent_elapsed_time

(Recently elapsed time for an activity or process)

 

 

com_tibco_bw_process_recent_elapsed_time / com_tibco_bw_activity_recent_elapsed_time

(Recently elapsed time for an activity or process)

 

for more detailed information please refer :-

https://docs.tibco.com/pub/activematrix_businessworks/6.9.1/doc/html/Default.htm#binding-palette/commands.htm?Highlight=elapsedtime

 

scheduled.jobs

(job scheduled including sub-process)

 

com_tibco_bw_free_memory

(Free memory per appnode)

 

com_tibco_bw_process_min_execution_time / com_tibco_bw_activity_min_execution_time

(Minimum time taken among done process/activity since it started and completed)

 

com_tibco_bw_free_heap_memory

(free heap memory)

 

com_tibco_bw_process_max_elapsed_time / com_tibco_bw_activity_max_elapsed_time

(Maximum elapsed time among activities/processes)

 

cancelled.jobs

(job cancelled including sub-process)

 

com_tibco_bw_cpu_up_time

(CPU UP time for appnode)

 

com_tibco_bw_process_total_elapsed_time / com_tibco_bw_activity_total_elapsed_time

( Elapsed time is the time difference (in milliseconds) between start time and end time of activity/process)

 

total.jobs

(Total job created including sub-process)

 

com_tibco_bw_active_thread_count

(no. of threads active per Appnode)

 

com_tibco_bw_process_total_execution_time com_tibco_bw_activity_total_execution_time

(Total time taken since it started and completed the execution)

 

 

 

 

 

   
     
     
     
     
     
     
     
     
     

 

 

Issue/Introduction

To support observability in TIBCO BusinessWorks (BW), OpenTelemetry (OTEL) instruments have been integrated to collect various runtime metrics as mentioned in the following table.