Configure request security
Request security allows you to limit requests from the Grafana server by targeting requests generated by users, such as data source metric queries and alert notifications.
This can be used to limit access to internal systems that the server Grafana runs on can access but that users of Grafana should not be able to access. This feature does not affect traffic from the Grafana users browser.
Note: Although request security works with backend plugins, you can create a backend plugin that bypasses this security.
IP and hostname blocking
You can limit requests based on a hostname, an IP address, or both.
Grafana blocks any request to a hostname or IP address on the deny list.
If there is at least one entry on the list, then any request to a hostname or IP address not on the list is denied.
[security.egress] # A list of hostnames or IP addresses separated by spaces for which requests are blocked. host_deny_list = supersecret.internal 192.168.1.10 # a list of hostnames or IP addresses separated by spaces for which requests will be allowed, all other requests will be blocked host_allow_list = prometheus.internal
Drop headers and cookies
You can set a list of cookies or headers that are to be dropped from outgoing requests.
[security.egress] # a list of headers that will be stripped from outgoing datasource and alerting requests header_drop_list = user # a list of cookies that will be stripped from outgoing datasource requests (case sensitive) cookie_drop_list = session_id
Related Grafana resources
Unify your data with Grafana plugins: Splunk, MongoDB, Datadog, and more
Show how Grafana can be used to take data from multiple different sources and unify it, without disrupting the investments that are working today.
Getting started with Grafana Enterprise and observability
Join the Grafana Labs team for a 30-minute demo of how to get started with the Grafana Stack, so you can go from zero to observability in just a few minutes.