search

temporalio / cli

Command-line interface for running Temporal Server and interacting with Workflows, Activities, Namespaces, and other parts of Temporal
https://docs.temporal.io/cli
MIT License
250 stars 34 forks source link

[Feature Request] There should not be error-level logs on startup #633

Open dandavison opened 1 month ago

dandavison commented 1 month ago

When starting up with no previous DB contents, there should not be any errors (or warnings).

$ /opt/homebrew/bin/temporal server start-dev
time=2024-08-09T12:36:38.477 level=ERROR msg="service failures" operation=GetSystemInfo error="Frontend is not healthy yet"
time=2024-08-09T12:36:38.477 level=WARN msg="error creating sdk client" service=worker error="failed reaching server: Frontend is not healthy yet"
CLI 1.0.0 (Server 1.24.2, UI 2.28.0)

Server:  localhost:7233
UI:      http://localhost:8233
Metrics: http://localhost:50972/metrics

v1.0

dandavison commented 1 month ago

Another one seen (on recent server) is

time=2024-08-09T13:12:52.750 level=ERROR msg="Skipping notification for new tasks, processor not registered" shard-id=1 address=127.0.0.1:52909 component=history-engine queue-task-category-id=7
time=2024-08-09T13:12:52.756 level=WARN msg="error in prometheus reporter" error="a previously registered descriptor with the same fully-qualified name as Desc{fqName: \"workflow_context_cleared\", help: \"workflow_context_cleared counter\", constLabels: {}, variableLabels: {service_name,operation,cache_type,namespace_id}} has different label names or a different help string"