Mendix offers a few integrations with various Application and Performance Monitoring (APM) tools.
There is no integration with Azure Monitor. The closest I have is log files can be downloaded.
 |
| Cloud edition allows you to download the log files. |
TBC
Showing posts with label Azure Monitor. Show all posts
Showing posts with label Azure Monitor. Show all posts
Sunday, 13 April 2025
Tuesday, 13 August 2024
An Introduction to Pulumi for Azure
Overview: I have been using Pulumi predominantly on AWS. This post is an introduction to setting up Pulumi on VS Code and building resources out on Azure.
Setup Pulumi a new Pulumi project using VS Code, connect to Azure and retrieve a specific Azure Resource Group", the video below walks thru me setting it up.
Summary: At this point you should have a VS code TypeScript pulumi project setup that can read/access a resource group in Azure.
Series on Pulumi:
Introduction and setup Pulumi on VS Code (This post)
Monday, 30 October 2023
Thoughts on Logging and Monitoring
Overview: I mainly work in the Microsoft stack, so my default for logging as Azure Monitor. Log Analytics/Workspace and Application Insights fall under the term Azure Monitor.
Going forward MS are storing App Insight logging data within a Log analytics instance.
There are 4 options for displaying/analysis logs in Azure:
- Azure Dashboards
- Power BI
- Grafana
- Workspaces
SIEM tools take in logs from various sources such as Azure Log Analytics, Defender, other vendors Prometheus logs or Open Telemetry.
Grafana can be used on most SIEMS including Dynatrace, NewRelic, Microsoft Sentinel, or Azure Monitor. Grafana supports PromQL and has fantastic dashboarding.
Friday, 11 August 2023
App Insights for Power Platform - Part 3 - Canvas App Logging (Instrumentation key)
App Insights for Power Platform - Part 1 - Series Overview
App Insights for Power Platform - Part 2 - App Insights and Azure Log Analytics
App Insights for Power Platform - Part 3 - Canvas App Logging (Instrumentation key) (this post)
App Insights for Power Platform - Part 4 - Model App Logging
App Insights for Power Platform - Part 5 - Logging for APIM
App Insights for Power Platform - Part 6 - Power Automate Logging
App Insights for Power Platform - Part 7 - Monitoring Azure Dashboards
App Insights for Power Platform - Part 8 - Verify logging is going to the correct Log analytics
App Insights for Power Platform - Part 9 - Power Automate Licencing
App Insights for Power Platform - Part 10 - Custom Connector enable logging
App Insights for Power Platform - Part 11 - Custom Connector Behaviour from Canvas Apps Concern
Overview: Logging & monitoring for Canvas apps is done in two parts: App Insights, and using the Canvas app Monitor. This post focuses on logging via App Insights.
Note: Once a solution that contains a Instrumentation key, they app logging key cannot be alter unless you make the environment have unmanaged layers. You can use PowerCli and compose a new managed solution for each DTAP environment but it's a new compile for each environment.
Example:
In the annotated diagram below including a log snippet.
1. Canvas App has an instrumentation key, the log captures the front end action
2. Calls to Dataverse & Power automate Flows are logged (relies on step 1)
4. the function logs into APIM and sends APIM a request (APIM logging is setup on the end points), and
5. APIM sends an outbound API request and captures the response (relies on step 4)
Note in this example I have Correlation tracking enabled on the Canvas App to get the full timeline, as shown below, it has been an experimental feature for a few years now.
When I turn off the Correlation, it is not as easy to trace items from start to finish. All I get by default is the steps 3&4 data in my transaction search timeline.
All 5 pieces are still captured but the timeline has to be pieced together for tracing.
I would also enable the preview feature for logging as well as the experimental if the clients governance allows experimental features to be turned on.
Add a trace Event into your logs in a Canvas app example with a Custom Dimension
Trace("Practice | Dimension " & txtMarker.Text, TraceSeverity.Information, {appCode:"Prac-01",appInfo:"Custom Dimensions button clicked"})
Summary: Always add as many logging features as possible in Canvas Apps, think about where your logs go and also setup logging on Azure services to transaction can be traced.
App Insights for Power Platform - Part 1 - Series Overview
App Insights for Power Platform - Part 2 - App Insights and Azure Log Analytics
App Insights for Power Platform - Part 3 - Canvas App Logging (Instrumentation key) (this post)
App Insights for Power Platform - Part 4 - Model App Logging
App Insights for Power Platform - Part 5 - Logging for APIM
App Insights for Power Platform - Part 6 - Power Automate Logging
App Insights for Power Platform - Part 7 - Monitoring Azure Dashboards
App Insights for Power Platform - Part 8 - Verify logging is going to the correct Log analytics
App Insights for Power Platform - Part 9 - Power Automate Licencing
App Insights for Power Platform - Part 10 - Custom Connector enable logging (this post)
App Insights for Power Platform - Part 11 - Custom Connector Behaviour from Canvas Apps Concern
Monday, 12 June 2023
App Insights for Power Platform - Part 5 - Logging for APIM
Series
App Insights for Power Platform - Part 1 - Series Overview
App Insights for Power Platform - Part 2 - App Insights and Azure Log Analytics
App Insights for Power Platform - Part 3 - Canvas App Logging (Instrumentation key)
App Insights for Power Platform - Part 4 - Model App Logging
App Insights for Power Platform - Part 5 - Logging for APIM (this post)
App Insights for Power Platform - Part 6 - Power Automate Logging
App Insights for Power Platform - Part 7 - Monitoring Azure Dashboards
App Insights for Power Platform - Part 8 - Verify logging is going to the correct Log analytics
App Insights for Power Platform - Part 9 - Power Automate Licencing
App Insights for Power Platform - Part 10 - Custom Connector enable logging
App Insights for Power Platform - Part 11 - Custom Connector Behaviour from Canvas Apps Concern
Overview: APIM is often part of you Power Platform solutions, such as monitoring and controlling all inbound and outbound traffic or to wrap over Azure functions.
Within APIM you can add multiple App Insights Instances. You can send all logging to a single instance an override specific API's to log to different instances. Making the logging nice and granular.
 |
| Setup Logging |
The diagram below is where i used the operation Parent Id to find a log entry using the Transaction Logs in App Insights I can see the APIM entry and the entry to the backend 3rd party and their http response
- Logging can be global or set at the API level in APIM.
- Telemetry "Sampling" will log a percentage of requests.
- "Always log errors" captures any errors APIM gets.
- Headers and body are not included in logs unless you specify them.
Series
App Insights for Power Platform - Part 1 - Series Overview
App Insights for Power Platform - Part 2 - App Insights and Azure Log Analytics
App Insights for Power Platform - Part 3 - Canvas App Logging (Instrumentation key)
App Insights for Power Platform - Part 4 - Model App Logging
App Insights for Power Platform - Part 5 - Logging for APIM (this post)
App Insights for Power Platform - Part 6 - Power Automate Logging
App Insights for Power Platform - Part 7 - Monitoring Azure Dashboards
App Insights for Power Platform - Part 8 - Verify logging is going to the correct Log analytics
App Insights for Power Platform - Part 9 - Power Automate Licencing
App Insights for Power Platform - Part 10 - Custom Connector enable logging
App Insights for Power Platform - Part 11 - Custom Connector Behaviour from Canvas Apps Concern
Subscribe to:
Posts (Atom)