I’m new to LogicMonitor and am looking to see if there’s a way to get a table of call history. We have CUCM sending over the CDR data and it looks like some of it is being pulled in, but I don’t see where I could generate a table with who made a call, who received it, the call duration, and timestamp at minimum.

I believe this data is obtained from files, correct? Our PS team has developed custom logicmodules to obtain this info but I do not believe it is available OOB.

Are you sending CDRs in as Netflow or LM Logs or some other method? The way it’s coming in determines how you can use it.

Yes, CUCM is sending the files via FTP to a directory specified by cucm.path on the resource and I am seeing some CDR datasources populating. I’m all ears if there is a better way to do this though we generally avoid using Netflow

The easiest way to view a simple table that displays call data, as you’ve outlined above, is to create a datasource that ingests all individual call records and consolidates them into one or more CSVs. If you have LM Logs, you could ingest the CUCM files and create pipelines that look for the data that you want displayed.

Are you licensed for LM Logs? If so, I’d suggest ingesting them that way (there are lots of ways to skin that cat). Once you do, you can use parse methods (or maybe a Log Source, but I think they’re beta) to extract the data into the fields you want. If the files are local to the collector, you can use fluentd to pick them up and send them to LM (why doesn’t the collector have a local LM Logs option @Kellena? You have to use fluentd to get logs from the collector’s disk into LM Logs? Is that right?). Alternatively you can setup a standalone fluentd and use it to gather the logs from your CUCM server(s) and forward them to LM Logs. That would eliminate the custom FTP operation and take the collector out of the picture altogether.If you want to see them in the custom DS, you’ll probably have to build that yourself or get PS to do it if they built the modules originally.

Using CUCM CDR Data for Reviewing Call History

Anonymous
2 years ago
Yeah, that’s why i was thinking the ability that the otel collector has to push local logs into LM logs should be built into the standard collector. If there are no log sources for it, it wouldn’t take any additional resources from the collector.
Kellena
LM Champion
2 years ago
@Stuart Weenig - Yes, you can install an OTel collector on the same box as a regular collector. However, that box will then need to share its resources with both collectors. Depending on the log streaming requirements, this could impact the performance and capabilities of the regular collector.
pgordon
Advisor
2 years ago
@Stuart Weenig Probably, I’ll have to look more into it
Anonymous
2 years ago
@Stuart Weenig - FluentD is the most widely used option but there are OTel collector and LogStash options as well, depending on the use case. Search for “Log Files on Disk” on this page.
Can you install an OTel collector on the same box as a regular collector?
pgordon
Advisor
2 years ago
Awesome, that is where I’ll direct my attention then. Thank you both!
Kellena
LM Champion
2 years ago
@pgordon - LM Logs would be your best bet, followed by a custom datasource that ingests and consolidates data and spits it all out to one or more CSVs. LM Logs is not OOB and would need to be purchased before it can be used. You can always ask to set up a POV trial period first, to see if it meets your needs.
pgordon
Advisor
2 years ago
@Kellena our VOIP person shows me that CDR records are ingested in other third party reporting tools every few minutes, ours is currently set to ingest files every two minutes
Kellena
LM Champion
2 years ago
@Stuart Weenig - FluentD is the most widely used option but there are OTel collector and LogStash options as well, depending on the use case. Search for “Log Files on Disk” on this page.
@pgordon - How often do you need these files queried? PropertySources only run automatically once per day.
Anonymous
2 years ago
Yes, that would be separate. You can technically set anything. The key is what might pick those properties up and use them to activate datasources that will result in data.
pgordon
Advisor
2 years ago
I’ll look into the LM Logs then. I did also just find there are CUCM API properties that can be set. Is that completely separate from the Logs?

Forum Discussion

Using CUCM CDR Data for Reviewing Call History

Related Content

Collectors Capacity review

Dashboard Filtering Using Instance Properties

History of LogicModule version changes

LM Community - 2023 in Review

Entering enable mode using JSch

Recent Discussions

How do you monitor Running Services on Linux boxes?

Event Sources SNMP and Windows collectors?

Can anyone help modify this Datasource to be able to use any port?

⚠️COMMUNITY OUTAGE⚠️ Posts and replies fail only titles visible

Can Logic Monitor Pull Routing tables