jenkinsci / opentelemetry-plugin

Monitor and observe Jenkins with OpenTelemetry.
https://plugins.jenkins.io/opentelemetry/
Apache License 2.0
93 stars 47 forks source link

MonitoringAction NOT found on run #818

Closed josh-at-straker closed 3 months ago

josh-at-straker commented 3 months ago

Jenkins and plugins versions report

Environment ``` Jenkins: 2.440.1 OS: Linux - 5.15.0-91-generic Java: 17.0.10 - Eclipse Adoptium (OpenJDK 64-Bit Server VM) --- ant:497.v94e7d9fffa_b_9 antisamy-markup-formatter:162.v0e6ec0fcfcf6 apache-httpcomponents-client-4-api:4.5.14-208.v438351942757 authentication-tokens:1.53.v1c90fd9191a_b_ bootstrap5-api:5.3.3-1 bouncycastle-api:2.30.1.77-225.v26ea_c9455fd9 branch-api:2.1152.v6f101e97dd77 build-timeout:1.32 caffeine-api:3.1.8-133.v17b_1ff2e0599 checks-api:2.0.2 cloudbees-folder:6.901.vb_4c7a_da_75da_3 command-launcher:107.v773860566e2e commons-lang3-api:3.13.0-62.v7d18e55f51e2 commons-text-api:1.11.0-95.v22a_d30ee5d36 credentials:1337.v60b_d7b_c7b_c9f credentials-binding:657.v2b_19db_7d6e6d dark-theme:439.vdef09f81f85e display-url-api:2.200.vb_9327d658781 durable-task:550.v0930093c4b_a_6 echarts-api:5.5.0-1 email-ext:2.105 font-awesome-api:6.5.1-3 git:5.2.1 git-client:4.7.0 github:1.38.0 github-api:1.318-461.v7a_c09c9fa_d63 github-branch-source:1781.va_153cda_09d1b_ global-slack-notifier:1.5 gradle:2.10 gson-api:2.10.1-15.v0d99f670e0a_7 instance-identity:185.v303dc7c645f9 ionicons-api:56.v1b_1c8c49374e jackson2-api:2.16.2-378.v7e79818f53ce jakarta-activation-api:2.1.3-1 jakarta-mail-api:2.1.3-1 javax-activation-api:1.2.0-6 javax-mail-api:1.6.2-9 jaxb:2.3.9-1 jdk-tool:73.vddf737284550 jjwt-api:0.11.5-77.v646c772fddb_0 joda-time-api:2.12.7-29.v5a_b_e3a_82269a_ jquery3-api:3.7.1-2 jsch:0.2.16-86.v42e010d9484b_ json-api:20240303-41.v94e11e6de726 json-path-api:2.9.0-33.v2527142f2e1d junit:1259.v65ffcef24a_88 kubernetes:4193.vded98e56cc25 kubernetes-client-api:6.10.0-240.v57880ce8b_0b_2 kubernetes-credentials:0.11 ldap:711.vb_d1a_491714dc mailer:470.vc91f60c5d8e2 matrix-auth:3.2.2 matrix-project:822.824.v14451b_c0fd42 metrics:4.2.21-449.v6960d7c54c69 mina-sshd-api-common:2.12.0-90.v9f7fb_9fa_3d3b_ mina-sshd-api-core:2.12.0-90.v9f7fb_9fa_3d3b_ okhttp-api:4.11.0-172.vda_da_1feeb_c6e opentelemetry:3.1111.vc2733c03b_db_1 pam-auth:1.10 pipeline-build-step:540.vb_e8849e1a_b_d8 pipeline-github-lib:42.v0739460cda_c4 pipeline-graph-analysis:216.vfd8b_ece330ca_ pipeline-groovy-lib:704.vc58b_8890a_384 pipeline-input-step:491.vb_07d21da_1a_fb_ pipeline-milestone-step:111.v449306f708b_7 pipeline-model-api:2.2183.vb_36481468374 pipeline-model-definition:2.2183.vb_36481468374 pipeline-model-extensions:2.2183.vb_36481468374 pipeline-rest-api:2.34 pipeline-stage-step:305.ve96d0205c1c6 pipeline-stage-tags-metadata:2.2183.vb_36481468374 pipeline-stage-view:2.34 plain-credentials:179.vc5cb_98f6db_38 plugin-util-api:4.1.0 popper2-api:2.11.6-4 resource-disposer:0.23 role-strategy:711.vf33a_d2c994b_a_ scm-api:683.vb_16722fb_b_80b_ script-security:1326.vdb_c154de8669 slack:684.v833089650554 snakeyaml-api:2.2-111.vc6598e30cc65 ssh-credentials:322.v124df57ed808 ssh-slaves:2.948.vb_8050d697fec sshd:3.322.v159e91f6a_550 structs:337.v1b_04ea_4df7c8 theme-manager:215.vc1ff18d67920 timestamper:1.26 token-macro:400.v35420b_922dcb_ trilead-api:2.141.v284120fd0c46 variant:60.v7290fc0eb_b_cd workflow-aggregator:596.v8c21c963d92d workflow-api:1291.v51fd2a_625da_7 workflow-basic-steps:1049.v257a_e6b_30fb_d workflow-cps:3883.vb_3ff2a_e3eea_f workflow-durable-task-step:1331.vc8c2fed35334 workflow-job:1400.v7fd111b_ec82f workflow-multibranch:773.vc4fe1378f1d5 workflow-scm-step:415.v434365564324 workflow-step-api:657.v03b_e8115821b_ workflow-support:865.v43e78cc44e0d ws-cleanup:0.45 ```

