Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

Add feedback Subscribe
Status Future consideration
Product Feature Experimentation
Categories SDKs & Agent
Created by Guest
Created on Dec 12, 2022

RELATED FEEDBACK

Logger having error categorised into types

The Optimizely logger indicates different types of errors. Our client suggests to divide the different types of errors by type.

Example use case: our client is currently using a Regex to identify the error messages received for the error "not in datafile" (when a feature is not present in the datafile). Having the error messages categorised into types would help, and the client would not need the Regex anymore to identify specific errors.

  • Post comment
  • Guest
    Reply
    |     Dec 12, 2022

    This could be extremely beneficial for us. We are using the logger for this usecase to realize when requests for non-existing/malformed flags are made and notify the teams to fix it. Using a regex for this is very sub-optimal.

    Please consider make this a feature :)