Part 3 indeed.  That means, there are two other parts in this series, and if you haven’t read about it, and if you’re interested in learning more about how to handle Telemetry for your Business Central business – I can suggest to read my previous posts about it 😉

• Handling Business Central Telemetry like a boss: my Azure Data Explorer dashboard
• Handling Business Central Telemetry like a boss: my Azure Data Explorer dashboard – Pt. 2

In the latter, I suggested that I was working on getting our internal app available, that sends even more telemetry than we have available out-of-the-box.  I would come back to it – this post is me coming back to it 😉.

More Telemetry with the iFacto Telemetry app

Disclaimer

I’ll start with a few disclaimers right away.  I mean .. I know.  Sending telemetry with an app on AppSource that’s not yours, is a risk: where do you send your Telemetry to??  Well, we did not set up the applicationInsightsConnectionString in the app.json of this app.  Meaning: we don’t get any signal in our telemetry: it’s all yours, or the customer’s, or whoever sets up Telemetry on the service.

Second – it is not an Open Source project.  Simply because I didn’t have the intention to make it Open Source, and now, so many months later, the effort doesn’t beat the purpose from how I see it.  If you have suggestions: contact me!  You want access to the source code?  It’s in the symbols.

Please note that you are using this service at your own discretion and risk. We cannot be held liable for any consequences that may arise from its use.  Remember, if you’re not interested in some events, then you have “data collection rules” to rule them out! I might extend the functionality a bit, although I don’t like the thought users being able to switch off Telemetry.. .

Last thing: this app is free, and will be free for eternity.

Feedback? You can give feedback to me through the contact page on this blog or via mail if you have it.

What does it enable?

Well – in this blogpost, I’ll give you an overview.  In a following one, I might go into more details of certain of these signals.  Let’s see.. 😉.

Here’s a brief overview of what it brings to the table today:

I won’t go into detail just yet, because in my opinion, while they are quite self-explanatory, it’s also interesting to dive into all of these topics in a separate post.  So .. I’ll dedicate specific posts to it, but for now – in the light of my previous posts .. it DOES enable the following tabs in my dashboard:

• CT: Custom Events
• CT: Performance
• Daily – Missing Indexes
• Daily – Media Orphans
• Daily – Apps
• Daily – Retention Policy
• Daily – Features

“CT” stands for “Custom Telemetry”, and “Daily” stand for “Daily Telemetry” (or pretty much signals that are meant to be sent every day).  Admittedly, some tabs need more love – but in general, the most important ones have quite interesting tiles. 

Check them out!

Make sure your daily Telemetry is getting triggered

Last thing I want to mention for now is: make sure your daily telemetry is running.  This is especially true for OnPrem customers, but even for SaaS it’s worth to check!  How do you check?  Easy: make sure your Job queue is running codeunit 1350 on a daily basis:

That’s it.  Hope you like it.  If you have suggestions – comment down below, send me a mail, or use the contact page!  If you don’t like it – don’t use it 🤪🤷‍♂️

Enjoy!