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.

Sign up for GitHub

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

Jump to bottom

adding a log format pattern for glassfish4/payara application servers #204

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

adding a log format pattern for glassfish4/payara application servers #204

wants to merge 1 commit into from

Conversation

thomas-mc-work
Copy link

@thomas-mc-work thomas-mc-work commented May 29, 2017 •
edited
Loading

Default log format for the application servers glassfish 4 and payara (which is deriveed from glassfish). Here is an example log line:

[2017-05-15T11:45:13.506+0200] [Payara 4.1] [INFO] [] [de.tln.aexit.pp.scratch.service.HealthCheckService] [tid: _ThreadID=100 _ThreadName=http-thread-pool::http-listener-1(1)] [timeMillis: 1494841513506] [levelValue: 800] [[
  status api request -- info]]

@thomas-mc-work thomas-mc-work changed the title adding a log format pattern for glassfish 3/4/payara application servers adding a log format pattern for glassfish3/4/payara application servers Jun 2, 2017
@thomas-mc-work thomas-mc-work changed the title adding a log format pattern for glassfish3/4/payara application servers adding a log format pattern for glassfish4/payara application servers Jun 7, 2017
@thomas-mc-work
Copy link
Author

ping @ph @jsvd

@thomas-mc-work
Copy link
Author

Dear project team (@ph, @jsvd),

may I kindly ask you about any statement about this PR after three years? It's ok if you don't like it. But then please reject it to have certainty.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
needs tests patttern-request
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@thomas-mc-work @kares