Skip to content

Commit 177db3b

Browse files
authored
Merge branch 'main' into merge-button
2 parents 7de17f1 + 016ed5f commit 177db3b

File tree

6 files changed

+65
-0
lines changed

6 files changed

+65
-0
lines changed
Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
# Binary-based Color Stack
2+
3+
import BrowserWindow from '@site/src/components/BrowserWindow';
4+
5+
For quick troubleshooting, you can use the binary-based color stack mode to quickly identify the most expensive binaries in the rendered flamegraph. In binary-based color stack mode, the colour of a node in the flamegraph is based on the
6+
binary that the function belongs to. This way, you can quickly identify the most expensive binaries in the given profile.
7+
8+
### How to use it
9+
Open the User Preferences dialog by clicking the gear icon in the top-right corner of the UI.
10+
11+
<BrowserWindow>
12+
13+
![User Preferences Option](../static/img/parca/user-preferences-icon.png)
14+
</BrowserWindow>
15+
<br />
16+
17+
In the User Preferences dialog, select your preferred color profile in the `Flamegraph Color Profile` section and click `Close`.
18+
19+
20+
<BrowserWindow>
21+
22+
![Color Profile Selection](../static/img/parca/color-profile-selection.gif)
23+
24+
</BrowserWindow>
25+
<br />
26+
27+
:::tip
28+
You can always switch back to the `Default` color profile to disable the binary-based color stack mode.
29+
:::
30+
31+
<br />
32+
33+
You can also click on the `Binary` names at the top to highlight the nodes corresponding to that binary in the flamegraph.
34+
35+
<BrowserWindow>
36+
37+
![Highlighting Nodes From a Binary](../static/img/parca/highlighting-nodes-from-binary.png)
38+
39+
</BrowserWindow>
40+
<br />

docs/observability.mdx

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,20 @@ Parca exposes Prometheus metrics on [localhost:7070/metrics](http://localhost:70
2626
Parca's monitoring is mostly focused on read and write requests to Parca.
2727
For that reason the `grpc_server_handled_total` is the most important metric for Parca and most of the other metrics and helpful for debugging overall.
2828

29+
There are some FrostDB specific metrics that are useful to monitor as well.
30+
31+
| Metric | Description | Type |
32+
| ----------------------------|------------------------------------------------------------ | --------- |
33+
| `frostdb_granules_compactions_total`| Number of per table compaction events that have occurred. | counter |
34+
| `frostdb_granules_created_total` | Number of per table granules that have been created. | counter |
35+
| `frostdb_blocks_rotated_total` | Number of per table blocks that have rotated out. | counter |
36+
| `frostdb_active_table_block_size` | The estimated size in bytes of each tables active block size. | gauge |
37+
| `frostdb_row_insert_size` | Per table tracking of the size in bytes of rows inserted. | histogram |
38+
| `frostdb_thanos_objstore_bucket_last_successful_upload_time`| If bucket storage is enabled, the last successful upload to the bucket. | gauge |
39+
| `frostdb_thanos_objstore_bucket_operation_failures_total` | Total number of bucket operations that have failed. | counter |
40+
| `frostdb_tx_high_watermark` | The transaction number that is safe to read up to. | gauge |
41+
42+
2943
### Service Level Objectives
3044

3145
Here are some example Service Level Objectives for Parca.

sidebars.js

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -41,6 +41,17 @@ module.exports = {
4141
},
4242
"observability",
4343
"configuration",
44+
{
45+
type: "category",
46+
label: "Profile Visualization",
47+
items: [
48+
{
49+
type: "category",
50+
label: "Flamegraph",
51+
items: ["flamegraph-binary-based-colour-stack"],
52+
},
53+
],
54+
},
4455
],
4556
},
4657
{
1.73 MB
Loading
876 KB
Loading
148 KB
Loading

0 commit comments

Comments
 (0)