Skip to content

APPENG-4285 - Intercept Tracing Context in ExploitIQ Agent and save to DB#198

Merged
RedTanny merged 4 commits intoRHEcosystemAppEng:mainfrom
RedTanny:MLOpsAgentSide
Feb 8, 2026
Merged

APPENG-4285 - Intercept Tracing Context in ExploitIQ Agent and save to DB#198
RedTanny merged 4 commits intoRHEcosystemAppEng:mainfrom
RedTanny:MLOpsAgentSide

Conversation

@RedTanny
Copy link
Collaborator

@RedTanny RedTanny commented Feb 5, 2026

No description provided.

@RedTanny
Copy link
Collaborator Author

RedTanny commented Feb 8, 2026

/test-heavy

- Added tracing context interception
- Persisted context data to database
- Updated confusion matrix and Tekton run handling
Copy link
Collaborator

@zvigrinberg zvigrinberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@RedTanny This is a good job, that intercepts the spans and traces from the agent pipeline, in an independent manner from the agent!.
We'll need to do something similar for the online , that will not be enabled by default ( the default will be sending the traces to arize phoenix without the sidecars topology of otel collector and single broker kafka, we'll talk about how to do it.)

TRACE_VERSION = 1

# Default dispatch endpoint configuration
DEFAULT_URL = "https://exploit-iq-client-exploit-iq-tests.apps.ai-dev03.kni.syseng.devcluster.openshift.com"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@RedTanny Please change to service, this will become very critical very soon.
https://exploit-iq-client.exploit-iq-tests.svc.cluster.local:8443

Also, please verify using certificate ( ConfigMap - openshift-service-ca.crt - mount it to a volume in the container in order to access it from code for TLS Verification).

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@zvigrinberg

  1. change to url to service -- will be done
  2. certificate -- do u mean we should use it in the tekton scripts ? why ? i understand we need to use it for the online / ui flow

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@RedTanny We need to do it anyway as a matter of fact...

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I Just wanted you not to focus on it from the beginning, rather on doing the requirement itself, and then get back to it..

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok understand
will added it to the server (agent), test automation, and tracing script pod

from urllib3.util.url import parse_url

# Default dispatch endpoint configuration
DEFAULT_URL = "https://exploit-iq-client-exploit-iq-tests.apps.ai-dev03.kni.syseng.devcluster.openshift.com"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@RedTanny Please change to service, this will become very critical very soon.
https://exploit-iq-client.exploit-iq-tests.svc.cluster.local:8443

Also, please verify using certificate ( ConfigMap - openshift-service-ca.crt - mount it to a volume in the container in order to access it from code for TLS Verification).

@RedTanny RedTanny requested a review from zvigrinberg February 8, 2026 13:56
Copy link
Collaborator

@zvigrinberg zvigrinberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, good job!

@RedTanny RedTanny merged commit 738b34c into RHEcosystemAppEng:main Feb 8, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants