Skip to content

Open Feedback/Questions/Sharing #20

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

Open
uschtwill opened this issue Mar 7, 2017 · 5 comments
Open

Open Feedback/Questions/Sharing #20

uschtwill opened this issue Mar 7, 2017 · 5 comments

Comments

@uschtwill
Copy link
Owner

I just felt like opening up an avenue for users of this suite to have a conversation more easily.

So if you want to give any sort of feedback, want to share how you're using the suite, pose a quick question, or anything else of that sort, this is the place.

I am not sure how (un)orthodox its is to use issues in this way, but it seems like a legitimate thing to do - so why not? Of course, please open a separate issue for anything more discrete or serious.

Looking forward to hearing from you!

@bnjroos
Copy link

bnjroos commented May 29, 2017

Good afternoon uschtwill,

First thank you for your suite.
I am encountering a little issue when I try to install the suite in secure mode I always get the following messages:
WARNING: The DOMAIN variable is not set. Defaulting to a blank string. WARNING: The PASSWORD variable is not set. Defaulting to a blank string.
Furthermore once installed, when I try to connect to any prometheus.DOMAIN or grafana.DOMAIN for example I am just redirected to the classic Welcome to nginx! page.

Any idea why it is behaving this way ?

TIA

Benjamin

@uschtwill
Copy link
Owner Author

Hey bjnroos,

are you setting and substituting YOUR_DOMAIN and VERY_STRONG_PASSWORD with your information when running sh setup.sh secure YOUR_DOMAIN VERY_STRONG_PASSWORD? The script expects those values to be set. If you look at setup.sh and docker-compose.secure.yml you can see that they are used to set up the proxying configuration and basic auth for nginx.

Cheers
Will

@bnjroos
Copy link

bnjroos commented May 29, 2017

Yes I am using my own domain name and I have generated a password. I had a look at the file also and I have no clue why it is behaving like this.
I have also tried to set the variable prior to launching the script by using export without success.
I am on a ubuntu 16.04 distro server.

@laysp
Copy link

laysp commented Jul 3, 2017

Hi uschtwill,

Firstly, thanks for all the work you've put into this suite and its documentation. I'm not entirely clear though on how to get containers running on a different host outputting their data to the suite? I know for logging it's necessary to add:

logging:
  driver: gelf
  options:
    gelf-address: udp://suiteshostip:12201
    labels: container_group

To the docker-compose.yml used to create (for example) a Wordpress container. But nothing from my Wordpress container appears in Kibana etc. after running the secure mode setup - it only seems to be seeing the containers that make up the suite?

Also, I'm not sure how to direct container output for monitoring to the suite - presumably the above logging lines only handle the logging side of things and not monitoring or alerting?

@uschtwill
Copy link
Owner Author

@bnjroos: Sorry, at the moment I can't help you with that.

@laysp:

presumably the above logging lines only handle the logging side of things and not monitoring or alerting?

That is correct. Also the IP for gelf-addresss should not be the host's IP, but the Logstash container's IP. Inter-host aggregation of logging and metrics is not supported out of the box yet. Check this issue for details and ideas: #11

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

No branches or pull requests

3 participants