Re: Logging the total number of fragments that make up a message

Alexander Malysh <[email protected]> Wed, 9 Oct 2024 09:50:11 +0200
Newsgroups gmane.comp.mobile.kannel.user
Message-ID <d9e304f6-3477-4d5d-a8b5-8ecc8d46fd8a@Spark>
--670635b9_19495cff_433b
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

you can use custom access log format and log parts amount. After that jus=
t 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=5Flog=
 the total number of its parts (it doesn't matter,=C2=A0it's MO or MT), s=
ince each part of such a composite message is charged by the upstream SMS=
C operator.=C2=A0I will collect such information in Elasticsearch for sub=
sequent analysis after the billing period.
>
> How do you solve this problem=3F If I am not mistaken, MO messages comi=
ng from the SMS service will always have a =22=5Budh:0:=5D=22 entry in th=
e log file, since, apparently, Kannel deletes information in the SMS.udhd=
ata format after assembling the message.
>
> --
> Regards,
> Denis

--670635b9_19495cff_433b
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 />
you can use custom access log format and log parts amount. After that jus=
t parse the log line and put into Elastic.</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 24. Sept. 2024, 11:38 +0200 schr=
ieb =D0=94=D0=B5=D0=BD=D0=B8=D1=81 =D0=94=D0=B0=D0=B2=D1=8B=D0=B4=D0=BE=D0=
=B2 &lt;dynax60=40gmail.com&gt;:<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>
<div dir=3D=22ltr=22>Hi all,
<div><br /></div>
<div>Along with the message, it is necessary to register in the access=5F=
log the total number of its parts (it doesn't matter,&=23160;it's MO or M=
T), since each part of such a composite message is charged by the upstrea=
m SMSC operator.&=23160;I will collect such information in Elasticsearch =
for subsequent analysis 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.
<div><br clear=3D=22all=22 />
<div>
<div dir=3D=22ltr=22 class=3D=22gmail=5Fsignature=22 data-smartmail=3D=22=
gmail=5Fsignature=22>--<br />
Regards,<br />
Denis</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</body>
</html>

--670635b9_19495cff_433b--