Himmat Singh Dulawat (4x Sitecore MVP)

Problem Statement: As part of the cloud infrastructure monitoring activities, the Sitecore Cloud Operations team identified an event and shared an email regarding the Sitecore Cloud Alert 'SearchStax CPU Usage.' We received alerts indicating that high CPU usage was detected on all nodes of the Solr deployment. Upon further investigation, the following observations were made: High CPU usage and system load High indexing activities  Solution: A CPU Usage alert is a Threshold Alert that notifies you via email when the CPU of your SearchStax Managed Search service deployment exceeds a specified threshold for a certain number of minutes. This triggers an Incident in the Managed Search Dashboard. Here are some recommendations to enhance SearchStax performance and improvement: 1. ContentSearch.SearchMaxResults/Lowering &rows=1000000 This setting determines the number of search results the search provider is asked to retrieve...

Problem Statement: Due to certain business requirements, we create fields read-only or hide them from the author to avoid unnecessary confusion while ensuring business logic is implemented.  In Sitecore Content Hub, we create a field property from the Content-Type option, there is no way to hide it during the creation process. Solution: There are two types of members for content types: content members and detail members . Content members represent individual pieces of content and are editable on the content detail page. Detail members represent content metadata and can be hidden from the content detail page. To meet the above requirements, you can change the member type from content to detail by moving the member to the M.Content schema page. Next, you can update the entity details component to ensure this member does not appear on the page. Happy Sitecoreing  😊