Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
aj0031724
Partner - Creator
Partner - Creator

STRAIGHT TABLE DATE CAN BE MAPPED WITH 0-23 hours and then do the logic based on HOUR filter.?

  DEAR TEAM,

IS THERE ANY WAY BY WHICH DATE CAN BE MAPPED WITH 0-23 hours and then do the logic based on HOUR filter.?

CAN YOU PLEASE SUGGEST ?

INPUT FILE:

AlarmDateAlarm IDTechnologyVendorRNCNodeBCellNE LevelRaised TimeDropped TimeSeverity
17-02-20171483992308686UMTSZTER1S1 NODEB17-02-2017 15:1617-02-2017 18:16Critical
17-02-20171483992308685UMTSZTER2S1 NODEB17-02-2017 15:1617-02-2017 18:16Critical
17-02-20171483992308684UMTSZTER3S1 NODEB17-02-2017 15:16 Critical
17-02-20171483992308683UMTSZTER4S1EKOL0000JGPA3CELL17-02-2017 15:0817-02-2017 18:08Critical
17-02-20171483992308682UMTSZTER5S1EKOL0000JGPA2CELL17-02-2017 15:0817-02-2017 18:08Critical
17-02-20171483992308680UMTSZTER6S1EKOL0000JGPA1CELL17-02-2017 15:08 Critical
17-02-20171483992308679UMTSZTER7S1EKOL0000BOND3CELL17-02-2017 14:54 Critical
17-02-20171483992308678UMTSZTER8S1EKOL0000BOND2CELL17-02-2017 14:54 Critical
17-02-20171483992308673UMTSZTER9S1 NODEB17-02-2017 14:45 Critical
17-02-20171483992308672UMTSZTER10S1 NODEB17-02-2017 10:38 Critical
17-02-20171483992303238UMTSZTER11S1 NODEB17-02-2017 15:1317-02-2017 18:13Major
17-02-20171483992267154UMTSZTER12S1 NODEB17-02-2017 15:1417-02-2017 18:14Major
17-02-20171483992267153UMTSZTER13S1 NODEB17-02-2017 15:14 Minor
17-02-20171483992267147UMTSZTER14S1 NODEB17-02-2017 15:14 Major
17-02-20171483992267144UMTSZTER15S1 NODEB17-02-2017 15:14 Minor
17-02-20171483992267143UMTSZTER16S1 NODEB17-02-2017 15:13 Major
17-02-20171483992267142UMTSZTER17S1 NODEB17-02-2017 15:13 Minor
17-02-20171483992267134UMTSZTER18S1 NODEB17-02-2017 15:12 Minor
17-02-20171483992267133UMTSZTER19S1 NODEB17-02-2017 15:12 Minor
17-02-20171483992267132UMTSZTER20S1 NODEB17-02-2017 15:12 Minor
17-02-20171483992308686UMTSZTER21S1 NODEB17-02-2017 15:1617-02-2017 18:16Critical
17-02-20171483992308685UMTSZTER22S1 NODEB17-02-2017 15:1617-02-2017 18:16Critical
17-02-20171483992308684UMTSZTER23S1 NODEB17-02-2017 15:16 Critical
17-02-20171483992308683UMTSZTER24S1EKOL0000JGPA3CELL17-02-2017 15:0817-02-2017 18:08Critical
17-02-20171483992308682UMTSZTER25S1EKOL0000JGPA2CELL17-02-2017 15:0817-02-2017 18:08Critical
17-02-20171483992308680UMTSZTER26S1EKOL0000JGPA1CELL17-02-2017 15:0817-02-2017 21:08Critical
17-02-20171483992308679UMTSZTER27S1EKOL0000BOND3CELL17-02-2017 14:5417-02-2017 20:54Critical
17-02-20171483992308678UMTSZTER28S1EKOL0000BOND2CELL17-02-2017 14:54 Critical
17-02-20171483992308673UMTSZTER29S1 NODEB17-02-2017 14:45 Critical
17-02-20171483992308672UMTSZTER30S1 NODEB17-02-2017 10:38 Critical
17-02-20171483992303238UMTSZTER31S1 NODEB17-02-2017 15:1317-02-2017 18:13Major
17-02-20171483992267154UMTSZTER32S1 NODEB17-02-2017 15:1417-02-2017 18:14Major
17-02-20171483992267153UMTSZTER33S1 NODEB17-02-2017 15:1417-02-2017 21:14Minor
17-02-20171483992267147UMTSZTER34S1 NODEB17-02-2017 15:1417-02-2017 21:14Major
17-02-20171483992267144UMTSZTER35S1 NODEB17-02-2017 15:14 Minor
17-02-20171483992267143UMTSZTER36S1 NODEB17-02-2017 15:13 Major
17-02-20171483992267142UMTSZTER37S1 NODEB17-02-2017 15:13 Minor
17-02-20171483992267134UMTSZTER38S1 NODEB17-02-2017 15:12 Minor
17-02-20171483992267133UMTSZTER39S1 NODEB17-02-2017 15:12 Minor
17-02-20171483992267132UMTSZTER40S1 NODEB17-02-2017 15:12 Minor

