You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/sources/configure-client/language-sdks/dotnet.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -204,3 +204,10 @@ To configure the .NET SDK to send data to Grafana Cloud Profiles or Pyroscope, r
204
204
If you need to send data to Grafana Cloud, you'll have to configure HTTP Basic authentication. Replace `<User>` with your Grafana Cloud stack user and `<Password>` with your Grafana Cloud API key.
205
205
206
206
If your open source Pyroscope server has multi-tenancy enabled, you'll need to specify a tenant ID. Replace `<TenantID>` with your Pyroscope tenant ID.
207
+
208
+
### Locate the URL, user, and password in Grafana Cloud Profiles
209
+
210
+
[//]: #'Shared content for URl location in Grafana Cloud Profiles'
211
+
[//]: #'This content is located in /pyroscope/docs/sources/shared/locate-url-pw-user-cloud-profiles.md'
### Option: Use `DisableGCRuns` for handling increased memory usage
182
189
183
190
Pyroscope may require additional resources when tracking a lot of objects. For example, a Go service that indexes large amounts of data requires more memory.
Copy file name to clipboardExpand all lines: docs/sources/configure-client/language-sdks/java.md
+9-2Lines changed: 9 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -178,7 +178,7 @@ The Java integration supports JFR format to be able to support multiple events (
178
178
|`PYROSCOPE_PROFILER_LOCK`| Sets the threshold to register lock events, in nanoseconds (equivalent to `--lock=` in `async-profiler`). The default value is `""` - empty string, which means that lock profiling is disabled. Setting it to `0` will register every event, causing significant CPU and network overhead, making it not suitable for production environments. We recommend setting a starting value of 10ms and adjusting it as needed. |
179
179
|`PYROSCOPE_UPLOAD_INTERVAL`| Sets the interval for uploading profiling data. The default is `10s`. |
180
180
|`PYROSCOPE_JAVA_STACK_DEPTH_MAX`| Sets the maximum stack depth. The default is `2048`. |
181
-
|`PYROSCOPE_SERVER_ADDRESS`| Address of the Pyroscope server. The default is `http://localhost:4040`|
181
+
|`PYROSCOPE_SERVER_ADDRESS`| Address of the Pyroscope server. The default is `http://localhost:4040`|
182
182
|`PYROSCOPE_CONFIGURATION_FILE`| Sets an additional properties configuration file. The default value is `pyroscope.properties`. |
183
183
|`PYROSCOPE_BASIC_AUTH_USER`| HTTP Basic authentication username. The default value is `""` - empty string, no authentication. |
184
184
|`PYROSCOPE_BASIC_AUTH_PASSWORD`| HTTP Basic authentication password. The default value is `""` - empty string, no authentication. |
@@ -218,7 +218,14 @@ If you need to send data to Grafana Cloud, you'll have to configure HTTP Basic a
218
218
219
219
If your Pyroscope server has multi-tenancy enabled, you'll need to configure a tenant ID. Replace `<TenantID>` with your Pyroscope tenant ID.
220
220
221
-
#### Example configurations
221
+
### Locate the URL, user, and password in Grafana Cloud Profiles
222
+
223
+
[//]: #'Shared content for URl location in Grafana Cloud Profiles'
224
+
[//]: #'This content is located in /pyroscope/docs/sources/shared/locate-url-pw-user-cloud-profiles.md'
The following configuration sets application name, Pyroscope format, profiling interval, event, and lock.
224
231
This example is an excerpt from the [`rideshare` Dockerfile](https://github.com/grafana/pyroscope/blob/main/examples/language-sdk-instrumentation/java/rideshare/Dockerfile#L24-L34) available in the Pyroscope repository.
[//]: #'If you make changes to this file, verify that the meaning and content are not changed in any place where the file is included.'
12
+
[//]: #'Any links should be fully qualified and not relative: /docs/grafana/ instead of ../grafana/.'
13
+
14
+
<!-- Locate your stack's URL, user, and password -->
15
+
16
+
When you configure Alloy or your SDK, you need to provide the URL, user, and password for your Grafana Cloud stack.
17
+
This information is located in the **Pyroscope** section of your Grafana Cloud stack.
18
+
19
+
1. Navigate to your Grafana Cloud stack.
20
+
1. Select **Details** next to your stack.
21
+
1. Locate the **Pyroscope** section and select **Details**.
22
+
1. Copy the **URL**, **User**, and **Password** values in the **Configure the client and data source using Grafana credentials** section.
23
+

24
+
1. Use these values to complete the configuration.
25
+
26
+
As an alternative, you can also create a Cloud Access Policy and generate a token to use instead of the user and password.
27
+
For more information, refer to [Create a Cloud Access Policy](https://grafana.com/docs/grafana-cloud/security-and-account-management/authentication-and-permissions/access-policies/create-access-policies/).
0 commit comments