Idea Details

Spectrum : Simplified CABI, please replace CABI with simplified Reporting-Engine

Last activity 06-13-2019 09:54 AM
e.heinemann's profile image
07-15-2014 04:15 AM

Hi folks,

I have worked with the old Spectrum Reporting-Manager for a long time, - it worked.

For CABI, I fetched my old BOXI-Training-Manauals and tried to start with it.

I have given up and replaced it by my own "Reporting-Engine"

 

I rebuild some reports, like Outage-Report and Alarm-Report with my own PHP-Middleware, - the frontend looks like the old one. *-)

I still use the reporting-DB and SRMDBAPI to fetch the data.

 

Customers are unhappy with BOXI too, - perhaps there are some customers which needed BOXI, But I believe it would be better to integrate the Report-Manager better into oneclick.

 

In my case, now I am able to start my reports via context-menu for Global Collections or Devices.

 

In the last 2 years I have seen many Spectrum-Installations where other partners didn´t install BOXI. All these capabilities of the Reportmanager are lost in these installations.

Why didn´t they install BOXI .. .

 

The SRMDBAPI / reporting_DB is a great resource but we have to simplify the way how we access this database and how we create reports.

 

While I rebuild these reports in PHP, I analysed the SQL-Statements which BOXI fires to the Reporting-DB, - awful, hundreds and thousends SQL-Queries rather than one big query. perhaps I am wrong, but for me it looked like simple statements, not even prepared SQL. After that I was not wondering about the lazy execution of Statements.

 

my Requirements:

- Smaller footprint than BOXI, less hardware. best way would be to combine it on the Oneclickserver via JSP

- Context-based-integration in Oneclick

- No report needs more than 1 minute to present the final result

- CSV / Excel - Rawdata-Export which is usable rather than these over-formatted once

- Reporting of Outages filtered by models/devices of multiple Global Collections, ... in BOXI it is limited to only 1 Global Collection used in a report.

 

Best Regards

Erich Heinemann


Comments

12-18-2016 01:24 PM

Dear Spectrum Community Users,

 

This idea is a delivered with CA Spectrum 10.2 release. As we move Jaspersoft reporting engine also exposed the queries as mentioned above by Kiran. 

 

Thanks,

Nagesh 

08-20-2015 10:06 AM

It would be great to get https://communities.ca.com/ideas/235722267 fixed. If this gets fixed, we could use this subscription service and just populate our own databases with what we want! I'm sure I saw 9.4.3 announced - I need to install it and check to see if this is fixed.

08-04-2015 10:05 PM

We are planning on exposing the schema as well - and giving samples.

As a vendor, we do realize the problems with BOXI - not just Spectrum, but other tools as well complain about it.

While we are working on that, we are trying to figure out ways to easily make the reporting interface "open" enough where we can support it.

 

Again, I intend to touch upon this during our webcast later this month..


Regards,

Kiran Diwakar

08-04-2015 12:09 PM

I know you've marked this as planned, and that's awesome.  I still want to throw my support behind it, though (since I can't vote on it, which seems silly).

 

We get constant complaints about BOXI:

  • "It's slow"
  • "it's cumbersome"
  • "it's horribly complex"
  • "it fails on most event reports"
  • "it's a nightmare to do custom reports"

 

I've got users that are writing SQL queries against the SRM DBAPI directly, because it's faster, easier, and more reliable than using BOXI.  That tells me there's a serious problem here.

 

A lightweight reporting solution that is more reliable and easier to use than BOXI would be enormously useful.  As it stands now, most of our users spend a few hours with BOXI and then write it off as "not worth it".

07-29-2015 06:14 AM

Hello Team,

 

Great feedback! As you would have seen my post on the other thread, we are working very aggressively on this

We are working towards officially exposing the Spectrum Reporting Schema (with potentially some views). We will also supply some sample code to help you pull reports from the reporting platform of your choice

Do stay tuned, we will have something very soon and do look forward to an invite for a Community Webcast in August where I will touch upon this and many other interesting things happening in the Spectrum world..


Please keep your ideas coming. We will be marking this idea as "Planned"


Regards,

Kiran Diwakar

07-27-2015 08:31 AM

Hi Robin,

I´d got an schema for an older SRM-Version some years ago and started digging in the Database. .. the schema was not complete.

Finally I do not have a document and cannot provide any document for it.

I mostly connect to the reporting-db and then dig via „show tables like ‚%alarm%‘\G  …

 

I provided a SQL-Training for some customers where we have build some SQL-Examples around the SRM-DB.

 

 

 

My SRM crashed o lot of times and I prefer a Oracle-DB which collects the Alarms via Notifier. In my Oracle-DB it is only a table of models which are assigned to Global Collections and the Alarm-Table… no events and no GBytes of unused tables. Only enough to create Alarm-Reports.

 

 

 

 

 

 

Am 27.07.2015 um 14:16 schrieb p.robin <communityadmin@communities-mail.ca.com<mailto:communityadmin@communities-mail.ca.com>>:

 

CA Communities<https://communities.ca.com/?et=watches.email.idea_comment>

 

Spectrum : Simplified CABI, please replace CABI with simplified Reporting-Engine

new comment by p.robin<https://communities.ca.com/people/p.robin> View all comments on this idea<https://communities.ca.com/ideas/235713950#comment-233916307>

07-27-2015 08:15 AM

Erich

I have been trying to get a schema for the SRMdbs, events/Alarms dbs for example.

Did you create your own or get it somewhere?  Would like to be able to extract the data for manipulation elsewhere as the reports I try to run fail about 30-40% of the time and for some I have to run a mysql query to get the report.

Are you willing to share the db info you are using?

07-14-2015 09:22 AM

Hi Diego,

I have found tools/javascript sources to convert a DIV into CANVAS and then into PDF....

 

I will send that to you ... basically jsPDF

07-13-2015 10:06 AM

Example of an simplified formular/report ....

This is not a "Report" but something on the way to a report.

basically, it uses JSP and Oneclick-Web as the platform.

List of alarms included into Oneclick which uses the SRM as the Database.

 

I have build an JSP which only executes an SQL-Query which is stored in a file....

CSS was delivered by Bootstrap.JS

 

 

Very simple Formular to edit the Report-Settings and Definition.

Mostly we need Reports for multiple Global Collections!

07-13-2015 09:30 AM

Gracias Elio, es desarrollo propio con php, mysql, y d3js. Hace poco subi en linkedin una captura de como quedo terminado el reporte.

saludos y buena semana !

07-13-2015 09:15 AM

Bien Diego! Qué estás usando para hacer esos reportes?

Well done Diego! What are you using to show those reports?

06-29-2015 05:02 PM

Hi, I do not agree with that requirement.

We are requesting a product, not an API.

We would like to get a ready to go reporting, from one mouseclick in Oneclick to a final HTML oder PDF-Report in 4 or 5 Clicks.

.. not Lego *-)

Specially for the Mid-Market, it is a problem to work with BOXI. .. to much switches and options.

And for the Big market, we have too many problems with SRM, which is unavailable to often ... Bucketfiles etc.

 

If it doesn´t scale, then focus to something - or replace it with something which scales.

 

I have some customers, - and my own installation where SRM fails monthly and BOXI faild sometimes too.

I want to use a product! - not my own script-Reporting-Engine.

 

... my background .. more than 10 Years Oracle-DB-Development, Reporting etc..

If we cold kick out BOXI and get a stable Database with direct SQL-Access, that would be fine, but the customers need a simple reporting to create PDFs.

In my mind, BOXI should be an option where You have to pay extra. .. perhaps Spectrum-Licenses would get cheaper without Boxi *-)

 

Most of my customers do not use PM. They only use Spectrum. An integration wouldn´t help.

 

Regards

Erich

06-29-2015 11:57 AM

It would be nice if they could use the OpenAPI stuff that was introduced in CA PM...  not sure how hard it would be to port that over for Spectrum to use without having it integrated with CA PM.  Maybe they can comment here.

06-27-2015 01:45 AM

Agree. Please look into a more flexible reporting engine.

06-26-2015 07:17 PM

Hi Diego,

really cool Your solution!!

 

I am trying to build something only based on alarms...

 

a Liveline, … known by other tools would be cool too.

 

 

.. its only a HTML/Javascript/SVG-Dummy.

 

When You move over the Liveline, the content of every alarm ( .. colored rectangle ) is displayed… not ready to go yet

 

 

Am 27.06.2015 um 00:54 schrieb d.pereyra <communityadmin@communities-mail.ca.com<mailto:communityadmin@communities-mail.ca.com>>:

 

CA Communities<https://communities.ca.com/?et=watches.email.idea_comment>

 

Spectrum : Simplified CABI, please replace CABI with simplified Reporting-Engine

