Skip to content
This repository has been archived by the owner on Oct 5, 2023. It is now read-only.

Please explain what is MUX_NAMESPACES #7

Open
sradco opened this issue Jul 20, 2017 · 3 comments
Open

Please explain what is MUX_NAMESPACES #7

sradco opened this issue Jul 20, 2017 · 3 comments

Comments

@sradco
Copy link
Member

sradco commented Jul 20, 2017

Please elaborate on what MUX_NAMESPACES is.
In oVirt documentation we call it ovirt-env-name.
If you can mention that , it would be great.

@richm

@richm
Copy link
Member

richm commented Jul 21, 2017

This is what the README-mux.md says: https://github.com/ViaQ/Main/blob/master/README-mux.md

The MUX_NAMESPACES parameter is used to pass in a list of space-delimited namespaces to create in mux for your logs. See mux-logging-service.md for a description about how mux detects and separates logs into namespaces. Basically, you can specify a namespace for your logs, and only users who are members of those namespaces can view those logs. If you do not use MUX_NAMESPACES your logs will go into the mux-undefined namespace.

The document linked above says this: https://github.com/openshift/origin-aggregated-logging/blob/master/docs/mux-logging-service.md

The namespaces used in the tag must be added ahead of time to OpenShift - for example, something like this:

for namespace in my-namespace-a my-namespace-b ; do
    oadm new-project $namespace --node-selector=''
done

If the tag is not in the project.namespacename format, the log records will use a namespace of mux-undefined, so the log records will be in an index named something like project.mux-undefined.$mux-undefined_uuid.YYYY.MM.DD

How can I clarify the above?

Are you asking that I mention ovirt-env-name in the mux documentation? I don't think I can do that.

@sradco
Copy link
Member Author

sradco commented Jul 23, 2017

Perhaps something like this:

Download the setup-mux.sh script.

  • MUX_HOST parameter - The FQDN you will use to access mux externally, and will also be used in the mux TLS server cert subject DN.

  • MUX_NAMESPACES parameter - Represents the environment name that you are sending logs from.
    It is a list of space-delimited namespaces, to create in mux for your logs. Only users who are members of those namespaces can view those logs.

See mux-logging-service.md for a description about how mux detects and separates logs into namespaces.

Note: If you do not use MUX_NAMESPACES, your logs they will go into the mux-undefined namespace.

Update the MUX_HOST and MUX_NAMESPACES below and run the following commands:

@richm
Copy link
Member

richm commented Jul 23, 2017

Sounds good. If you like, just submit that as a PR and I'll merge it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants