Chris BoardNov 1, 2018 • 3 min read
This is the second post regarding our new Crash monitoring platform "CritiMon" coming as an early access preview in Q1 of 2019. In this post, we will be talking about registering new applications as well as what we believe to be a unique feature that other crash monitoring platforms don't provide.
In the last post, we gave a quick overview of the purpose of the platform and how it will work. If you want more information and/or want to read the rest of the posts in this series then click here.
When you've signed up for an account, the next step is to register your application. When you register, you will see the following page:
Once you've provided an application name and selected which language the app is for, you can register the application, and the application will be shown in the app view. In the app view, each app has its own unique ID which is used to initialise CritiMon along with your account API.
Registered Applications List
Now you may have noticed that in the app registration page, there is the option to select Custom SDK, and you may be asking what's that about? This lets you create your own SDK for any language and platform you want if we don't currently support the language officially. They'll be an API that you can send your crash data to, along with being able to send a JSON object to include more information that's specific to your language or platform along with the standard information that you'd likely want to send for any crash such as stacktrace, line no it failed on etc.
That's it for part 2 in our CritiMon development blog. In the next post we will be talking about viewing and managing your crashes. If you have any feedback or have any questions, then please let us know in the comments section.
*Note that screenshots are subject to change during the development of the platform so how things look in the blog post, may not be how it looks when the platform becomes available.