- Sort Score
- Result 10 results
- Languages All
Results 1 - 8 of 8 for Done (0.15 sec)
-
helm/minio/templates/_helper_create_svcacct.txt
echo \"Failed attempts: $ATTEMPTS\" ; if [ $ATTEMPTS -gt $LIMIT ]; then exit 1 ; fi ; sleep 2 ; # 2 second intervals between attempts $MC_COMMAND ; STATUS=$? ; done ; set -e ; # reset `e` as active return 0 } # checkSvcacctExists () # Check if the svcacct exists, by using the exit code of `mc admin user svcacct info` checkSvcacctExists() {
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/metrics/prometheus/README.md
metrics_path: /minio/v2/metrics/bucket scheme: http static_configs: - targets: ['localhost:9000'] ``` ##### Node (optional) Optionally you can also collect per node metrics. This needs to be done on a per server instance. The scrape configurations should use all the servers under `targets` so that graphing systems like grafana can visualize them for all the nodes ```yaml scrape_configs: - job_name: minio-job
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) -
docs/metrics/v3.md
query API metrics for buckets `test1` and `test2`, make a scrape request to `/minio/metrics/v3/api/bucket?buckets=test1,test2`. Instead of a metrics scrape, it is also possible to list the metrics that would be returned by a path. This is done by adding a `?list` query parameter. The MinIO server will then list all possible metrics that could be returned. During an actual metrics scrape, only available metrics are returned - not all of them. With the `list` query parameter, the output format...
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu May 02 17:37:57 GMT 2024 - 28.5K bytes - Viewed (0) -
docs/metrics/README.md
## Prometheus Probe MinIO allows reading metrics for the entire cluster from any single node. This allows for metrics collection for a MinIO instance across all servers. Thus, metrics collection for instances behind a load balancer can be done without any knowledge of the individual node addresses. The cluster wide metrics can be read at `<Address for MinIO Service>/minio/v2/metrics/cluster`.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Feb 29 18:35:20 GMT 2024 - 1.9K bytes - Viewed (0) -
docs/distributed/CONFIG.md
- Mixing `local-path` and `distributed-path` is not allowed, doing so would cause MinIO to refuse starting the server. - Ellipses notation (e.g. `{1...10}`) or bracket notations are fully allowed (e.g. `{a,c,f}`) to have multiple entries in one line. > 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
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) -
docs/metrics/prometheus/list.md
# Cluster Metrics MinIO collects the following metrics at the cluster level. Metrics may include one or more labels, such as the server that calculated that metric. These metrics can be obtained from any MinIO server once per collection by using the following URL: ```shell https://HOSTNAME:PORT/minio/v2/metrics/cluster ``` Replace ``HOSTNAME:PORT`` with the hostname of your MinIO deployment.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Apr 25 22:01:31 GMT 2024 - 43.4K bytes - Viewed (2) -
docs/extensions/s3zip/README.md
## How to enable S3 ZIP behavior ? Ensure to set the following header `x-minio-extract` to `true` in your S3 requests. ## How to access to files inside a ZIP archive Accessing to contents inside an archive can be done using regular S3 API with a modified request path. You just need to append the path of the content inside the archive to the path of the archive itself. e.g.:
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Wed Apr 10 16:28:27 GMT 2024 - 3K bytes - Viewed (0) -
CREDITS
ensure that, in the event an Application does not supply the function or data, the facility still operates, and performs whatever part of its purpose remains meaningful, or b) under the GNU GPL, with none of the additional permissions of this License applicable to that copy. 3. Object Code Incorporating Material from Library Header Files.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Apr 26 06:31:35 GMT 2024 - 1.6M bytes - Viewed (0)