Use this article to understand what Yarken Insights does, how teams use it, and how anomaly detection supports proactive financial monitoring.
Detect and manage unusual spend or usage patterns
Insights helps teams detect, review, investigate, and resolve unusual movement across spend and usage data.
Instead of relying only on dashboards or manual reviews, Yarken can monitor selected metrics automatically through Insight Rules. When spend or usage falls outside the expected range, Yarken creates an Insight for review.
Each Insight gives teams the context needed to understand what happened, why it was flagged, and what action may be needed next.
What you can do
-
Monitor spend and usage data for unusual patterns.
-
Detect spend spikes, usage drops, budget overruns, forecast deviations, tagging issues, new vendor activity, and structural changes.
-
Configure Insight Rules for specific metrics, data sources, dimensions, filters, and thresholds.
-
Use different detection methods based on how the data behaves.
-
Notify the right users or groups when rule conditions are met.
-
Review generated Insights in one workspace.
-
Acknowledge Insights once investigation begins.
-
Resolve Insights after the issue is explained or corrected.
-
Reopen Insights when an issue reappears or needs further review.
Insight Rules
Insights are generated from Insight Rules.
Each rule defines what Yarken should monitor, which data source and metric to use, how anomalies should be detected, who should be notified, and how often the rule should run.
Rules can monitor spend and usage data across supported data sources such as the Spend Cube and Cloud Cube.
Once a rule is enabled, it runs automatically on the selected schedule. If behavior falls outside the expected range, Yarken creates an Insight and adds it to the Insights page.
Anomaly detection methods
Insights supports multiple anomaly detection methods.
-
Z Score is used for stable datasets where sudden spikes or drops need to be detected.
-
Moving Average is used for data with short term fluctuations and clearer trend movement.
-
Prophet is used for data with stronger seasonality, such as recurring billing or usage patterns.
-
CUSUM is used for detecting sustained changes in baseline behavior, such as a new contract, service launch, or structural shift in spend.
This gives teams more control over how unusual movement is detected, instead of relying only on simple threshold alerts.
Insight details
Each Insight includes context to support investigation.
Users can review the type of Insight, affected dimension, severity, current status, generation time, trend visualization, baseline comparison, threshold range, detection method, confidence score, impacted spend amount, rule details, timeline, and suggested next steps.
This helps teams understand not only that something changed, but why Yarken flagged it and what should happen next.
Insight lifecycle
Each Insight moves through a defined lifecycle.
-
New means the Insight has been created and needs review.
-
Acknowledged means a user has started investigating it.
-
Resolved means the issue has been explained or corrected.
-
Reopened means the issue has returned or the previous resolution needs further review.
This lifecycle helps teams manage anomalies as work items, not just notifications.
How teams use Insights
Finance teams use Insights to detect unexpected spend movement and protect budget discipline.
FinOps teams use Insights to monitor cloud spend, usage spikes, tagging issues, and optimization signals.
IT teams use Insights to detect unusual cost or usage patterns that may indicate operational change.
Business owners use Insights to understand when spend or usage in their area needs attention.
What makes it different
Insights is not just alerting.
Alerts notify users that something happened. Insights gives teams a workspace to understand, investigate, track, and resolve what happened.
Because Insights works against Yarken's spend and usage data, it stays connected to the same model used for analytics, planning, FinOps, chargeback, and governance.
When to use Insights
Use Insights when teams need proactive monitoring for cost, usage, variance, budget, forecast, vendor, tagging, or structural changes.
Use Insight Rules when a metric or pattern should be checked regularly.
Use the Insights page when teams need to review, acknowledge, investigate, resolve, or reopen detected anomalies.
For detailed step by step instructions on creating Insight Rules, configuring detection methods, setting notifications, reviewing Insights, and resolving anomalies, refer to the relevant user guides.
Next step
Related articles
Ask Yarken: AI-Powered Financial Intelligence