We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Seems like some metrics would be useful:
Also the fact that the operator just keeps on being healthy when there is an error (slack is down now) seems somewhat wrong.
With Slack down the operator remains healthy and no errors are being logged, from looking at the code they should be logged, but not seeing anything.
The text was updated successfully, but these errors were encountered:
E.g. if an incorrect url is entered, how would anyone tell. Maybe non-transient errors should terminate the operator (e.g. 404).
Sorry, something went wrong.
add metrics IBMStreams#25
28f6aa8
Merge pull request #44 from markheger/metrics
e25f8e6
add metrics #25
No branches or pull requests
Seems like some metrics would be useful:
Also the fact that the operator just keeps on being healthy when there is an error (slack is down now) seems somewhat wrong.
With Slack down the operator remains healthy and no errors are being logged, from looking at the code they should be logged, but not seeing anything.
The text was updated successfully, but these errors were encountered: