Messages

1

QueueMetrics installation / Install Queuemetrics on CentOS 7, systemd issue

« on: October 22, 2020, 17:40:21 »

Hello!

I installed Queuemetrics on CentOS 7 and notice that command "systemctl status queuemetrics" show status active(exited) It is said that queuemetrics doesn't have native unit for systemd service. But I install it from loway repo.

Code: [Select]

[sudo] password for a.klimenko:
● queuemetrics.service - SYSV: Starts/stops QueueMetrics' internal Tomcat
   Loaded: loaded (/etc/rc.d/init.d/queuemetrics; bad; vendor preset: disabled)
   Active: [b]active (exited)[/b] since Thu 2020-10-22 10:40:14 MSK; 7h ago
     Docs: man:systemd-sysv-generator(8)
  Process: 5998 ExecStop=/etc/rc.d/init.d/queuemetrics stop (code=exited, status=0/SUCCESS)
  Process: 6062 ExecStart=/etc/rc.d/init.d/queuemetrics start (code=exited, status=0/SUCCESS)

Oct 22 10:40:12 qm-01.tps.local systemd[1]: Starting SYSV: Starts/stops QueueMetrics' internal Tomcat...
Oct 22 10:40:14 qm-01.tps.local queuemetrics[6062]: Starting qm-tomcat6 (via systemctl):  [  OK  ]
Oct 22 10:40:14 qm-01.tps.local systemd[1]: Started SYSV: Starts/stops QueueMetrics' internal Tomcat.

2

Running QueueMetrics / Re: Running report for agent with two queue keys

« on: July 24, 2017, 11:38:37 »

This is a new machine.

Previous version was 16.09.

3

Running QueueMetrics / Running report for agent with two queue keys

« on: July 24, 2017, 09:19:31 »

Hi!

I have new installation of QueueMetrics 17.06: "Software release:   Loway QueueMetrics - 17.06.1 B: 397 - 2017.06.20-10:10"

Supervisors don't have to pick agents in field "Filtered for agent:" that have two or more queuekey in key field. Agents that have one queuekey in key field there are in a list of "Filtered for agent:" in a report page.

Previous version of QueueMetrics doesn't have that issue.