What Operating System are you using (both controller, and any agents involved in the problem)?

k8s deployment - Containers, official Jenkins images.

Observibility endpoint is Elastic APM 8.12

Reproduction steps

After installation, and setup of the plugin, I see multiple log line relating to "MonitoringAction Not run" across all my builds.

I don't know if this affect log flow into ELK, but the dashboards appear to be missing data and not capturing job runs.

Expected Results

Observibility metrics to flow to ELK stack.

Actual Results

Log lines as below:

2024-03-11 22:07:00.176+0000 [id=1912]  INFO    i.j.p.o.j.OtelEnvironmentContributorService#addEnvironmentVariables: MonitoringAction NOT found on run builds/PROD/build_pt-vendordocs-ui #3
2024-03-11 22:07:00.181+0000 [id=1874]  INFO    i.j.p.o.j.OtelEnvironmentContributorService#addEnvironmentVariables: MonitoringAction NOT found on run builds/UAT/build_sts-website-ui #120
2024-03-11 22:07:00.185+0000 [id=1914]  INFO    i.j.p.o.j.OtelEnvironmentContributorService#addEnvironmentVariables: MonitoringAction NOT found on run builds/UAT/build_task-wb-tms-export #13
2024-03-11 22:07:00.190+0000 [id=1911]  INFO    i.j.p.o.j.OtelEnvironmentContributorService#addEnvironmentVariables: MonitoringAction NOT found on run builds/UAT/build_pt-verify-consumer #49
2024-03-11 22:07:00.253+0000 [id=1910]  INFO    i.j.p.o.j.OtelEnvironmentContributorService#addEnvironmentVariables: MonitoringAction NOT found on run builds/PROD/build_ai-translation-edits #2
2024-03-11 22:07:01.400+0000 [id=1912]  INFO    i.j.p.o.j.OtelEnvironmentContributorService#addEnvironmentVariables: MonitoringAction NOT found on run builds/PROD/build_pt-vendordocs-ui #3
2024-03-11 22:07:01.406+0000 [id=1912]  INFO    i.j.p.o.j.OtelEnvironmentContributorService#addEnvironmentVariables: MonitoringAction NOT found on run builds/PROD/build_pt-vendordocs-ui #3
2024-03-11 22:07:01.696+0000 [id=1992]  INFO    i.j.p.o.j.OtelEnvironmentContributorService#addEnvironmentVariables: MonitoringAction NOT found on run builds/UAT/build_pt-vendordocs-api #9

Anything else?

Please let me know if I need to provide more info.

Are you interested in contributing a fix?

No response

josh-at-straker commented 3 months ago

While I have solved the APM flow issue, I still have a large amount of logs with the format above. Do I need to worry about these?

kuisathaverat commented 3 months ago

It should not be an INFO message. It should be FINE or FINER. It is not an error, it is debug info.