Dashboards & Visualizations

Create dashboard and relatorio

fiveitsplunk
Explorer

Hello,

I would like to create 03 reports, but I have difficulties.
What happens, I need to create:
- Calls that are not answered by extension;
- Calls that are answered by extension successfully;

  • Calls made by extension successfully;
  • Unsuccessful extension calls;

But I notice that I can't filter by time, because there are links
  00:00:00, so I can't create a report using just the "status" of the call because it usually has "normal clean call".

It is possible to make a query in the way that, define that the calls "received" by time, and consider that with the value 00:00:00 s;

Att,
Richard

0 Karma

richgalloway
SplunkTrust
SplunkTrust

Perhaps this will get you started.

index=foo duration="00:00:00" cause_description=* | table _time cause_description
---
If this reply helps you, Karma would be appreciated.
0 Karma

fiveitsplunk
Explorer

I could not resolve with this condition

richgalloway
SplunkTrust
SplunkTrust

What do you get? Did you make any necessary changes for your environment (correct index and field names) ?

---
If this reply helps you, Karma would be appreciated.
0 Karma

fiveitsplunk
Explorer

What I'd like to create is a report where you filter:
Call that came in and was not answered by anyone, in this case those that have the time value 00:00:00;alt text

0 Karma

richgalloway
SplunkTrust
SplunkTrust

It would help if you shared some sample events, sanitized as necessary.

---
If this reply helps you, Karma would be appreciated.
0 Karma

fiveitsplunk
Explorer

It is possible to create a query, containing only calls with "zero duration" and the cause of the call.
"cause_description"?

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