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

JSON schema #115

Closed
anfly0 opened this issue Oct 20, 2019 · 1 comment
Closed

JSON schema #115

anfly0 opened this issue Oct 20, 2019 · 1 comment
Labels

Comments

@anfly0
Copy link
Contributor

anfly0 commented Oct 20, 2019

Does anyone know if there is any official or reasonably correct JSON schema available for the /entries endpoint?

I'm currently looking at moving some methods from the RaygunClient class to the RaygunMessage class, and it would be great to have a schema to check the serialized message objects aginst.

The main problem I'm having is the documentation is not very clear on what fields are mandatory.

@BenjaminHarding
Copy link
Contributor

Sorry for the delayed reply @anfly0.

This is a bit tricky to answer, because different fields are "required" for different things. The fields that are absolutely required is occurredOn and details - this will allow the api to accept it but they won't be that useful. It's likely that we'll want error => className, message, stackTrace => className, methodName to get the minimum useful information.

Additional fields are then added depending on what else is needed or found useful when debugging issues.

Hope that clears some stuff up?

@anfly0 anfly0 closed this as completed Dec 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants