-
Notifications
You must be signed in to change notification settings - Fork 2
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
prelim elk docker-compose #25
Draft
craigsteffen
wants to merge
11
commits into
main
Choose a base branch
from
elk_initial
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Conversation
This file contains 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
Believed-basically-working docker-compose.yml. This brings up ELK in a configuration that the security genreally is turned on but the ssl checking is turned off. This gets us JUST far enough that the commands that set the main root password seem to work. This commit is to put a stake in the ground. This was based on a cdrohook config file that was a bit older, so this will need to get merged in with current versions of it. Signed-off-by: Craig P Steffen <[email protected]>
Stitched together different versions of docker-compse.yml. One from the proof-of-concept version that makes ELK possibly slightly work, but which was based on an older version of the docker-compose file, and the newer docker-compse from the repo. UNTESTED
Bringing in experimental ELK config directory that the _craig file was tested with. These are untested.
From David Watkins on slack on December 10. I copied the public SSL key that they'll apparently be using, and also copied in a text file copying his instructions. We won't need this in our testing, but we'll want to incorporate this as we roll it out. I'm putting it in this branch as a separate commit on the assumption that this will become the running branch since it contains all the ELK stuff. If that doesn't turn out, then this can be cherry-picked easily enough.
Continuing the merge between Craig's ELK and main version of docker-compose.yml. Traefik now works having commented out the profiles section. This may need to be fixed later. Other UIUC component containers don't start yet.
With this version of the docker-compose.yml, all the UIUC containers come up, and the two ELK containers come up as well. With this configuration I was able to log into the elasticsearch container and at least start the password setup utility. So I'm not going to say that it's *working*, but as far as elk is concnered it works at least as far as ELK ever has at NCSA.
The previous version of the config files produced containers that were superficially working, but kibana was remaining in the "starting" state, and was not working. This is a walk back several configuration versions of the docker-compose config file and then bringing the kibana and elastic search into synch. This version of all of those files brings up all the containers, including the UIUC containers and the elk containers, which now indicate that they're "heahlthy". It's not clear exactly which of the changes is the critical one. Also these versions are going back before the big merge with main from the repo, so they will have to be re-merged. But this is the best ELK we have so far.
This was the almost-working version of the docker-compose.yml merged between the main branch from a couple of days ago and the not-quite working ELK configuration. The differences in this file against the now checked-in version of the docker-compose.yml from this branch need to be merged into that file to minimize the ugly merging that will need to bring this file into line with what's in main.
A preliminary logstash file that seems to bring up logstash but doesn't connect to anything.
Snapshot of Craig trying to get the logstash stuff to connect. Slightly working but things are apparently not connecting yet. Don't think we have a full configuration for the import pipeline in logstash.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As of December 11, this is very preliminary, but I'm starting this branch so we can track what I'm doing.
Believed-basically-working docker-compose.yml. This brings up ELK in a configuration that the security genreally is turned on but the ssl checking is turned off. This gets us JUST far enough that the commands that set the main root password seem to work.
This commit is to put a stake in the ground. This was based on a cdrohook config file that was a bit older, so this will need to get merged in with current versions of it.