Monitor Alibaba RSocket Broker with Prometheus and Grafana Cloud
The open source project Alibaba RSocket Broker from Alibaba provides a Prometheus exporter so that you can aggregate, scrape, and push metrics to a Prometheus-compatible database. To store your Alibaba RSocket Broker application’s Prometheus metrics in a scalable, long-term remote storage service such as Grafana Cloud’s fully-managed Mimir database, follow one of the methods below.
Send Prometheus metrics from Alibaba RSocket Broker to Grafana Cloud
Choose one of the following methods for pushing your metrics to Grafana Cloud.
- Set up an agentless scrape job with the Metrics Endpoint integration (easiest)
- Deploy a Grafana Agent scraping service (most flexible)
- Modify your Prometheus instance to write metrics directly to Grafana Cloud
Need a Grafana Cloud account? Create a new account for free.
Set up an agentless scrape job with the Metrics Endpoint integration
- Navigate to your Grafana Cloud instance
- In your Grafana Cloud instance, use the left-side navigation to get to the Connections Console (Home > Connections > Add new connection).
- Search “Metrics Endpoint” to find the Metrics Endpoint configuration page.
- Enter your Scrape Job URL (Prometheus endpoint), choose between Bearer and Basic under “Type of Authentication Credentials”, and test your connection using the Test Connection button.
- Click the “Save Scrape Job” button to submit your new agentless scrape job.
That’s it! Scrapes will be automatically performed at the target scrape job URL every 60 seconds.
Deploy a Grafana Agent scraping service
If you are already using Grafana Agent in Flow mode, you may benefit from creating a new
prometheus.scrape component that will let you compose advanced Prometheus scrape configurations and easily reuse scrape configurations—all managed in one place.
Examples of advanced scrape job arguments include settings for scrape job name, scrape interval, sample limit, label limit, proxy url, and configuration blocks for oAuth authorization.
Push metrics using Prometheus remote write
Below is an example remote write code snippet. You will need to add this
remote_write block to your
prometheus.yml config file in order to forward your metrics from your local Prometheus instance to fully-managed remote storage with Grafana Cloud:
remote_write: - url: <Your Metrics instance remote_write endpoint> basic_auth: username: <Your Metrics instance ID> password: <Your Cloud Access Policy token>
You can find the
https://...grafana.net/api/prom/push URL, username, and password for your metrics endpoint in the Cloud Portal. Click your stack ‘Details’ then select the Prometheus ‘Details’. The target URL and basic auth username display towards the middle of the page.
Can’t find your Prometheus config file?
prometheus.yml config file for Alibaba RSocket Broker can be found at the following location:
Visit the Prometheus.io Configuration Docs to view additional
remote_write configuration settings.
Control your Grafana Cloud metrics expense
Every Grafana Cloud account includes 10,000 active series metric storage, free-forever. To reduce your billable metrics usage, we recommend following the guidelines below.
Reduce the number of metric data points pushed to Grafana Cloud
Grafana Cloud provides 1 data point per minute (DPM) resolution for $8 per 1,000 series. You can adjust the total DPM you push to Grafana Cloud by adjusting the
scrape_interval settings in your
prometheus.yml config file.
Identify and eliminate unused metric data
We designed Adaptive Metrics so that you can easily aggregate metrics that are unused. By applying our aggregation rules, you will block unused time series data at the time of ingestion while keeping the metric name and labels so that you can discover them if needed in the future. Adaptive Metrics is available to all Grafana Cloud users for no additional cost.