- Sort Score
- Result 10 results
- Languages All
Results 1 - 8 of 8 for alias (0.22 sec)
-
docs/metrics/prometheus/README.md
supports a bearer token approach to authenticate prometheus scrape requests, override the default Prometheus config with the one generated using mc. To generate a Prometheus config for an alias, use [mc](https://min.io/docs/minio/linux/reference/minio-mc.html#quickstart) as follows `mc admin prometheus generate <alias> [METRIC-TYPE]`. The valid values for METRIC-TYPE are `cluster`, `node`, `bucket` and `resource` and if not mentioned, it defaults to `cluster`. The command will generate the `scrape_configs`...
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Apr 12 15:49:30 GMT 2024 - 7.1K bytes - Viewed (0) -
helm/minio/templates/_helper_create_svcacct.txt
ACCESS=$(cat /config/rootUser) ; SECRET=$(cat /config/rootPassword) ; set +e ; # The connections to minio are allowed to fail. echo "Connecting to MinIO server: $SCHEME://$MINIO_ENDPOINT:$MINIO_PORT" ; MC_COMMAND="${MC} alias set myminio $SCHEME://$MINIO_ENDPOINT:$MINIO_PORT $ACCESS $SECRET" ; $MC_COMMAND ; STATUS=$? ; until [ $STATUS = 0 ] do ATTEMPTS=`expr $ATTEMPTS + 1` ; echo \"Failed attempts: $ATTEMPTS\" ;
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Mar 28 23:20:50 GMT 2024 - 3.4K bytes - Viewed (0) -
docs/site-replication/README.md
## Configuring Site Replication - Configure an alias in `mc` for each of the sites. For example if you have three MinIO sites, you may run: ```sh mc alias set minio1 https://minio1.example.com:9000 adminuser adminpassword mc alias set minio2 https://minio2.example.com:9000 adminuser adminpassword mc alias set minio3 https://minio3.example.com:9000 adminuser adminpassword ``` or ```sh
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Mon Feb 26 21:30:28 GMT 2024 - 3.4K bytes - Viewed (0) -
helm/minio/templates/_helper_create_bucket.txt
ACCESS=$(cat /config/rootUser) SECRET=$(cat /config/rootPassword) set +e # The connections to minio are allowed to fail. echo "Connecting to MinIO server: $SCHEME://$MINIO_ENDPOINT:$MINIO_PORT" MC_COMMAND="${MC} alias set myminio $SCHEME://$MINIO_ENDPOINT:$MINIO_PORT $ACCESS $SECRET" $MC_COMMAND STATUS=$? until [ $STATUS = 0 ]; do ATTEMPTS=$(expr $ATTEMPTS + 1) echo \"Failed attempts: $ATTEMPTS\"
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Jan 12 18:18:57 GMT 2024 - 3.5K bytes - Viewed (0) -
docs/distributed/CONFIG.md
> NOTE: MinIO environmental variables still take precedence over the `config.yaml` file, however `config.yaml` is preferred over MinIO internal config KV settings via `mc admin config set alias/ <sub-system>`. ### TODO In subsequent releases we are planning to extend this to provide things like - Reload() of MinIO server arguments without fully restarting the process.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri May 03 15:54:03 GMT 2024 - 4.2K bytes - Viewed (0) -
helm/minio/templates/_helper_create_user.txt
ACCESS=$(cat /config/rootUser) ; SECRET=$(cat /config/rootPassword) ; set +e ; # The connections to minio are allowed to fail. echo "Connecting to MinIO server: $SCHEME://$MINIO_ENDPOINT:$MINIO_PORT" ; MC_COMMAND="${MC} alias set myminio $SCHEME://$MINIO_ENDPOINT:$MINIO_PORT $ACCESS $SECRET" ; $MC_COMMAND ; STATUS=$? ; until [ $STATUS = 0 ] do ATTEMPTS=`expr $ATTEMPTS + 1` ; echo \"Failed attempts: $ATTEMPTS\" ;
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Dec 12 23:43:32 GMT 2023 - 3.2K bytes - Viewed (0) -
README.md
```sh mc admin update <minio alias, e.g., myminio> ``` - For deployments without external internet access (e.g. airgapped environments), download the binary from <https://dl.min.io> and replace the existing MinIO binary let's say for example `/opt/bin/minio`, apply executable permissions `chmod +x /opt/bin/minio` and proceed to perform `mc admin service restart alias/`.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Wed Feb 14 17:51:34 GMT 2024 - 18.7K bytes - Viewed (0) -
docs/metrics/prometheus/alerts.md
1. Start a distributed MinIO instance (4 nodes setup) 2. Start Prometheus server and AlertManager 3. Bring down couple of MinIO instances to bring down the Erasure Set tolerance to -1 and verify the same with `mc admin prometheus metrics ALIAS | grep minio_cluster_health_erasure_set_status` 4. Wait for 5 mins (as alert is configured to be firing after 5 mins), and verify that you see an entry in webhook for the alert as well as in Prometheus console as shown below ```json
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sun Jan 28 20:53:59 GMT 2024 - 4.4K bytes - Viewed (0)