Skip to content

RC: Specify internal IP standard for Prometheus on Redis Cloud #1035

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jan 9, 2025
Merged

RC: Specify internal IP standard for Prometheus on Redis Cloud #1035

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions content/integrate/prometheus-with-redis-cloud/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,6 +56,13 @@ You can quickly set up Prometheus and Grafana for testing using the Prometheus a
- Connect to the VPC subnet that is peered with your Redis Cloud subscription.
- Allow outbound connections to port 8070, so that Prometheus can scrape the Redis Cloud server for data.
- Allow inbound connections to port 9090 for Prometheus and port 3000 for Grafana.
- Be located in one of the CIDR ranges of the RFC-1918 internal IP standard, which is comprised of three CIDR ranges:

- 10.0.0.0/8
- 172.16.0.0/12
- 192.168.0.0/16

The Prometheus endpoint is subject to a whitelist according to this standard.

### Set up Prometheus

Expand Down
Loading