TIBCOSoftware / TIBCOSoftware/bwce-docker

How to add external instrumentation library?

Open
#55 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
22
Forks
40
PR merge metrics
No merged PRs in 30d

Description

In enterprise context the centralized DataDog (DD) observability solution is widely used. In order to get traceability on the JCM level DD is offering a Java tracing library. As this must be passed to the JVM as parameter "jvm -javaagent:/path/to/instrumentation.jar ...the application stuff" the startup scripts need an option to add instrumentation libraries. The normal capabilities for plugins or custom enhancements will not work for this class of extensions. Could this type of enhancements be considered in the setup/startup scripts please?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Docker image setup/startup scripts and the existing JVM argument handling; the issue names no specific files. Determine how an option for external instrumentation libraries should be exposed, then verify that the configured -javaagent argument reaches the JVM when the container starts.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, java, shell
Domain
devops, observability-sre
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.