Discussion Feed

Anytime:) If I understand your request correctly, I believe you could use one getter chain. Can concatenate it together, I haven't tested it but should work as below. replaceAll(Running,1). replaceAll(Stopped,2). replaceAll(Suspended,3) That way it stays one metric and the value will change as the state changes. Otherwise you a create seperate metric chains per status. Ciao ... View more

Hi Blain   You can set the smapling frequency lower by changing the sampling frequency in the ServerMonitoring.yml file.    https://docs.appdynamics.com/21.5/en/infrastructure-visibility/server-visibility/machine-agent-settings-for-server-visibility   Not sure if you can make it less than 1minute, or let me say it this way the backend controller will only store a certain amount of samples per minute.   If I can remember correctly it will store 1 metric per minute, so for your use case that should be fine. If you want to reduce the sampling to less than 1 minute you would have to check with AppDynamics what the Controller backend will support   Ciao ... View more

Thanks Jeremy   Completely misunderstood the initial request:)   Can you please provide more info on the following   I've create a custom metric which populates the events tab in database visibility with data from a query Can you advise what you did here, created a custom metrics query? This in itself will not create events in the events tab, so I assume you created a health rule on the returned values. Which then populated the events tab correct?   , is it possible to create an action that matches on these to send them via email, http request etc? Yes, since you created the health rule, all you have to do, is create an action, e.g send email to whomever. And the create a policy, which you then select the health rules , and the action that needs to happen when they are triggered ... View more

Hi Jeremy   The Type, needs to be set to the customevent type that you set for the custom events you are sending to AppDynamics   e.g if you set the  customeventtype=mydbevents, you need to set that as the value for type   https://docs.appdynamics.com/21.5/en/extend-appdynamics/appdynamics-apis/alert-and-respond-api/events-and-action-suppression-api   If you look at the above documentation, you can set additional  propertynames:propertyvalues, that you can use in the Policies, which you can't see in the UI, however they are used in the Health rule policies to be used to filter different sub types of Events.   Simple use case, you are sending both Oracle & MSSQL Events to AppDynamics You can set the  following in your script or tool that is sending the events to AppD. customeventtype:mydbevents   Then set the following values depending on which DB Type the event is for(propertynames:propertyvalues) dbtype:MSSQL or dbtype:ORACLE   That way you can create separate policies for MSSQL & Oracle by using the parameter values   I hope I am making sense:) ... View more

Hi Jeremy   If the custom events are being populated, you can just create a new policy and select the Custom Events from the options   Which you can then add actions to send email etc. once those events are picked up     ... View more