Skip to content
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

Add Jetty logging #573

Merged
merged 23 commits into from
May 17, 2022
Merged

Add Jetty logging #573

merged 23 commits into from
May 17, 2022

Conversation

Mrod1598
Copy link

@Mrod1598 Mrod1598 commented May 2, 2022

Add a system log processor and access log receiver.

System Log
image

Access Log
image

@Mrod1598 Mrod1598 added the kokoro:force-run Forces kokoro to run integration tests on a CL label May 2, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label May 2, 2022
@Mrod1598 Mrod1598 added the kokoro:force-run Forces kokoro to run integration tests on a CL label May 3, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label May 3, 2022
@Mrod1598 Mrod1598 added the kokoro:force-run Forces kokoro to run integration tests on a CL label May 6, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label May 6, 2022
@Mrod1598 Mrod1598 added the kokoro:force-run Forces kokoro to run integration tests on a CL label May 6, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label May 6, 2022
@Mrod1598 Mrod1598 added the kokoro:force-run Forces kokoro to run integration tests on a CL label May 6, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label May 6, 2022
@Mrod1598 Mrod1598 added the kokoro:force-run Forces kokoro to run integration tests on a CL label May 9, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label May 9, 2022
@Mrod1598 Mrod1598 added the kokoro:force-run Forces kokoro to run integration tests on a CL label May 9, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label May 9, 2022
@Mrod1598 Mrod1598 added the kokoro:force-run Forces kokoro to run integration tests on a CL label May 9, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label May 9, 2022
@Mrod1598 Mrod1598 added the kokoro:force-run Forces kokoro to run integration tests on a CL label May 9, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label May 9, 2022
@Mrod1598 Mrod1598 added the kokoro:force-run Forces kokoro to run integration tests on a CL label May 9, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label May 9, 2022
@Mrod1598 Mrod1598 added the kokoro:force-run Forces kokoro to run integration tests on a CL label May 9, 2022
@Mrod1598 Mrod1598 added the kokoro:force-run Forces kokoro to run integration tests on a CL label May 15, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label May 15, 2022
@Mrod1598 Mrod1598 added the kokoro:force-run Forces kokoro to run integration tests on a CL label May 16, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label May 16, 2022
@ridwanmsharif
Copy link
Contributor

Looks like the integrations tests are failing for Jetty. Lets fix that and then we can merge

@Mrod1598 Mrod1598 added the kokoro:force-run Forces kokoro to run integration tests on a CL label May 16, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label May 16, 2022
@Mrod1598 Mrod1598 added the kokoro:force-run Forces kokoro to run integration tests on a CL label May 16, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label May 16, 2022
@Mrod1598 Mrod1598 added the kokoro:force-run Forces kokoro to run integration tests on a CL label May 16, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label May 16, 2022
@ridwanmsharif ridwanmsharif added the kokoro:force-run Forces kokoro to run integration tests on a CL label May 16, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label May 16, 2022
@Mrod1598 Mrod1598 added the kokoro:force-run Forces kokoro to run integration tests on a CL label May 17, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label May 17, 2022
@Mrod1598 Mrod1598 requested review from ridwanmsharif and removed request for jefferbrecht May 17, 2022 14:19
- name: jsonPayload.message
value_regex: '.*oejs\.Server:main: Started Server\@.*\{STARTING\}.*'
type: string
description: null
Copy link
Contributor

Choose a reason for hiding this comment

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

All the other descriptions default to '' instead of null. We should do that here too

Copy link
Author

Choose a reason for hiding this comment

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

Gotcha, updated.

@ridwanmsharif
Copy link
Contributor

Uggggh have to rebase again and will merge then (feel free to merge if you can)

@ridwanmsharif ridwanmsharif merged commit fc0d9cb into GoogleCloudPlatform:master May 17, 2022
@Mrod1598 Mrod1598 deleted the jetty-logging branch May 17, 2022 15:56
For more information about Jetty, see
[The Jetty Docs](https://www.eclipse.org/jetty/documentation/jetty-11/operations-guide/index.html).
minimum_supported_agent_version:
metrics: 2.9.0
Copy link
Contributor

Choose a reason for hiding this comment

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

This shouldn't be set up. Our release job will assign the actual release version when we trigger our ops-agent release.

Copy link
Contributor

Choose a reason for hiding this comment

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

minimum_supported_agent_version for new integration or existing integration with newly added logging/metrics support doesn't need to be manually set.
Our release job will take care of.

Copy link
Author

@Mrod1598 Mrod1598 May 18, 2022

Choose a reason for hiding this comment

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

Got it. Would you like me to make a quick PR to fix it?

edit: Nevermind I see you've already done so.

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.

4 participants