Recommend path for pulling Application Insights data

[alfredmyers]

Global Service Monitor has been used to ping against a couple dozen URLs for a couple of years now.
The resulting data is extracted and summarized by a custom application to show periods of unavailability (start, finish, timespan) of each URL.
Now, GSM monitoring is being phased out in favor of Application Insights.

I have prototyped a working sample that pulls data directly from the REST APIs (https://api.applicationinsights.io/v1/apps/) using HttpClient.

I also have another working prototype that references Microsoft.Azure.ApplicationInsights and Microsoft.Azure.Management.ApplicationInsights, but both are in preview and haven't been updated in a while. Are these two going to move forward? If so, any estimates on when they'll RTW?

[alexeldeib]

Hi! I've been working towards a 1.0.0 (stable) release for the Microsoft.Azure.ApplicationInsights package. We plan to continue supporting the C# SDK as a way to retrieve, metrics, events, and logs. Prior to stable release we may switch to using a package name like Microsoft.Azure.ApplicationInsights.Query to reduce ambiguity with Microsoft.ApplicationInsights (for sending telemetry to App Insights).

I'm currently syncing up a fairly large PR with breaking changes. After that, I'd like to see some usage with the new version and work out kinks. I'd expect something stable here soon -- ideally Oct '18, conservatively Dec '18.

I can't comment on a timeline for the management plane side of things. These will likely get some love in the near-but-not-immediate future.

If I can help in other ways with the App Insights REST API, please let me know 😊

[alexeldeib]

@alfredmyers BTW -- New package is live. I'm still working on reference info + docs for this. If you prototyped, it looks fairly similar to the existing client. Key changes:

• Metrics, Events, and Query are distinguished into their own interfaces, with method names slightly renamed to reflect this.
  • e.g. client.GetMetric -> client.Metrics.Get
  • for metrics extension methods there is still e.g. client.Metrics.GetMetricSummary. This isn't consistent with the other naming, is a possible candidate for further refinement as e.g. client.Metrics.GetSummary
• AppId is now a parameter to methods rather than a property on the client. This makes querying more than one app easy with a single client.
• Query results should now return values as their actual types, rather than forcing them all into strings.
• Various parameter fixes. C# TimeSpans don't model all of our time values properly, so some are strings. Tightened and loosened validation as necessary on some other parameters (e.g., MetricId, MetricsAggregration)

If you are interested in trying this out, I'd love to get some direct feedback to shape any additional changes before 1.0.0 👍 Unfortunately until the docs are sync'd as well (in progress), I can only point to the source and tests for specific usage.

[older]

@alexeldeib Maybe SDK documentation should be updated as well, as it still points to the old NuGe package.