![]() Please check the help wanted label to find issues that are good for getting started. Contributeįeel free to open issues and pull requests, any feedback will be highly appreciated! HA Setup will double your requests, which may run out your quota. You can separate metrics over multiple exporter instances to scale.įor HA setup, simply duplicate your deployments: 2 * prometheus, and 2 * exporter for each prometheus. To use the prometheus integration in your installation, add the following to your configuration.yaml file: Example configuration.yaml entry prometheus: Configuration Variables Looking for your configuration file namespace string (Optional) The namespace that will be assigned to all the Prometheus metrics. The CloudMonitor API could be slow if you have large amount of resources. host:port/projects/_up, which indicates whether this metric are successfully scraped.host:port will host all the available monitor projects.You can visit the metric meta in localhost:9525 after launching the exporter. Metrics MetaĪliyun-exporter shipped with a simple site hosting the metrics meta from the CloudMonitor API. But the API of special projects could be slow, so it is recommended to separate special projects into a standalone exporter instance. Note: special projects invokes different API with ordinary metrics, so it will not consume your Cloud Monitor API invocation quota. rds_performance: RDS performance metrics, available metric names: Performance parameter tableĪn example configuration file of special project is provided as special-projects.yml.For these metrics, we keep the configuration abstraction consistent by defining special projects. Some metrics are not included in the Cloud Monitor API. Given that you have 50 metrics to scrape with 60s scrape interval, about 2,160,000 requests will be sent by the exporter for 30 days. CloudMonitor API also has an monthly quota for invocations (AFAIK, 5,000,000 invocations / month for free). Option 1: Enter this simple command in your command-line interface and create the monitoring namespace on your host: kubectl create namespace monitoring The output confirms the namespace creation.An exporter is considered essential in any cloud-native ecosystem that includes applications that don’t expose Prometheus-supported metrics by default. CloudMonitor API has an rate limit, tuning the rate_limit configuration if the requests are rejected. A Prometheus exporter aggregates and imports data from a non-Prometheus to a Prometheus system.Find your target metrics using Metrics Meta.default: 60 measure: Average # measure field in the response. default: same as the 'name' period: 60 # query period. name: QPS # required, Metric Name of CloudMonitor, belongs to a certain Project rename: qps # rename the related prometheus metric. default: 10 credential:Īccess_key_id: # required access_key_secret: # required region_id: # default: 'cn-hangzhou' metrics: # required, metrics specifications acs_cdn: # required, Project Name of CloudMonitor Rate_limit: 5 # request rate limit per second.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |