-
Notifications
You must be signed in to change notification settings - Fork 440
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Actually e2e test java #3381
base: main
Are you sure you want to change the base?
Actually e2e test java #3381
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -20,3 +20,6 @@ spec: | |
traces: | ||
receivers: [otlp] | ||
exporters: [debug] | ||
metrics: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. java auto inst can send metrics too, why not accept them :) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. +1 |
||
receivers: [otlp] | ||
exporters: [debug] |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -9,11 +9,9 @@ spec: | |
- name: OTEL_EXPORTER_OTLP_ENDPOINT | ||
value: http://localhost:4317 | ||
- name: OTEL_EXPORTER_OTLP_TIMEOUT | ||
value: "20" | ||
value: "20000" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this is to account for the collector not being ready fast enough There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. What happens if it's not ready? Shouldn't this work correctly either way? |
||
- name: OTEL_TRACES_SAMPLER | ||
value: parentbased_traceidratio | ||
- name: OTEL_TRACES_SAMPLER_ARG | ||
value: "0.85" | ||
value: always_on | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. don't want our test data to be sampled |
||
- name: SPLUNK_TRACE_RESPONSE_HEADER_ENABLED | ||
value: "true" | ||
exporter: | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -49,3 +49,37 @@ spec: | |
catch: | ||
- podLogs: | ||
selector: app=my-java-multi | ||
- name: "wait for app to be ready" | ||
try: | ||
- sleep: | ||
duration: 5s | ||
- name: Make a request to the app | ||
try: | ||
- script: | ||
content: | | ||
#!/bin/bash | ||
# set -ex | ||
pod=$(kubectl get pods -n $NAMESPACE | awk '{print $1}' | tail -n 1) | ||
kubectl get --raw /api/v1/namespaces/$NAMESPACE/pods/${pod}:8080/proxy/ | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this is new to me :) @IshwarKanse does it work on OCP? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Looking at this, I really wonder if we shouldn't use e2e_framework and/or terratest for these tests. The main problem is really getting data out of the cluster, as we don't have a remote we can easily query. I can think of a few solutions to do this in kind, but they won't work on OpenShift. It'd be best if these could simply be Go tests we could run on a host against any cluster. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This can be implemented natively using Chainsaw We were also discussing on implementing some kind of custom store in Chainsaw which gathers all the signals and would be useful for asserting. https://docs.google.com/document/d/1G4uDMrC3okF2q2qyNYTg2qj7yxNBjSTGgn8pBEXEeiw/edit#heading=h.8mm7ay5rgjs6 @eddycharly Do we have any decision on what custom store we can use for testing observability data. ? |
||
check: | ||
($error): ~ | ||
($stdout): Hello World! | ||
- name: "wait for the telemetry to be there" | ||
try: | ||
- sleep: | ||
duration: 5s | ||
- name: Check the sidecar has sent request data successfully | ||
try: | ||
- script: | ||
content: | | ||
#!/bin/bash | ||
# set -ex | ||
pod=$(kubectl get pods -n $NAMESPACE | awk '{print $1}' | tail -n 1) | ||
kubectl get --raw /api/v1/namespaces/$NAMESPACE/pods/${pod}:8888/proxy/metrics | ||
check: | ||
($error): ~ | ||
# TODO: Check that the number is non-zero and that failed is zero | ||
(wildcard('*otelcol_exporter_sent_spans*', $stdout)): true | ||
catch: | ||
- podLogs: | ||
selector: app=my-java-multi |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -19,4 +19,7 @@ spec: | |
traces: | ||
receivers: [otlp] | ||
exporters: [debug] | ||
metrics: | ||
receivers: [otlp] | ||
exporters: [debug] | ||
mode: sidecar |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -41,3 +41,6 @@ spec: | |
traces: | ||
receivers: [otlp] | ||
exporters: [debug] | ||
metrics: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. i was going to attempt the TLS test, but it seemed way too hard to do on a first-pass |
||
receivers: [otlp] | ||
exporters: [debug] |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -19,4 +19,7 @@ spec: | |
traces: | ||
receivers: [otlp] | ||
exporters: [debug] | ||
metrics: | ||
receivers: [otlp] | ||
exporters: [debug] | ||
mode: sidecar |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this version does not work on go 1.22. I would wait with updating before we upgrade the go version
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If that's a concern for us, we should install it by downloading the release binary instead. Our supported Go version shouldn't get in the way of tooling upgrades.