Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Most commands only generate DEBUG event for successful completion #1712

Open
jphickey opened this issue Jul 26, 2021 · 0 comments · May be fixed by #2575
Open

Most commands only generate DEBUG event for successful completion #1712

jphickey opened this issue Jul 26, 2021 · 0 comments · May be fixed by #2575

Comments

@jphickey
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Most commands will increment the command counter for the application and send a debug event after they are processed. However, in the default/sample config, debug events are filtered out, so these will NOT be visible to the operator. As such there is really no way to confirm a specific command was accepted - since any command will increment the command counter (including noop, etc) the counter by itself is not a reliable means to check if a particular command was accepted.

Describe the solution you'd like
Generally, the fact that a command was accepted and processed is useful and necessary information for operators, so it should not be classified only as "DEBUG". Consider making all these events to be of type CFE_EVS_EventType_INFORMATION.

Note that some commands, such as no-op, already send an INFORMATION event (so not fully consistent as it is).

Additional context
Noted when reviewing command documentation in #1396. For Caelum will just document the EID that is currently being generated (debug or information) but will not change it. For next release should try to make this more consistent.

Requester Info
Joseph Hickey, Vantage Systems, Inc.

@skliper skliper added this to the cFS-Draco milestone Jul 26, 2021
@skliper skliper removed this from the Draco milestone Mar 18, 2022
thnkslprpt added a commit to thnkslprpt/cFE that referenced this issue Jun 22, 2024
thnkslprpt added a commit to thnkslprpt/cFE that referenced this issue Jun 24, 2024
thnkslprpt added a commit to thnkslprpt/cFE that referenced this issue Jul 9, 2024
thnkslprpt added a commit to thnkslprpt/cFE that referenced this issue Jul 9, 2024
thnkslprpt added a commit to thnkslprpt/cFE that referenced this issue Jul 10, 2024
thnkslprpt added a commit to thnkslprpt/cFE that referenced this issue Jul 10, 2024
thnkslprpt added a commit to thnkslprpt/cFE that referenced this issue Jul 10, 2024
@thnkslprpt thnkslprpt linked a pull request Jul 10, 2024 that will close this issue
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants