I want to write ensemble alerts to a separate file other than console.log. Anyone have suggestion on how to implement it.
Thanks
Shiva
Shiva
Ensemble alerts aren't written to the console log by default. These are typicallyissues with message routing or queue length.
But Cache system monitor alerts are. These are typically system issues such as file full or lock table full issues.
Can you clarify the problem you are trying to solve because the solutions are different
Dave
Sent from my Verizon, Samsung Galaxy smartphone-------- Original message --------From: shivapannala reddy <shivapa...@gmail.com>Date: 11/29/17 4:42 PM (GMT+10:00)To: "InterSystems: Ensemble in Healthcare" <Ensemble-in-Healthcare@googlegroups.com>Subject: [InterSystems-EnsHlth] Writing ensemble error alerts to another file
Hi
I want to write ensemble alerts to a separate file other than console.log. Anyone have suggestion on how to implement it.
Thanks
Shiva
--
You received this message because you are subscribed to the Google Groups "InterSystems: Ensemble in Healthcare Community" group.
To post to this group, send email to Ensemble-in-Healthcare@googlegroups.com
To unsubscribe from this group, send email to Ensemble-in-Healthcare-unsub...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/Ensemble-in-Healthcare?hl=en
---
You received this message because you are subscribed to the Google Groups "InterSystems: Ensemble in Healthcare" group.
To unsubscribe from this group and stop receiving emails from it, send an email to Ensemble-in-Healthcare+unsub...@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "InterSystems: Ensemble in Healthcare Community" group.
To post to this group, send email to Ensemble-in-Healthcare@googlegroups.com
To unsubscribe from this group, send email to Ensemble-in-Healthcare-unsub...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/Ensemble-in-Healthcare?hl=en
---
You received this message because you are subscribed to a topic in the Google Groups "InterSystems: Ensemble in Healthcare" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/Ensemble-in-Healthcare/k5co4CbZslA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to Ensemble-in-Healthcare+unsub...@googlegroups.com.
Hi David,Thank you for reply.1.I want to write any errors in ensemble production like error in transformation or errors in any business components to a separate file instead of console.log.For example - I want to write error message like the file path does not exist.2. Is it possible to write cache monitor alerts as you mentioned to a file?Thanks,Shiva
On Nov 29, 2017 11:30 AM, "David Loveluck" <David.Loveluck@intersystems.com> wrote:
Shiva
Ensemble alerts aren't written to the console log by default. These are typicallyissues with message routing or queue length.
But Cache system monitor alerts are. These are typically system issues such as file full or lock table full issues.
Can you clarify the problem you are trying to solve because the solutions are different
Dave
Sent from my Verizon, Samsung Galaxy smartphone-------- Original message --------From: shivapannala reddy <shivapa...@gmail.com>Date: 11/29/17 4:42 PM (GMT+10:00)To: "InterSystems: Ensemble in Healthcare" <Ensemble-in-Healthcare@googlegroups.com>Subject: [InterSystems-EnsHlth] Writing ensemble error alerts to another file
Hi
I want to write ensemble alerts to a separate file other than console.log. Anyone have suggestion on how to implement it.
Thanks
Shiva
--
You received this message because you are subscribed to the Google Groups "InterSystems: Ensemble in Healthcare Community" group.
To post to this group, send email to Ensemble-in-Healthcare@googlegroups.com
To unsubscribe from this group, send email to Ensemble-in-Healthcare-unsubscri...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/Ensemble-in-Healthcare?hl=en
---
You received this message because you are subscribed to the Google Groups "InterSystems: Ensemble in Healthcare" group.
To unsubscribe from this group and stop receiving emails from it, send an email to Ensemble-in-Healthcare+unsubscri...@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "InterSystems: Ensemble in Healthcare Community" group.
To post to this group, send email to Ensemble-in-Healthcare@googlegroups.com
To unsubscribe from this group, send email to Ensemble-in-Healthcare-unsubscri...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/Ensemble-in-Healthcare?hl=en
---
You received this message because you are subscribed to a topic in the Google Groups "InterSystems: Ensemble in Healthcare" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/Ensemble-in-Healthcare/k5co4CbZslA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to Ensemble-in-Healthcare+unsubscri...@googlegroups.com.
The simplest way to handle alerts is to create a configuration item in your production called Ens.Alert. The class that implements that can be any BP or BO.
If all alerts are to be sent to a single place this could be a business operation that could use email, http, files or whatever technology you want. In your case it seems as if a business operation that uses a file adapter would be the way to go. There are plenty of examples in the documentation.
If you want to send different alerts to different places, or perhaps transform or filter alerts before sending them on, then you should configure Ens.Alert to be a BP that uses a routing engine. Then you have a lot of power and flexibility to control where your alerts go.
By the way, these days the InterSystems Developer Community is a much more active place that this google group. There are all sorts of questions, articles and announcements there. You should consider posting future questions there.
Check out https://community.intersystems.com/
Dave
From: ensemble-in...@googlegroups.com [mailto:ensemble-in...@googlegroups.com]
On Behalf Of shivapannala reddy
Sent: Wednesday, November 29, 2017 2:19 AM
To: Ensemble-in...@googlegroups.com
Subject: Re: [InterSystems-EnsHlth] Writing ensemble error alerts to another file
I mean to write event log data of production monitor to a file.
On Nov 29, 2017 12:39 PM, "shivapannala reddy" <shivapa...@gmail.com> wrote:
Hi David,
Thank you for reply.
1.I want to write any errors in ensemble production like error in transformation or errors in any business components to a separate file instead of console.log.
For example - I want to write error message like the file path does not exist.
2. Is it possible to write cache monitor alerts as you mentioned to a file?
Thanks,
Shiva
On Nov 29, 2017 11:30 AM, "David Loveluck" <David.L...@intersystems.com> wrote:
Shiva
Ensemble alerts aren't written to the console log by default. These are typicallyissues with message routing or queue length.
But Cache system monitor alerts are. These are typically system issues such as file full or lock table full issues.
Can you clarify the problem you are trying to solve because the solutions are different
Dave
Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------
From: shivapannala reddy <shivapa...@gmail.com>
Date: 11/29/17 4:42 PM (GMT+10:00)
To: "InterSystems: Ensemble in Healthcare" <Ensemble-in...@googlegroups.com>
Subject: [InterSystems-EnsHlth] Writing ensemble error alerts to another file
Hi
I want to write ensemble alerts to a separate file other than console.log. Anyone have suggestion on how to implement it.
Thanks
Shiva
--
You received this message because you are subscribed to the Google Groups "InterSystems: Ensemble in Healthcare Community" group.
To post to this group, send email to Ensemble-in...@googlegroups.com
To unsubscribe from this group, send email to Ensemble-in-Healt...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/Ensemble-in-Healthcare?hl=en
---
You received this message because you are subscribed to the Google Groups "InterSystems: Ensemble in Healthcare" group.
To unsubscribe from this group and stop receiving emails from it, send an email to Ensemble-in-Healt...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "InterSystems: Ensemble in Healthcare Community" group.
To post to this group, send email to Ensemble-in...@googlegroups.com
To unsubscribe from this group, send email to Ensemble-in-Healt...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/Ensemble-in-Healthcare?hl=en
---
You received this message because you are subscribed to a topic in the Google Groups "InterSystems: Ensemble in Healthcare" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/Ensemble-in-Healthcare/k5co4CbZslA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to Ensemble-in-Healt...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "InterSystems: Ensemble in Healthcare Community" group.
To post to this group, send email to
Ensemble-in...@googlegroups.com
To unsubscribe from this group, send email to
Ensemble-in-Healt...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/Ensemble-in-Healthcare?hl=en
---
You received this message because you are subscribed to the Google Groups "InterSystems: Ensemble in Healthcare" group.
To unsubscribe from this group and stop receiving emails from it, send an email to Ensemble-in-Healt...@googlegroups.com.
To: "InterSystems: Ensemble in Healthcare" <Ensemble-in-Healthcare@googlegroups.com>
Subject: [InterSystems-EnsHlth] Writing ensemble error alerts to another file
Hi
I want to write ensemble alerts to a separate file other than console.log. Anyone have suggestion on how to implement it.
Thanks
Shiva
--
You received this message because you are subscribed to the Google Groups "InterSystems: Ensemble in Healthcare Community" group.
To post to this group, send email to Ensemble-in-Healthcare@googlegroups.com
To unsubscribe from this group, send email to Ensemble-in-Healthcare-unsub...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/Ensemble-in-Healthcare?hl=en
---
You received this message because you are subscribed to the Google Groups "InterSystems: Ensemble in Healthcare" group.
To unsubscribe from this group and stop receiving emails from it, send an email to Ensemble-in-Healthcare+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "InterSystems: Ensemble in Healthcare Community" group.
To post to this group, send email to Ensemble-in-Healthcare@googlegroups.com
To unsubscribe from this group, send email to Ensemble-in-Healthcare-unsub...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/Ensemble-in-Healthcare?hl=en
---
You received this message because you are subscribed to a topic in the Google Groups "InterSystems: Ensemble in Healthcare" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/Ensemble-in-Healthcare/k5co4CbZslA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to Ensemble-in-Healthcare+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "InterSystems: Ensemble in Healthcare Community" group.
To post to this group, send email to Ensemble-in-Healthcare@googlegroups.com
To unsubscribe from this group, send email to Ensemble-in-Healthcare-unsub...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/Ensemble-in-Healthcare?hl=en
---
You received this message because you are subscribed to the Google Groups "InterSystems: Ensemble in Healthcare" group.
To unsubscribe from this group and stop receiving emails from it, send an email to Ensemble-in-Healthcare+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "InterSystems: Ensemble in Healthcare Community" group.
To post to this group, send email to Ensemble-in-Healthcare@googlegroups.com
To unsubscribe from this group, send email to Ensemble-in-Healthcare-unsub...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/Ensemble-in-Healthcare?hl=en
---
You received this message because you are subscribed to a topic in the Google Groups "InterSystems: Ensemble in Healthcare" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/Ensemble-in-Healthcare/k5co4CbZslA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to Ensemble-in-Healthcare+unsub...@googlegroups.com.