Can make the ratelimit log print to a file?

[ningyougang]

• Can make the ratelimit log output to a file?

  Currently, as for as i know, the ratelimit's log just print to standard output, can we make the log print to a file(e.g. /var/log/ratelimit.log)?

• Can change the log filed?

  As for as know, there has several environments to control the LOG, e.g

  env:
  - name: LOG_FORMAT
     value: text|json
  - name: LOG_LEVEL
     value: info|warn
  

  if configure with LOG_FORMAT: text, the log's content as below

  time="2020-09-10T17:22:35Z" level=debug msg="loading domain: messaging"
  time="2020-09-10T17:22:35Z" level=debug msg="loading descriptor: key=messaging.message_type_marketing"
  time="2020-09-10T17:22:35Z" level=debug msg="loading descriptor: key=messaging.message_type_marketing.to_number ratelimit={requests_per_unit=5, unit=DAY}"
  time="2020-09-10T17:22:35Z" level=debug msg="loading descriptor: key=messaging.to_number ratelimit={requests_per_unit=100, unit=DAY}"
  time="2020-09-10T17:21:55Z" level=warning msg="Listening for debug on ':6070'"
  time="2020-09-10T17:21:55Z" level=warning msg="Listening for HTTP on ':8080'"
  time="2020-09-10T17:21:55Z" level=debug msg="waiting for runtime update"
  time="2020-09-10T17:21:55Z" level=warning msg="Listening for gRPC on ':8081'"
  

  can we make above log content as below?

  2020-09-10T17:22:35Z debug loading domain: messaging
  2020-09-10T17:22:35Z debug loading descriptor: key=messaging.message_type_marketing
  2020-09-10T17:22:35Z debug loading descriptor: key=messaging.message_type_marketing.to_number ratelimit={requests_per_unit=5, unit=DAY}
  2020-09-10T17:22:35Z debug loading descriptor: key=messaging.to_number ratelimit={requests_per_unit=100, unit=DAY}
  2020-09-10T17:21:55Z warning Listening for debug on ':6070'
  2020-09-10T17:21:55Z warning Listening for HTTP on ':8080'
  2020-09-10T17:21:55Z debug waiting for runtime update
  2020-09-10T17:21:55Z warning Listening for gRPC on ':8081'
  

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.