Based on above table structure there is requirement to get COUNT(ALARMID) on "Hour basis"" and also DAILY basis.

So output table requirement is :

   

ResolutionDateHourCRITICALMAJORMINORWARNING
HOURLY17-02-201700000
HOURLY17-02-201710000
HOURLY17-02-201720000
HOURLY17-02-201730000
HOURLY17-02-201740000
HOURLY17-02-201750000
HOURLY17-02-201760000
HOURLY17-02-201770000
HOURLY17-02-201780000
HOURLY17-02-201790000
HOURLY17-02-2017101000
HOURLY17-02-2017111000
HOURLY17-02-2017121000
HOURLY17-02-2017131000
HOURLY17-02-2017144000
HOURLY17-02-20171510460
HOURLY17-02-20171610460
HOURLY17-02-20171710460
HOURLY17-02-20171810460
HOURLY17-02-2017196260
HOURLY17-02-2017206260
HOURLY17-02-2017216260
HOURLY17-02-2017224150
HOURLY17-02-2017234150

and :

   

ResolutionDateSeverityCount
DAILY17-02-2017CRITICAL10
DAILY17-02-2017MAJOR4
DAILY17-02-2017MINOR6
DAILY

17-02-2017

WARNING0
15 Replies
avinashelite

Share the sample data and the app ...let me check and get back to you

aj0031724
Partner - Creator
Partner - Creator
Author

Dear Avinash,

Many thanks.

Please see the below  data in excel  and the require output also.

Requesting you to please help me in order to  get the desired output.

Requirements ->Count of  distictnt alarms  per hour till it gets dropped.(Output table built accordingly)

avinashelite

check this ..

Hope this helps you

aj0031724
Partner - Creator
Partner - Creator
Author

Dear Avinash,

I have checked the TCOM.qvw ,HERE THE COUNT as per hourly break up is completely different to excel  output.

For example Hour 3 is shoing  count(4) whereas there is no Count shpiung on hour 3 a sper excel output.

Same goes for different hours.

Can you please re-check the output of TCOM and suggest?

avinashelite

Its according to you data set check the input sheet you have given

If we calculate the hours , for AlarmID 1,2, 4 and 5 Critical we have 4 count that is showing in the output of our file

You show load the full data set and check

aj0031724
Partner - Creator
Partner - Creator
Author

Dear Avinash,

Many thanks for your help on this so far.

If I we SELECT Hour  =3 ,then count should be Zero because there was no AlarmID exists which was raised on or before 3 am .

The first alarmed that was raised as per Input Structure it is 10:30 AM (Alrmid=10).

So previuos to Hour 10 all count shoud be Zero .

Now next Hour=11 SAY ,HERE Alarmid=10 is still not dropeed so Count of Alarmid=1 for Hour =11 AS PER EXCEL OUTPUT.

sAME GOES FOR all hours calcualtions.

Please suggest.