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.

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

Setting and using SELDON_ENVIRONMENT for Request Logging to use one ELK Cluster for multiple Environment #2327

Closed
os-virtualretail opened this issue Aug 26, 2020 · 0 comments
Labels
triage Needs to be triaged and prioritised accordingly

Comments

@os-virtualretail
Copy link
Contributor

MAIN MOTIVATION: Having 1 ELK Cluster for different ENVIRONMENTs ( dev/test/staging/prod)

Can we put a prefix on index to Request-Logger's ELK Indices

Right now it is like

inference-log-seldon-<NAMESPACE>-<SELDONDEPLOYMENT>-<MODELNAME>

what i want is something like

inference-log-<SELDON_ENVIRONMENT>-seldon-<NAMESPACE>-<SELDONDEPLOYMENT>-<MODELNAME>
 

as i create user based on that and have 1 ELK cluster that dev/staging/prod will log to this cluster. For me to create user via Kibana DevTools: ( I define Index Pattern to access to role).

POST _security/role/logstash_writer-dev
{
  "cluster": ["manage_index_templates", "monitor", "manage_ilm"], 
  "indices": [
    {
      "names": [ "k8s_cluster-dev-*" , "inference-log-dev-*" ], 
      "privileges": ["write","create","delete","create_index","manage","manage_ilm"]  
    }
  ]
}



POST _security/user/elastic-seldon-dev
{
  "password" : "PASS",
  "roles" : [ "logstash_writer-dev"],
  "full_name" : "Internal Logstash User for Seldon"
}

I can provide prefix to Fluentd part like:

fluentd-values.yaml: ( via elasticsearch.logstash.prefix

elasticsearch:
  hosts: ["df65d4b2795d481dbe235733219ca518.eu-central-1.aws.cloud.es.io:9243"]
  logstash:
    prefix: k8s_cluster-dev
  auth:
    enabled: true
    user: elastic-seldon-dev
    password: <PASSSWORD>
  sslVerify: false
  scheme: https
@os-virtualretail os-virtualretail added the triage Needs to be triaged and prioritised accordingly label Aug 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Needs to be triaged and prioritised accordingly
Projects
None yet
Development

No branches or pull requests

1 participant