Re: Logging the total number of fragments that make up a message
Alexander Malysh <[email protected]> Tue, 22 Oct 2024 10:09:41 +0200
| Newsgroups | gmane.comp.mobile.kannel.user |
|---|---|
| Message-ID | <b4135b81-8307-44d6-960a-84c1666b5ef7@Spark> |
--67175dca_66334873_d041 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, ohh sorry, this is not in official Kannel version. I will try to merge it= next week. Regards, Alexander Malysh Am 9. Okt. 2024, 11:29 +0200 schrieb =D0=94=D0=B5=D0=BD=D0=B8=D1=81 =D0=94= =D0=B0=D0=B2=D1=8B=D0=B4=D0=BE=D0=B2 <dynax60=40gmail.com>: > Hi Alexander=21 > > How exactly can this be done=3F It's not very clear to me. As far as I > understand, the MO concatenated messages are logged as one long > message only after receiving all parts and stitching them together, > there's no flag in the access-log-format that shows the total number > of parts. Maybe I wrong and missing something. > > -- > Regards, > Denis > > On Wed, Oct 9, 2024 at 10:50=E2=80=AFAM Alexander Malysh <amalysh=40kan= nel.org> wrote: > > > > Hi, > > > > you can use custom access log format and log parts amount. After that= just parse the log line and put into Elastic. > > > > Regards, Alexander Malysh > > Am 24. Sept. 2024, 11:38 +0200 schrieb =D0=94=D0=B5=D0=BD=D0=B8=D1=81= =D0=94=D0=B0=D0=B2=D1=8B=D0=B4=D0=BE=D0=B2 <dynax60=40gmail.com>: > > > > Hi all, > > > > Along with the message, it is necessary to register in the access=5Fl= og the total number of its parts (it doesn't matter, it's MO or MT), sinc= e each part of such a composite message is charged by the upstream SMSC o= perator. I will collect such information in Elasticsearch for subsequent = analysis after the billing period. > > > > How do you solve this problem=3F If I am not mistaken, MO messages co= ming from the SMS service will always have a =22=5Budh:0:=5D=22 entry in = the log file, since, apparently, Kannel deletes information in the SMS.ud= hdata format after assembling the message. > > > > -- > > Regards, > > Denis --67175dca_66334873_d041 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline <html xmlns=3D=22http://www.w3.org/1999/xhtml=22> <head> <title></title> </head> <body> <div name=3D=22messageBodySection=22> <div dir=3D=22auto=22>Hi,<br /> <br /> ohh sorry, this is not in official Kannel version. I will try to merge it= next week.</div> </div> <div name=3D=22messageSignatureSection=22><br /> <div class=3D=22match=46ont=22>Regards, Alexander Malysh</div> </div> <div name=3D=22messageReplySection=22>Am 9. Okt. 2024, 11:29 +0200 schrie= b =D0=94=D0=B5=D0=BD=D0=B8=D1=81 =D0=94=D0=B0=D0=B2=D1=8B=D0=B4=D0=BE=D0=B2= <dynax60=40gmail.com>:<br /> <blockquote type=3D=22cite=22 style=3D=22border-left-color: grey; border-= left-width: thin; border-left-style: solid; margin: 5px 5px;padding-left:= 10px;=22>Hi Alexander=21<br /> <br /> How exactly can this be done=3F It's not very clear to me. As far as I<br= /> understand, the MO concatenated messages are logged as one long<br /> message only after receiving all parts and stitching them together,<br />= there's no flag in the access-log-format that shows the total number<br /= > of parts. Maybe I wrong and missing something.<br /> <br /> --<br /> Regards,<br /> Denis<br /> <br /> On Wed, Oct 9, 2024 at 10:50=E2=80=AFAM Alexander Malysh <amalysh=40ka= nnel.org> wrote:<br /> <blockquote type=3D=22cite=22><br /> Hi,<br /> <br /> you can use custom access log format and log parts amount. After that jus= t parse the log line and put into Elastic.<br /> <br /> Regards, Alexander Malysh<br /> Am 24. Sept. 2024, 11:38 +0200 schrieb =D0=94=D0=B5=D0=BD=D0=B8=D1=81 =D0= =94=D0=B0=D0=B2=D1=8B=D0=B4=D0=BE=D0=B2 <dynax60=40gmail.com>:<br /= > <br /> Hi all,<br /> <br /> Along with the message, it is necessary to register in the access=5Flog t= he total number of its parts (it doesn't matter, it's MO or MT), since ea= ch part of such a composite message is charged by the upstream SMSC opera= tor. I will collect such information in Elasticsearch for subsequent anal= ysis after the billing period.<br /> <br /> How do you solve this problem=3F If I am not mistaken, MO messages coming= from the SMS service will always have a =22=5Budh:0:=5D=22 entry in the = log file, since, apparently, Kannel deletes information in the SMS.udhdat= a format after assembling the message.<br /> <br /> --<br /> Regards,<br /> Denis<br /></blockquote> </blockquote> </div> </body> </html> --67175dca_66334873_d041--