Remove Group warning 17001 warning from logs

[MelanieWawryk]

The Group warning 17001 is unnecessary and only serves to clog up the log making it difficult to read. It already warns us that groups are not used in Feature services when publishing but they are useful in map services so we still use them. There should be a spot to remove common and unnecessary errors from logs like 17001. 

[AmandaDeMedeiros]

Unfortunately, you are running into a known limitation.

Error Code: Group warning 17001

A map service with group layers has feature access enabled. This is a known limit as the following data types are not supported in feature services:

• Annotations
• Dimensions
• Group layers
• Layers and tables based on SDE views
• Raster datasets
• Terrains

You could disable feature access on the map service and the error would no longer be present. Alternatively, you could ungroup the data in ArcMap/ArcGIS Pro and publish a new map service to enable feature access. 

• https://enterprise.arcgis.com/en/server/latest/publish-services/windows/author-feature-services.htm

You can manage your logs by setting the retention date of your logs to help with disk space. 

• Log Retention

If it's annoying to view, you could filter the warnings. Perhaps, put a range on the error code numbers and exclude the number 17001? You can do that in Server Manager or Server Admin Directory. 

• To filter based on a range of codes and individual codes, specify the beginning and ending code (separated by a dash) and separate the individual codes with a comma (for example, 204000–205999, 212015, 219114).
• Example:
  • 1-17000,17002-169999

[MelanieWawryk]

Thanks that is a good suggestion. Ideally, it would be nice if there was a config file where you could specify codes you don't want to see in the manager log window. The admin filter works all right; you need to switch to the admin though and add in the dates.  Having an additional filter like the one in admin for codes when looking through the manager log would be a nice addition. Alternatively, Esri could move that error to verbose or fine since it doesn't impact the server in any meaningful way and you were already warned about it when publishing.

[AmandaDeMedeiros]

@MelanieWawryk 

If you want your idea post to be more specific. I would suggest altering the wording to:

Enhancement: Allow ArcGIS Server/Portal to ignore certain error codes specified in a config file. However, I can see this being problematic, as users might ignore very pertinent error codes in hopes of a problem going away on its own. 

You would be required to state a specific use case to get this limitation lifted. There is most likely some backend reason why grouping is not supported. It does not state the why in the documentation that I've read.