This repository was archived by the owner on Feb 29, 2024. It is now read-only.
Add logging-proxy deployment to logs server #359
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Build failed. |
Contributor
Author
|
-1 Other than the failure i just made BonnyCI/logging-proxy#1 which will make the logging much easier. |
At the moment we deploy the logging proxy onto the log server on a high port. We don't need to expose this on a standard port for now because people will only follow links. In future the client side of this can be integrated into the bonnyci.org site and the websock be on whatever port we like. For now splitting that up is not worth it. I've set up the proxy so that it redirects through apache so that when we put SSL on the site this will also be affected. There's some logging magic in here to get from journald -> syslog -> file so we can later put it into logstash. Signed-off-by: Jamie Lennox <jamielennox@gmail.com>
jamielennox
force-pushed
the
logging-proxy
branch
from
d101f96 to
f3193c1
Compare
|
Build failed. |
ConsoleCatzirl
suggested changes
Apr 24, 2017
Contributor
ConsoleCatzirl
left a comment
ConsoleCatzirl
left a comment
There was a problem hiding this comment.
For the most part this looks good
|
|
||
| - role: logrotate | ||
| logrotate_configs: | ||
| - name: zuul |
Contributor
There was a problem hiding this comment.
This name should probably be logging-proxy. I think this might overwrite the zuul config if both are included on the same host.
Contributor
Author
|
For an alternative: #361 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
At the moment we deploy the logging proxy onto the log server on a high
port. We don't need to expose this on a standard port for now because
people will only follow links. In future the client side of this can be
integrated into the bonnyci.org site and the websock be on whatever port
we like. For now splitting that up is not worth it.
I've set up the proxy so that it redirects through apache so that when
we put SSL on the site this will also be affected.
There's some logging magic in here to get from journald -> syslog ->
file so we can later put it into logstash.
Signed-off-by: Jamie Lennox jamielennox@gmail.com