This report shows the metakeys that have reached their "valueMax" setting in the index of the Concentrators or Archivers. The purpose of this report is to show which metakeys you need to increase their "valueMax" setting to accommodate all the unique values that it will receive within its index slice. Read more about the "valueMax" in the RSA Link Posting Core DB: Index Customization .
This report ran daily can catch the "ValueMax Has Been Reached" condition in the last 24 hours. This report also can give you the times when the metakey had reached this condition. The example below demonstrates how the "ValueMax" reached issue looks when you encounter it.
You are working on an investigation and you need to find a particular host "somejunkhost" in the alias.host metakey. You start out with your Investigation window, set your date range for one month, and open the metakey "Hostname alias" (alias.host). You locate the "somejunkhost" in the Investigation window and you see something like this:
You click on the "somejunkhost" name (Blue Text) to narrow your query and then you see something like this:
somejunkhost (1895) <---Notice the number is no longer 2052 as it should be?
When the session numbers (in green) do not maintain consistency when drilling into the metakey value (blue), this is an indication that the "ValueMax" has been reached. The 1 month query has spanned multiple index slices and one or more of those slices does not have the information for "somejunkhost" in the alias.host metakey. The information is in the metadb but not in the index. To access the information you can use another metakey, like ip.src/ip.dst or something that is directly associated with the hostname. Accessing or pivoting from those keys will make the values visible like a metakey that has been indexed with a "indexkeys" setting.