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.

Sign up for GitHub

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

Jump to bottom

The monitor-events command only monitors default events #59

Open
codefoster opened this issue Nov 20, 2018 · 0 comments
Open

The monitor-events command only monitors default events #59

codefoster opened this issue Nov 20, 2018 · 0 comments

Comments

@codefoster
Copy link

The monitor-events command monitors the default "events" endpoint of an IoT Hub; therefore, after adding routing to send some messages to other endpoints, a developer loses all visibility into those messages.
'monitor-events' should monitor messages before they are routed. This functionality could be configurable. Ideally CLI output would include an additional field indicating the route(s) that it matched.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@codefoster