Description of problem:

Loki Alerting rule is not firing when dataModel is Otel. (More details in comments after retest on this issue)

When working with viaQ, the AlertingRule fires as expected.

$ oc extract cm/lokistack-dev-rules-0
my-app-my-app-alert-9ad1db80-57b2-4d9e-b76b-2ecf4626323e.yaml

$ cat my-app-my-app-alert-9ad1db80-57b2-4d9e-b76b-2ecf4626323e.yaml 
groups:
- name: MyApplication
  interval: 1m
  limit: 0
  rules:
  - alert: MyAppLogVolumeIsHigh
    expr: |
      count_over_time({kubernetes_namespace_name="my-app"}[2m]) > 0
    for: 5m
    annotations:
      description: My app has high amount of logs.
      summary: project "my-app" log volume is high.
    labels:
      kubernetes_namespace_name: my-app
      namespace: my-app
      project: my-app
      severity: info
      tenantId: application

Version-Release number of selected component (if applicable):

Logging 6.1

How reproducible: Always

Steps to Reproduce:

1. Deploy LO and CLO v6.1
2. Forward logs to lokiStack with dataModel as Otel.
3. Create AlertingRule for an application project.

Actual results: 

AlertingRule does not fire when dataModel is OTEL.

Expected results:

AlertingRule Should fire when dataModel is Otel as it fires for ViaQ.

Additional info:

Ruler logs, Console UI, AM Query logs are attached.

Firing Alert with viaQ is attached.