Forum Discussion
Solved
Adding a column in a Log Analytic Workspace dashboard for writing notes
Hi! I am designing a Dashboard with Monitoring information I get from my Agent. I managed to make a dashboard which shows me all the current issues, but I want to a column to this table so I can ...
- Got it (I hope 😉 ).
The challenge is that Azure Dashboards / Workbooks are read only (they read the Log Analytics data). So whilst you could type in a number for example to a field, it isn't written back to Log Analytics (so you lose it when you refresh).
So for Option 2, what you can do is run a process, like a Logic App (there maybe other options, but I don't know Jira/confluence well enough). This would read the Jira record when one is created manually or automatically, or on a update action and create in a custom Log Analytics table the updated row, (with new Incident Number etc...). So when Jira is updated the dashboard would see the change from the custom table + plus any other Log Analytics table you wish to correlate with.
Data written to Log Analytics (1.) --> Monitor Alert fires (2.) --> data sent to Jira api where a ticket number is applied (3.)
Logic App triggers (4.)when a new Jira record (or update is made) --> data written to a custom Table in Log Analytics
Step 2/3 can be manual for now
You are right, I didn't gave you the complete picture.
Indeed first data is written to Log Analytics (1.) ---> then Monitoring sends an alert (2.) (I didn't add this yet) ---> then ideally a ticket in Jira is made automatically, but for now we want to first make a Jira ticket manually. Then the information of the Jira ticket (who, ticketnumber and current status) is put into a Azure Monitoring Dashboard again so everyone who uses the dashboard know that the issue is being managed (or not).
So I think there are 2 options:
1. I add 3 column to an Azure Log Analytics Dashboard so someone can manually add a name, ticketnumber and status.
2. A ticket with the right information is made in Jira automatically and each time the issue gets updated in Jira (a change of status or a change of person working on it), this is updated in the Azure Dashboard as well.
I hope I explained the problem well now!
What do you think the right way is?
Indeed first data is written to Log Analytics (1.) ---> then Monitoring sends an alert (2.) (I didn't add this yet) ---> then ideally a ticket in Jira is made automatically, but for now we want to first make a Jira ticket manually. Then the information of the Jira ticket (who, ticketnumber and current status) is put into a Azure Monitoring Dashboard again so everyone who uses the dashboard know that the issue is being managed (or not).
So I think there are 2 options:
1. I add 3 column to an Azure Log Analytics Dashboard so someone can manually add a name, ticketnumber and status.
2. A ticket with the right information is made in Jira automatically and each time the issue gets updated in Jira (a change of status or a change of person working on it), this is updated in the Azure Dashboard as well.
I hope I explained the problem well now!
What do you think the right way is?
Got it (I hope 😉 ).
The challenge is that Azure Dashboards / Workbooks are read only (they read the Log Analytics data). So whilst you could type in a number for example to a field, it isn't written back to Log Analytics (so you lose it when you refresh).
So for Option 2, what you can do is run a process, like a Logic App (there maybe other options, but I don't know Jira/confluence well enough). This would read the Jira record when one is created manually or automatically, or on a update action and create in a custom Log Analytics table the updated row, (with new Incident Number etc...). So when Jira is updated the dashboard would see the change from the custom table + plus any other Log Analytics table you wish to correlate with.
Data written to Log Analytics (1.) --> Monitor Alert fires (2.) --> data sent to Jira api where a ticket number is applied (3.)
Logic App triggers (4.)when a new Jira record (or update is made) --> data written to a custom Table in Log Analytics
Step 2/3 can be manual for now
The challenge is that Azure Dashboards / Workbooks are read only (they read the Log Analytics data). So whilst you could type in a number for example to a field, it isn't written back to Log Analytics (so you lose it when you refresh).
So for Option 2, what you can do is run a process, like a Logic App (there maybe other options, but I don't know Jira/confluence well enough). This would read the Jira record when one is created manually or automatically, or on a update action and create in a custom Log Analytics table the updated row, (with new Incident Number etc...). So when Jira is updated the dashboard would see the change from the custom table + plus any other Log Analytics table you wish to correlate with.
Data written to Log Analytics (1.) --> Monitor Alert fires (2.) --> data sent to Jira api where a ticket number is applied (3.)
Logic App triggers (4.)when a new Jira record (or update is made) --> data written to a custom Table in Log Analytics
Step 2/3 can be manual for now
- Thank you very much!
This really helps and I think option 2 is the right way to go.