Address PR feedback
parent
ace2642815
commit
a50b263525
|
@ -40,7 +40,7 @@ Notebooks are comprised of different cells. The following cell types are availab
|
|||
- **Transform: Flux Script**:
|
||||
- Use `__PREVIOUS_RESULT__` to build from data in the previous cell.
|
||||
- Enter a Flux script to transform your data.
|
||||
- **Pass-through: Markdown**: Enter explanatory notes or other information for your team members in Markdown.
|
||||
- **Pass-through: Markdown**: Enter explanatory notes or other information for yourself or one of your team members in Markdown.
|
||||
- **Pass-through: Visualization**:
|
||||
- Create a visualization of your data. For details on available visualization types and how to use them, see [Visualization types](/influxdb/cloud/visualize-data/visualization-types/).
|
||||
- Click **Export to Dashboard** in the upper right to send your cell to a new or existing dashboard.
|
||||
|
|
|
@ -34,7 +34,7 @@ Downsample data to reduce the overall disk usage as data collects over time. Thi
|
|||
```
|
||||
4. Add an **Output to Bucket** cell:
|
||||
- Select the destination bucket for your downsampled data.
|
||||
5. Add a **Markdown** cell to add a note to your team about what this notebook does. For example, the cell might say, "Downsample to one value per hour so we can do annual year-over-year performance. Sending data to downsample bucket."
|
||||
5. Add a **Markdown** cell to add a note to your team about what this notebook does. For example, the cell might say, "Downsample to one value per hour so we can do week-over-week performance. Sending data to downsample bucket."
|
||||
5. Click **Preview** in the upper left to verify that your notebook runs and preview the output.
|
||||
6. Run your notebook:
|
||||
- Click **Run** to run the notebook and write to the output bucket a single time.
|
||||
|
|
|
@ -13,11 +13,11 @@ menu:
|
|||
[Submit a request](https://w2.influxdata.com/notebooks-early-access/
) to be added to the queue, and we will send you a confirmation when you’ve been added to early access.
|
||||
{{% /note %}}
|
||||
|
||||
### No measurements appear in my bucket even there's data in it.
|
||||
### No measurements appear in my bucket even though there's data in it.
|
||||
Try changing the time range. You might have measurements prior to the time range you selected. For example, if the time range says 1h and you have written data for 1 day then you wouldn’t see any measurements in your bucket until you change the time range.
|
||||
|
||||
### "No bucket exists" error message appears.
|
||||
This error appears when the Buckets API endpoint returns a list of bucket and you don’t have access to that bucket.
|
||||
|
||||
### Metric selector crashes.
|
||||
This can occur with high cardinality buckets when there's too much data.
|
||||
This can occur with high cardinality buckets when there's too much data for the browser.
|
||||
|
|
Loading…
Reference in New Issue