-
Notifications
You must be signed in to change notification settings - Fork 11
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
Catalog update #44
Catalog update #44
Conversation
Signed-off-by: Brian McGinn <brian.mcginn@intel.com>
Signed-off-by: Brian McGinn <brian.mcginn@intel.com>
Signed-off-by: Brian McGinn <brian.mcginn@intel.com>
Signed-off-by: Brian McGinn <brian.mcginn@intel.com>
Signed-off-by: Brian McGinn <brian.mcginn@intel.com>
docs_src/use-cases/automated-self-checkout/catalog/Test-Performance.md
Outdated
Show resolved
Hide resolved
Signed-off-by: Brian McGinn <brian.mcginn@intel.com>
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.
LGTM
Do the following to launch the Grafana* dashboard to view the objects being detected and tracked: | ||
|
||
1. Open a web browser and enter the following URL to access the Grafana dashboard: | ||
``http://<target_system_IP>:3000``. |
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.
are we using target_system because the software may be running somewhere else, or why not simplify it to 127.0.0.1?
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.
It was due to us not being able to use the host network directly and some of the containers needed the host IP to since localhost and 127.0.0.1 didn't work inside the container.
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.
Something we can refactor in a future release once the latest EVAM images are published
PR Checklist
What requirement is this design document for?
Merging catalog documentation into the open source documentation
#issue_number
Anything the reviewer should know when reviewing this PR?
If there are any other design Pull Requests or requirements, please link them here (i.e. intel-retail/automated-self-checkout )