new comment by d.pereyra<https://communities.ca.com/people/d.pereyra> View all comments on this idea<https://communities.ca.com/ideas/235713950#comment-233914317>

06-26-2015 06:53 PM

The most common report that my clients have requested is one of availability (individual or groups) and including alarms, events, bandwidth, Netflows, logs from other tools. To generate a Big report.

 

 

I'm working on it;)

06-26-2015 03:49 PM

My simple version of CABI

its not photoshop, im playing a little with php/mysql.

Hope we get many more votes!

06-22-2015 01:36 PM

Since it's still marked as new, I wouldn't count on it.  I think we need to find a few more votes, especially as this seems like an enhancement that would be a lot of work and is probably not one that will be undertaken lightly.

06-20-2015 02:08 AM

I think this is under review by Spectrum product management for now. Let's wait for some good news.

06-18-2015 05:06 PM

We use Jaspersoft in some of our other CA tools (VAIM for example) for reporting.  It's pretty lightweight and might be interesting to investigate for at least some basic reporting. 

06-18-2015 04:43 PM

I think this is a great idea and would make a great addition to the Spectrum suite.

While CABI meets the demand for most of our customers, it does make sense to have a lighter reporting solution!

06-18-2015 02:51 PM

I read that CABI from Spectrum 10.0 needs now 16GByte of Ram exclusive... to provide an alternative is a must.

Specially for midrange and small customers there is a need to keep the system on one server .. Spectrum, Oneclick and reporting on the same Server.

 

I believe, most of my customers need only some standard-reports:

- Alarms of a Topology-Structure

- Alarms of selected Global Collections

- Alarms of a Device

- Outages of selected Global Collections

- Devices of selected Global Collections

- Interfaces/Ports which are inactive since n days

 

- Formats:  all in HTML, simple CSV and PDF

- On Demand and Scheduled/Email

06-11-2015 10:24 AM

Hi,

My webbased-Frontend accepts URLs which contain the names of some Global-Collections in the URL.

.. .http://myReportingServer.mylab.de/custom/spectrumreport/availabilityreport.php?timeframe=last%20month&GC=MyGlobalCollectionForReporting

 

In the custom-menu-config.xml-File at /Specroot/custom/console/config I inserted a new menuentry to join this URL.

 

...that´s far away from the current CABI/Spectrum - SidebySide-Solution, but the output (PDF or HTML) looks really like the old SRM-Reports.

Actually I have to support 2 different versions. .. one version for alarms, which fetches the alarms out of my custom Oracle-Database which works fine since years. .

the second version works with the SRM / SRMDBAPI as a backend .. but this version is mostly not available because of Bucketfiles.

 

I tested the ElasticSearch/Kibana-Soution too. Kibana looks great but I was not able to create requested reports / PDF.

 

At DevXChange 2015 in London, I heard from many people who are using Splunk to provide a reporting.

 

Actually I try to implement the reporting directly into the Reporting for a Ticket-System .. to give these problems away to others.

 

If I get the job to start a new SRM, I would do:

- it with Oracle APEX .. the most stable database

- Fetch Devices / Models of Interest via REST

- Push Alarms into the System via Notifier  .. to get the Notifydata into the Database too. ...  I like it to see that people got notified and they try to tell my that they were not notified.

- Events ... I do not need them for reporting.

 

I believe, this database-structure could work a long time .. small because of less "Event-Table"

06-11-2015 10:04 AM

We don't use GC's a lot. I've developed perl/SQL type query builder which dynamically creates XML for use with REST calls. It is also heavily integrated with internal systems, e.g. naming standard of our devices, etc.

 

I'm busy looking at generating a web front-end for it and hosting it on the existing tomcat server. We also have the ability to export it in various formats including csv, html, grid (ASCII table like SQL queries) or kvp (Key-Value-Pair).

06-11-2015 09:47 AM

"In my case, now I am able to start my reports via context-menu for Global Collections or Devices."

 

How are you doing this?

06-11-2015 09:21 AM

I agree, CABI is to big and complex to do just simple reports.  I rebuild some reports using kibana, but not the same, i miss many events to do a perfect availability report.   And some customers are beginning to distrust spectrum data because CABI have problems to show it.

 

Diego

06-11-2015 07:31 AM

We also have our own reporting and don't use CABI. I would be happy if they made all the info for alarms and events available and not encrypt it. I think in most cases, many will be happy with the default reporting, but I've always thought that CABI was over-engineered and slow (overengineered in terms of what you need to install and what it actually does in the end!).