Splunk AppDynamics

Health rule Timeframe

Viji_Radhakrish
Explorer

Hi,

When creating a health rule, use data from last ----- mins (1 to 120 mins), Is this the rolling time window ? Like every time it calculates the last X minutes ? 

Is there any way to choose the static timeframe ? Means, Choose the first 5 mins of data for evaluation, the next time choose the next 5 mins of time for evaluation. 

Thanks, 

Viji

Labels (3)
Tags (1)
0 Karma
1 Solution

iamryan
Community Manager
Community Manager

Hi @Viji.Radhakrishnan,

I was following up with the SME. I got a response. 

This time frame is always a rolling time frame.

View solution in original post

0 Karma

iamryan
Community Manager
Community Manager

Hi @Viji.Radhakrishnan,

I was following up with the SME. I got a response. 

This time frame is always a rolling time frame.

0 Karma

iamryan
Community Manager
Community Manager

Hi @Viji.Radhakrishnan,

I heard back! It's a rolling time frame. The 1 - 120 min value is the input to "Use data from last ___ mins" and this window measures the time from the health rule evaluation time.

Hope this helps.

Viji_Radhakrish
Explorer

Thanks for your reply Ryan. Can you please check if I can choose the static timeframe ? For example, Take the first 15 mins in the hour for first evaluation and the next 15 mins for the second evaluation. Is this possible ? 

The requirement is to monitor the response time and report it based on timeframe. 

0 Karma

Viji_Radhakrish
Explorer

@Ryan.Paredez Did you get chance to look at my query ? 

0 Karma

iamryan
Community Manager
Community Manager

Hi @Viji.Radhakrishnan,

I'm looking into this for you with the Docs team. I will report back when I get some clarification. 

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...