Skip to content
This repository was archived by the owner on May 26, 2023. It is now read-only.
This repository was archived by the owner on May 26, 2023. It is now read-only.

Service status driven by configuration #231

@jpwhitemn

Description

@jpwhitemn

🚀 Feature Request
Somewhat related to #119 and #103

Description

The CLI tool currently has a command for service status: ./edgex-cli status
Could that status command provide me the status of all the services listed in a configuration file if not from Consul/Registry?

Describe the solution you'd like

Since I may be adding / removing all sorts of services when developing (device services, app services, etc.), the status command could be particularly useful to provide me a quick status check. It would be enriched even more if it included an ability to check on various infrastructure elements
In other words, drive the list of service / infrastructure status returned by something like the following toml
[Services]
[Service]
Name = Core-data
Host = 'localhost'
Port = '48080'
Path ="/v1/api/ping"
[Service]
Name = Core-metadata
Host = 'localhost'
Port = '48081'
Path ="/v1/api/ping"
[Service]
Name = Core-data
Host = 'localhost'
Port = '48080'
Path ="/v1/api/ping"
[Infrastructure]
Name = RedisDB Server
Command ="redis-cli ping"

Describe alternatives you've considered

If you have integrated to SMA, the SMA could be called to provide the status of EdgeX services.
May not be as helpful in development environments where SMA is not always running and you want a quick check of what is working/up.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions