René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Add support for enabling metrics in Feast Operator","articleBody":"**Is your feature request related to a problem? Please describe.**\nI'm trying to enable metrics in my Feast deployment using the Feast Operator, but there's no clear way to pass the `--metrics` flag to the online container. The documentation provides examples for Helm chart deployment but not for Operator-based deployments. When attempting to use a custom image with an entrypoint that includes the `--metrics` flag, I found that the Operator doesn't respect this entrypoint configuration.\n\n**Describe the solution you'd like**\nAdd a configuration option in the Feast Operator specification to enable metrics for the online server. Ideally, this would be a simple boolean flag in the CustomResource definition that, when set to true, would add the `--metrics` flag to the command arguments of the online container.\n\n**Describe alternatives you've considered**\nI've tried creating a custom Docker image with an ENTRYPOINT that includes the `--metrics` flag, but the Operator seems to override this with its own command. Here's my Dockerfile:\n```\nFROM quay.io/feastdev/feature-server:0.49.0\n\n# Install ddtrace with OpenTelemetry support\nRUN pip install 'ddtrace[opentelemetry]\u003e=1.0.0'\n\n# Add environmental configurations\nENV DD_TRACE_ENABLED=true\nENV DD_LOGS_INJECTION=true\nENV DD_RUNTIME_METRICS_ENABLED=true\n\n# Use feast command directly as the entrypoint with metrics flag\nENTRYPOINT [\"feast\", \"serve\", \"-h\", \"0.0.0.0\", \"-p\", \"6566\", \"--metrics\"]\n```\n\nAdditional context\n\n\nWhen examining the pods created by the Operator, I can see that my custom entrypoint is being ignored. The Operator is setting its own command:\n```\nContainers:\n  online:\n    Container ID:  containerd://f6c09abfd39d85a60bba9bc5290eca07a0c8b5120ab2e6fc16ee2676cd59d18f\n    Image:         us-central1-docker.pkg.dev/artifacts/vertex-services-docker/feast-staging:sha-41c10\n    Image ID:      us-central1-docker.pkg.dev/artifacts/vertex-services-docker/feast-staging@sha256:0956b2af3fc7bc6cca143f3a886466989d8bb0827fb2a0f1e60d26990fe4d744\n    Port:          6566/TCP\n    Host Port:     0/TCP\n    Command:\n      feast\n      --log-level\n      DEBUG\n      serve\n      -h\n      0.0.0.0\n      -p\n      6566\n```\nThe Helm chart deployment supports metrics through --set metric=true, but there doesn't seem to be an equivalent option for the Operator. Clear documentation on how to enable metrics with the Feast Operator would also be helpful.","author":{"url":"https://github.com/ronniequinonez-qz","@type":"Person","name":"ronniequinonez-qz"},"datePublished":"2025-05-01T15:57:26.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/5317/feast/issues/5317"}