In order to provide an efficient data analysis tool and balance the operational needs of Clarity Communities, Bitfocus will be implementing Looker standard practices. These policies and procedures will be in full effect by 8/1/2021. All users are encouraged to change their own practices soon to help with the transition.
- Looks - Must be used at least once every two years
- Consequence: Unused Looks will be deleted
- Custom published Clarity fields - Must be included in Looker content within 30 days of being published to Looker
- Consequence: Unused fields will be unpublished
- Dashboard Content Limit - Must have <= 25 queries/tiles per dashboard
- Consequence: Scheduling will be removed
- Consequence: Auto-refresh will be removed
- Consequence: In extreme cases where this dashboard is causing degraded looker performance, we will quarantine the dashboard
- Alternative: Consider creating multiple, linked, dashboards for better presentation
- Refer to Using HTML/Markdown to Step Up the Dashboard Game for details on how to create "tabbed" dashboards
- Dashboard Auto-refresh - Auto-refresh rate must be less than once per hour
- Consequence: Auto-refresh will be set to once per hour
- Dashboard Scheduling - Scheduling must be for less than once per hour
- Consequence: Any dashboards scheduled more than once per hour will be changed to once per hour
- More frequent scheduling cannot be supported due to Looker caching functionality
- SFTP Scheduling - Failed SFTP transfers will be retried 3 times
- Consequence: The recurrence will be ended
- SFTP addresses must be static to be reliable
- Dynamic IPs are not supported by Looker
- Field Exposure Requests
- In Looker, exposing HUD-specified fields to all instances at data collection points that do not align with HUD guidance can negatively impact shared resources over time. Our Looker Usage Policies are designed to prioritize HUD-specified and documented collection methods.
- Merge Queries
- More than 3 merged queries may result in unexpected results and will not be supported.
- Number of Fields in Looks
- More than 30 fields in a look may result in unexpected results and will not be supported.
- Query Performance
- Query performance is monitored for long-running queries. If queries exceed execution times of 60-90+ minutes, it may have an adverse effect on shared resources, resulting in the cancellation of the query to prevent replica lag and query build-up.
Updated: 01/26/2024