AppD Archive

Service Availability issues

CommunityUser
Splunk Employee
Splunk Employee

Hello.  I am working on evaluating Service Availability monitoring to monitor the health of internal/external websites and am running into some potential road blocks.

1. Support tells me there is no way to create an xml or some other file to import configurations.  I would have over 3000 URLs that we monitor today that would be migrated...If we have to manually enter these using the GUI, that would be painstaking.

2. It seems like the GUI doesn't refresh properly.  When adding/deleting a configuration, it looks like I need to close and relaunch the appdynamics site to get them to show up in the Service Availability views.  Is this a known issue? Or is this something on my end?

3. Validators don't seem to work properly.  I attempted using Status Code <= 300 for a page that was returning a 200, and got "

validation result - Failed to validate: Response status code is not between 300 and 300 inclusive."  If I do = 200, it returns successfully.  I also tried with content that I know exists on the page, and it looks like the response truncates or something.  Is there a limit to the size of the response?  

 

4. Is there anyway to set up any kind of High Availability within the configurations?  It seems since we have to select an agent to perform the GET/POST, you are locked into a single agent.  If that server agent crashes, we lose our availability monitoring?

 

Thanks in advance for any reponses.

 

Jon

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

After some discussions with support (which are ongoing) I've got a few answers.

1. Support tells me there is no way to create an xml or some other file to import configurations.  I would have over 3000 URLs that we monitor today that would be migrated...If we have to manually enter these using the GUI, that would be painstaking.

- still hoping for a solution here.  

2. It seems like the GUI doesn't refresh properly.  When adding/deleting a configuration, it looks like I need to close and relaunch the appdynamics site to get them to show up in the Service Availability views.  Is this a known issue? Or is this something on my end?

-this seems to happen for everyone at my company.  The general consensus is to open AppD in a different browser until it shows similar issues, then move back to the other browser.  The thought is that the browsers are caching data somehow.

3. Validators don't seem to work properly.  I attempted using Status Code <= 300 for a page that was returning a 200, and got "

validation result - Failed to validate: Response status code is not between 300 and 300 inclusive."  If I do = 200, it returns successfully.  I also tried with content that I know exists on the page, and it looks like the response truncates or something.  Is there a limit to the size of the response?  

-This is fixed in the latest version (4.2.12.1)

4. Is there anyway to set up any kind of High Availability within the configurations?  It seems since we have to select an agent to perform the GET/POST, you are locked into a single agent.  If that server agent crashes, we lose our availability monitoring?

-Still waiting for an answer on this one too.

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

For the response content (question 3), I found the setting for Max Response size, but it looks like its limited to 5000 bytes?  I tried increasing and received an error.  Is there any way to increase that max?

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 ...