Skip to content

v0.4.2
Compare
Choose a tag to compare
@z4kn4fein z4kn4fein released this 14 Mar 13:08
· 21 commits to main since this release
v0.4.2
27566ea
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

Added

  • Option to turn gRPC health check service on/off.

    grpc:
  health_check_enabled: true # default: true

  • Option to turn gRPC server reflection on/off.

    grpc:
  server_reflection_enabled: true # default: false

  • Option to control the keep-alive settings of the gRPC server.

    grpc:
  keep_alive: 
    # these values are only examples
    max_connection_idle: 15 # If a client is idle for 15 seconds, send a GOAWAY
    max_connection_age: 30 # If any connection is alive for more than 30 seconds, send a GOAWAY
    max_connection_age_grace: 5 # Allow 5 seconds for pending RPCs to complete before forcibly closing connections
    time: 5 # Ping the client if it is idle for 5 seconds to ensure the connection is still active
    timeout: 1 # Wait 1 second for the ping ack before assuming the connection is dead

  • Option to turn off the main HTTP server in case of gRPC-only usage.

    http:
  enabled: false # default: true

  • Two more metric indicators:

    • configcat_grpc_rpc_duration_seconds: Histogram of RPC calls (duration/count).
      • Tags:
        • method: Name of the RPC service method.
        • code: Response status code.
    • configcat_stream_msg_sent_total: Total number of all messages sent with streaming.
      • Tags:
        • sdk: The related SDK's identifier.
        • type: sse or grpc.
        • flag: The flag's key that was evaluated.

  • Detailed RPC debug logging for gRPC calls. It is enabled automatically when the gRPC's logging option is set to debug.

Changed

  • Two more status indicators were added to the /status endpoint's content down and initializing. Each SDK node starts with the initializing status, and later, when initialized, it switches to one of the remaining (healthy, degraded, or down) statuses.
    The proxy's status becomes down when each SDK has down status. It becomes degraded when at least one degraded or down SDK exists.
    • down means that the related SDK can't accept evaluation requests because it doesn't have a valid config JSON (neither from cache nor from the ConfigCat CDN) to work with.
    • degraded means that the related SDK has a valid config JSON in its memory or from the external cache, but the last two refresh attempts failed, so it might work with stale config JSON data.
  • SSE and gRPC stream requests are now rejected when the related SDK doesn't have a valid config JSON to work with or when the requested feature flag key doesn't exist. These requests were accepted before but got a null result through the built-up connection.
Assets 11
Loading