wadm
wadm copied to clipboard
[FEATURE] add `wadm.api.{lattice}.status`
It'd be nice to be able to get some information about wadm itself across the API. Specifically, the version would be good so that consumers can adjust behavior based on differences between versions.
Sample response:
{
"wadm_version": "0.0.0"
}
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this has been closed too eagerly, please feel free to tag a maintainer so we can keep working on the issue. Thank you for contributing to wasmCloud!
Bumping for now, @lachieh would you mind dropping some very minimal information that you'd expect from this endpoint? It would be great to add just a few things and mark it good-first-issue 😄
What I could think of is mostly:
- Version of wadm
- Lattices observed (number or list, list of names is more useful but in the thousands it may overflow the NATS message size)
- Outstanding commands/events?
Yeah I think those are all valid. My primary use case was the parsing of responses based on the wadm version, but I think those are also great additions. Is there a way to summarize wadm's health? All applications healthy, some pending, errors, etc? That could also be useful here, but not fully necessary. Count is probably fine on the lattices, and outstanding events/commands might be useful as a boolean or a count also.
I updated the description with a sample response. I think it's probably fine to leave this as just the version for an initial implementation and have the additional fields be subsequent features. If you'd like to add more to the response you should have edit access 👍
Is there a way to summarize wadm's health?
Good question. Other than NATS connectivity (which you would know from a response) this feels kinda like it gets into OTEL metrics and failing to ack messages. I don't think wadm has a concept currently of an internal health since it's very work-queue based
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this has been closed too eagerly, please feel free to tag a maintainer so we can keep working on the issue. Thank you for contributing to wasmCloud!
still valid
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this has been closed too eagerly, please feel free to tag a maintainer so we can keep working on the issue. Thank you for contributing to wasmCloud!