IssueTracker

Issue Statement* :
Unrelated errors grouped together and  for the errors Validation failed is the same  but the route is different  and the actual error is different as well

Problem you have encountered:
Unrelated errors grouped together and  for the errors Validation failed is the same  but the route is different  and the actual error is different as well”
By comparing two samples of the error group the issue as in both the samples the "Validation failed" is the same but the route is different, and the actual error is different as well.
The issue is  that CX does not get notified if something NEW happens and also CX needs to frequently check the logs manually.

What you expected to happen:
 -Is there any option or click button available on existing error groups and make it read only ?

-Is there any configuration setting available for no new logs are allowed to be added to the group and a new group will get opened instead upon a new occurrence?

Note:
As suggested by the TSE both are not  currently possible, need to open a Feature Request .Please take in count Engineer  team will evaluate the need of these features and can or can't be added to the dev path.
 


Steps to reproduce: NA


Other information (workarounds you have tried, documentation consulted, etc):
Work Performed* : Over the GVC trying to find  out the report samples error reporting
    GCP console>> te-preferences >> error reporting >> error groups>> report samples
     Comparing two samples of the error group clarified the issue as in both the samples the "Validation failed" is same but the route is different, and the actual error is different as well.
 
Explained error reporting how they grouping  with an example :
   
   - GCE Application A getting same error 10 times the error reporting throws it to one error  group and generate as alert, If the GCE Application  B getting the same alert for 10 times it is also through to same error group which error group alert by GCE Application  A