AppD Archive

Ignoring specific error

CommunityUser
Splunk Employee
Splunk Employee

I have a lot of notification about one specific error that appdynamics finds. I excluded it from list, but anyway notifications go and go. I put a note for future to work on this error and dont want t receive it anymore. Can you suggest how to exclude it from monitoring?

Error is:

Summary of events occurring during the 1+ minute(s) prior to Fri Sep 12 09:25:45 EEST 2014:

Count

Event Type

1

ERROR

Link...

Fri Sep 12 09:24:40 EEST 2014

[Error] - SocketException: Connection reset -

Notes:

In attachment is how I excluded this error. 
Note: I use premium appdynamics, not lite.

0 Karma

Arun_Dasetty
Super Champion

Hi,

We have bug or otherwise the way it works the option "these specifed objects" in older version had issue, for more clarity can you provide the screenshots from health rule and policy with all section of these two rules in edit view and also screenshot from email for more clarity and if possible attach server.log during recent violation period to assist you better.

Also please mention controller UI version

Regards,

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi!
Version of agent and controller is 3.9.1. Screenshots attached. 


This error is not an error itself, which appears in log files. This is something about pdf,I forwarded this to developers and they know why it appears. But this is not about it - I need to remove this error from email notifications. Below is stacktrace from appdynamics (during this nothing is written in log file):

java.net.SocketException.Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:168)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:258)
at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:698)
at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:641)
at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:663)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1218)
at java.net.URL.openStream(URL.java:1010)
at org.xhtmlrenderer.swing.NaiveUserAgent.resolveAndOpenStream(NaiveUserAgent.java:122)
at org.xhtmlrenderer.pdf.ITextUserAgent.getImageResource(ITextUserAgent.java:54)
at org.xhtmlrenderer.pdf.ITextReplacedElementFactory.createReplacedElement(ITextReplacedElementFactory.java:57)
at org.xhtmlrenderer.render.BlockBox.calcDimensions(BlockBox.java:674)
at org.xhtmlrenderer.render.BlockBox.calcDimensions(BlockBox.java:628)
at org.xhtmlrenderer.render.BlockBox.layout(BlockBox.java:763)
at org.xhtmlrenderer.render.BlockBox.layout(BlockBox.java:732)
at org.xhtmlrenderer.layout.InlineBoxing.layoutInlineBlockContent(InlineBoxing.java:393)
at org.xhtmlrenderer.layout.InlineBoxing.layoutContent(InlineBoxing.java:290)
at org.xhtmlrenderer.render.BlockBox.layoutInlineChildren(BlockBox.java:938)
at org.xhtmlrenderer.render.BlockBox.layoutChildren(BlockBox.java:919)
at org.xhtmlrenderer.render.BlockBox.layout(BlockBox.java:802)
at org.xhtmlrenderer.render.BlockBox.layout(BlockBox.java:732)
at org.xhtmlrenderer.layout.LayoutUtil.layoutFloated(LayoutUtil.java:79)
at org.xhtmlrenderer.layout.InlineBoxing.processOutOfFlowContent(InlineBoxing.java:847)
at org.xhtmlrenderer.layout.InlineBoxing.layoutContent(InlineBoxing.java:287)
at org.xhtmlrenderer.render.BlockBox.layoutInlineChildren(BlockBox.java:938)
at org.xhtmlrenderer.render.AnonymousBlockBox.layout(AnonymousBlockBox.java:47)
at org.xhtmlrenderer.layout.BlockBoxing.layoutBlockChild0(BlockBoxing.java:293)
at org.xhtmlrenderer.layout.BlockBoxing.layoutBlockChild(BlockBoxing.java:271)
at org.xhtmlrenderer.layout.BlockBoxing.layoutContent(BlockBoxing.java:89)
at org.xhtmlrenderer.render.BlockBox.layoutChildren(BlockBox.java:922)
at org.xhtmlrenderer.render.BlockBox.layout(BlockBox.java:802)
at org.xhtmlrenderer.render.BlockBox.layout(BlockBox.java:732)
at org.xhtmlrenderer.layout.BlockBoxing.layoutBlockChild0(BlockBoxing.java:293)
at org.xhtmlrenderer.layout.BlockBoxing.layoutBlockChild(BlockBoxing.java:271)
at org.xhtmlrenderer.layout.BlockBoxing.layoutContent(BlockBoxing.java:89)
at org.xhtmlrenderer.render.BlockBox.layoutChildren(BlockBox.java:922)
at org.xhtmlrenderer.render.BlockBox.layout(BlockBox.java:802)
at org.xhtmlrenderer.render.BlockBox.layout(BlockBox.java:732)
at org.xhtmlrenderer.layout.BlockBoxing.layoutBlockChild0(BlockBoxing.java:293)
at org.xhtmlrenderer.layout.BlockBoxing.layoutBlockChild(BlockBoxing.java:271)
at org.xhtmlrenderer.layout.BlockBoxing.layoutContent(BlockBoxing.java:89)
at org.xhtmlrenderer.render.BlockBox.layoutChildren(BlockBox.java:922)
at org.xhtmlrenderer.render.BlockBox.layout(BlockBox.java:802)
at org.xhtmlrenderer.render.BlockBox.layout(BlockBox.java:732)
at org.xhtmlrenderer.layout.BlockBoxing.layoutBlockChild0(BlockBoxing.java:293)
at org.xhtmlrenderer.layout.BlockBoxing.layoutBlockChild(BlockBoxing.java:271)
at org.xhtmlrenderer.layout.BlockBoxing.layoutContent(BlockBoxing.java:89)
at org.xhtmlrenderer.render.BlockBox.layoutChildren(BlockBox.java:922)
at org.xhtmlrenderer.render.BlockBox.layout(BlockBox.java:802)
at org.xhtmlrenderer.render.BlockBox.layout(BlockBox.java:732)
at org.xhtmlrenderer.pdf.ITextRenderer.layout(ITextRenderer.java:209)
at com.company.commons.html2pdf.impl.Html2PdfConverterImpl$DocumentConverter.convert(Html2PdfConverterImpl.java:452)
at com.company.commons.html2pdf.impl.Html2PdfConverterImpl$XMLConverter.run(Html2PdfConverterImpl.java:427)
at java.lang.Thread.run(Thread.java:662)

0 Karma

Arun_Dasetty
Super Champion

Hi,

   We see this is as misinterpretation of how policy wizard is expected to work, we request you to let us if the following information helps to clarify the product behavior:

Select 'These specified objects' section is for non health rule related events which are not covered under HR configuration like code problems etc and also we see the health rule have the "Affects" section already set which will govern the policy.

With that said above we request you update health rule (not policy) in edit view and move "Socketexception" from selected exceptions list and save the changes so that next evaluation results in expected behavior.

Check if that information helps.

Regards,

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

All health rules are default ones. Which rule should I edit? 

"Business Transaction" and "Business Transaction error" HRs dont contain any error selection, but only "Business Transactions". Screenshot attached.

0 Karma

Arun_Dasetty
Super Champion

Hi,

We have two approaches here if we have idea on which BTs wil raise this errors then instead "all BTs" in affects section select the option "specific BTs" for BT error rule, Other way define HR of type "'Errors" as referred in docs:

http://docs.appdynamics.com/display/PRO39/Health+Rules#HealthRules-HeathRuleTypes

In error type policy select "these specified errors" in affects section and do not select "Socket exception" Hope that informaiton helps

Regards,

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hello!


Thank you for an answer, let's continue the investigation.

Currently I dont have any specific HR which checks error, so this comes from default HRs.
Speaking about suggested methods:

1. this doesnt fit, because if i exclude any business transaction i will not be notified of any other kind of error that will appear in exactly this business transaction.
2. this doesnt fit, because if i define new "Errors" HR (i guess here you are speaking about new "Error Rates" HR to be created), anyway notifications from default HRs will not stop

From my perspective, default HRs "Business Transaction" or "Business Transaction error" dont have possibilities to exclude unwanted notifications. So OK, I can disable any of default HRs, and maybe notifications will stop. But this gives nothing, but only business transactions will not be monitored. To avoid misunderstanding, again, I want to deliver what I want to obtain. Some default rules send me unwanted notifications with concrete error. I know name of this error and want to put it in some "exclusion list", but default HRs dont provide such functionality (in my opinion). But as I wrote previously I can find this error in my policy -> these specified objects -> any of these specified objects -> Errors -> then I put unwanted errors on right side "Other Errors". Unfortunately you wrote that this is incorrect approach.

Kindly ask if I can provide more info or screenshots to resolve my issue.

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Any suggestions so far?

0 Karma

Arun_Dasetty
Super Champion

Hi,

We do not see other options apart from one earlier sugggested, We undertood your concenrs on unwanted errors are moved to exluded list in policy but the way the HR works is bit different hence we request you to check/update policy with HR defined such that partciular errors are not in "affects" section of HR define and this HR is added to policy. Hope that make sense to you.

Regards,

Arun

0 Karma
Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...