Linter runs sweeps weekly by default, but this is configurable.
Timestamp: April 11, 2024
Linter does not currently support auto-fix, but there is work in progress to enable this in the future.
Timestamp: April 11, 2024
The batch compute savings number represents the sum of resource usage across all unused resources in the schedule over the last calendar month, aggregated and not distinguishing between different schedules. To make better estimates, you can look at past builds of the dataset and see the allocation that came from each schedule.
Timestamp: April 11, 2024
To avoid double-counting in impact tracking when removing the dataset from both schedules, you need to pass an "invalidate" flag to the second schedule as soon as you action the first.
Timestamp: April 11, 2024
An enrollment admin needs to first enable the application in the Application access section of Control Panel.
Timestamp: April 9, 2024
The alerts are flagged due to the Linter's inability to identify external transformations, treating them as false positives. The development team is actively working on enhancing Linter so that it can identify such cases better in the future.
Timestamp: April 11, 2024
Linter uses a service token with no restrictions on permissions for scanning, but user visibility on recommendations is limited by their permissions on the underlying resources. Note that Linter only considers scheduled resources for generating recommendations.
Timestamp: April 11, 2024
Integration of Linter recommendations into code repositories is not currently available. For new projects, Linter can immediately start looking for recommendations if the project's space is already in a linting scope. Some recommendations will appear immediately, while others may require a minimum duration to report a recommendation. There is no requirement for a project to exist for a specific amount of time before enabling Linter on it.
Timestamp: April 11, 2024
Yes, while there is a default lightweight profile suggested, manual tuning may be required to achieve the most optimal profile for a lightweight transform.
Timestamp: April 9, 2024
DYNAMIC_ALLOCATION_MAX_N
value be determined when updating the transform profiles for optimizing over-provisioned cores?The DYNAMIC_ALLOCATION_MAX_N
value should be determined by either switching from NUM_EXECUTORS_N
to enable dynamic allocation, thereby releasing idle executors, or by examining the job's Spark details to understand the actual average parallelism and selecting a maximum number of executors based on that. Additionally, enabling the DYNAMIC_ALLOCATION_ENABLED
profile without changing the NUM_EXECUTORS_N
profile achieves a similar optimization. Further guidance can be found in the provided documentation on dynamic allocation.
Timestamp: April 9, 2024
This is a bug currently present in the product. The immediate workaround is to manually snooze the recommendation.
Timestamp: April 17, 2024
Autofix for sweep schedules does not currently exist as a feature.
Timestamp: June 24, 2024
EXECUTOR_MEMORY_SMALL
profile?Try increasing the memory profile to EXECUTOR_MEMORY_MEDIUM
, or to EXECUTOR_MEMORY_OVERHEAD_MEDIUM
.
Timestamp: June 24, 2024
Ontology optimization can be enabled by activating non-default rules that detect inefficiencies in the Ontology. Currently, only one such rule exists: "Object type potentially unused", which is meant to detect unused object types. More rules might be made available in the future.
Timestamp: July 1, 2024
Use a Projection to compact the transactions, and schedule the Projection to build on a regular cadence, such as every 100 transactions or weekly, depending on the update frequency of the dataset.
Timestamp: June 12, 2024
The alert refers to the datasets that can be built locally and not all datasets in the workbook.
Timestamp: July 30, 2024
You can create custom sweep schedules in the space settings. By default, the Linter only runs cost rules on all spaces, but the project-scoped schedule rule is categorized under 'best practice' rules.
Timestamp: May 23, 2024
The Impact Tracking page is accessible to everyone, but only the metrics of resources that the user can view are displayed. Viewer access on the resource is required to view the associated impact summary on that resource. Additionally, to view Estimated saving and Verified saving, the user must also have the Resource management viewer/administrator
role at the enrollment level.
Timestamp: August 20, 2024
Resource saving rules do not need to be set up manually, as the sweep for that category is on by default. However, other categories, such as pipeline resilience rules, do not have a respective sweep schedule turned on by default. Some rules, such as "Force builds", can be in multiple categories (such as resource saving and pipeline resilience rules). As this rule is included in the cost savings, it is turned on by default. You can turn on more sweep schedules, such as "Best practices rules" (which feed the pipeline resilience mode), in the sweep schedule configuration in Control Panel or by individually including pipeline resilience rules.
Timestamp: August 22, 2024
By default, only cost rules are enabled in the Linter app. To enable other Pipeline Resilience rules, you need to manually configure your sweep schedule to include the appropriate rules/presets. More information on this can be found here.
Timestamp: September 17, 2024