search

amplitude / experiment-jvm-server

Amplitude Experiment Server-side SDK for the Java and Kotlin
MIT License
2 stars 2 forks source link

Unable to disable log #31

Open untoms opened 2 months ago

untoms commented 2 months ago

We are using experiment-jvm-server-1.0.0-beta.2, our log is flooded with below message

WARN [Evaluation] AmpId is 0 for amplitudeId bucketing; Skylab User is SkylabUser(userId=123, deviceId=deviceId, amplitudeId=0, country=null, region=null, dma=null, city=null, language=null, platform=null, version=null, startVersion=null, os=null, deviceManufacturer=null, deviceBrand=null, deviceModel=null, deviceFamily=null, deviceType=null, carrier=null, library=null, cohortIds=null, userProperties=null)

I try disable logging with config, even for root level : add below config in applaction.properties

logging.level.root=OFF

in logback.xml

<root additivity="false" level="OFF">
    <appender-ref ref="STDOUT"/>
  </root>

but log message is still printed.

is there any way to disable above log message ?

tyiuhc commented 2 months ago

@untoms Many thanks for raising this issue. This is resolved in later versions of the SDK. Are you encountering difficulties in upgrading?

untoms commented 2 months ago

thank you @tyiuhc , will inform this to team and try to upgrade

kareltan2 commented 2 months ago

hi @tyiuhc after I have upgraded SDK to version 1.4.1 (https://github.com/amplitude/experiment-jvm-server/releases/tag/1.4.1), it's still spamming log of: WARN [Evaluation] AmpId is 0 for amplitudeId bucketing; Skylab User is SkylabUser(userId=123, deviceId=deviceId, amplitudeId=0, country=null, region=null, dma=null, city=null, language=null, platform=null, version=null, startVersion=null, os=null, deviceManufacturer=null, deviceBrand=null, deviceModel=null, deviceFamily=null, deviceType=null, carrier=null, library=null, cohortIds=null, userProperties=null)

is there another things which can resolve this issue? or is there any misconfigured in our end caused this log recurring appeared?

tyiuhc commented 2 months ago

@kareltan2 Thank you for your update on this. This seems to be an issue due an experiment/flag bucketing by amplitudeId when it is not provided in the user object. To clarify, what was the operation/method that invoked this warning message?