Conversation
|
|
||
| Cons: | ||
| * Price premium compared to purely data storage-based pricing of other options, both for ingestion >5GB/month and retention >90 days | ||
| * Potential lag in data being available (potentially mitigated by Live Metrics Stream if supported for this scenario) |
There was a problem hiding this comment.
Agree that the delay (circa 5 minutes) can be a frustration. But would you be using this to debug live issues for example whilst getting a CI/CD new pipeline up and running for the first time?
| Pros: | ||
| * Built-in semantics for tracking events, exceptions etc. | ||
| * OOTB visualisation and query tools in the Azure Portal | ||
| * .Net SDK reduces up-front integration effort |
There was a problem hiding this comment.
Pro is it applies the "buy before build" principle?
Another pro is that would extend the concept of a central logging solution for "BuildDevOps", assuming Application Insights is being used already for infrastructure / application telemetry? So opportunity to look at pain points with applications through their end to end lifecycle, not just after they have been deployed?
| * Lower costs for long-term retention | ||
|
|
||
| Cons: | ||
| * Any visualisation interface will need to be built |
There was a problem hiding this comment.
Lots of small events needing to be consolidated in the data lake reminds me of the challenges Ed has been having with SmartR?
| * OOTB visualisation and query tools in the Azure Portal | ||
| * .Net SDK reduces up-front integration effort | ||
|
|
||
| Cons: |
There was a problem hiding this comment.
Application Insights also drops data if it decides it needs to, which it calls "sampling" IIRC. This is often a useful feature, enabling you to maintain an overview of what's going on without paying to capture every last bit of information. But for this sort of diagnostic logging of a single process, it could be a liability.
I've never been entirely certain if it's possible to completely disable this sampling feature. I know you can ask for it not to happen, but it's not clear to me whether it takes that as an inviolable instruction, or just a suggestion.
3 participants
Some initial thoughts on progressing the 'dev insights' concept we've talked about.