This counter tracks the number of bytes successfully placed into this egress CoS queue (cienaCesPmQueueGroupQueueIndex) for transmission, as stated in the MIB description. As the accepted-into-queue side of the pair with the matching DroppedBytes counter, its growth rate for this queue over the History window tells an admin how much of a given class-of-service's offered load the scheduler is actually able to service, which is the baseline needed to judge whether a rising drop counter on the same queue reflects real oversubscription or just normal growth. For example, 2,453,328 bytes enqueued into this queue in this history bin, compared against that same queue's DroppedBytes counter, tells the admin what fraction of this CoS queue's offered traffic is actually getting serviced versus discarded.