-
Notifications
You must be signed in to change notification settings - Fork 41
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.
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
Add sensor user journey #2986
Add sensor user journey #2986
Conversation
Overall readability score: 52.98 (🔴 -0.09)
View detailed metrics🟢 - Shows an increase in readability
Averages:
View metric targets
|
bcf8e5a
to
6dc46be
Compare
6bc301d
to
6795854
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple typos/periods but mostly looks great!
{{<imgproc src="/services/icons/data-management.svg" class="fill alignleft" style="max-width: 150px" declaredimensions=true alt="Configure the data management service">}} | ||
**1. Add the data management service** | ||
|
||
On your machine's **CONFIGURE** tab, add the **data management** service. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe more steps here like with the sensors?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
For example, you can configure data capture for several sensors on one machine, or for serveral sensors across multiple machines, to report the ambient operating temperature. | ||
You can then run queries against that data to search for outliers or edge cases, to analyze how the ambient temperature affects your machines' operation. | ||
|
||
{{< alert title="Content" color="tip" >}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
{{< alert title="Content" color="tip" >}} | |
{{< alert title="In this page" color="tip" >}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
High level I'm wondering if we can/should actually eliminate the visualization one since it doesn't really guide the user that much? Since it'd need to be specific to a given tool to actually provide step-by-step instructions, and because it relies on the data query use case anyway?
Some third-party visualization tools support the ability to directly query your data within their platform to generate more granular visualizations of specific data. | ||
You might use this functionality to visualize only a single day's metrics, limit the visualization to a select machine or component, or to isolate an outlier in your reported data, for example. | ||
|
||
While every third-party tool is different, you would generally query your data using either {{< glossary_tooltip term_id="sql" text="SQL" >}} or {{< glossary_tooltip term_id="mql" text="MQL" >}}. See the following guide on [querying sensor data](/use-cases/sensor-data-query/) for more information. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
! Wait, isn't this a bit circular? Why do we have this page if they just need to follow the query sensor data guide anyway?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that's fairly common with this style of choose your own path content. You cannot assume that they've read the other content. And if they have, they'll think "oh ok, I've reached the end of what I can get from this info"
weight: 31 | ||
type: "docs" | ||
images: ["/services/icons/data-query.svg"] | ||
description: "Query sensor data that you have synced to the Viam app using the data management service with SQL or MQL." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the exact same description as for the non-SDK one
Co-authored-by: JessamyT <[email protected]>
Co-authored-by: JessamyT <[email protected]>
Co-authored-by: JessamyT <[email protected]>
Co-authored-by: JessamyT <[email protected]>
Co-authored-by: JessamyT <[email protected]>
Co-authored-by: JessamyT <[email protected]>
Co-authored-by: JessamyT <[email protected]>
Co-authored-by: JessamyT <[email protected]>
I think that's a good observation, possibly the wrong conclusion to eliminate though. We want to show people that you can visualize. I think instead we probably want to pull in the Grafana example here but I don't want to do that in this PR. I'll make a ticket. |
Co-authored-by: JessamyT <[email protected]>
You can view a rendered version of the docs from this PR at https://docs-test.viam.dev/2986 |
I'm going to merge this now and we can do further review in a separate ticket |
Please review for content not design. I know there's some issues when viewing on small screens.
These are the how-tos:
They will replace: