Help Center > > FAQs> Usage FAQs> What Can I Do If Log or Threshold Alarm Data Cannot Be Retrieved Normally?

What Can I Do If Log or Threshold Alarm Data Cannot Be Retrieved Normally?

Updated at: Nov 25, 2019 GMT+08:00

When log or threshold alarm data cannot be retrieved normally, the possible causes are as follows.

Kafka Queue Is Incorrectly Deleted

A Kafka queue is a container that stores messages during transmission. It receives messages and stores them as files in order. Messages in a queue can then be retrieved by users. If you incorrectly delete a Kafka queue, data cannot be retrieved normally. To solve the problem, perform the following operations:

  1. On the subscription page of Application Operations Management (AOM), check whether the Kafka queue has been deleted. In the following example, the Kafka queue has been deleted.

  2. On the Queue Manager page of Distributed Message Service (DMS), check whether the Kafka queue has been deleted.

  3. If the Kafka queue has been deleted, select another Kafka queue or create a queue according to Creating a Queue, and then subscribe to logs or threshold alarms again according to Subscribing to Logs or Subscribing to Threshold Alarms.

Kafka Queue Is Unauthorized

During subscription configuration, AOM automatically grants the ProduceMessages (producing messages to the queue) permission to the op_svc_apm user. If you incorrectly modify or delete the permission, data cannot be retrieved normally. To solve the problem, perform the following operations:

  1. On the subscription page of AOM, check the permissions of the Kafka queue. In the following example, the Kafka queue is unauthorized.

  2. In the DMS console, check the policies of the Kafka queue and grant the ProduceMessages permission to the op_svc_apm user.

    1. On the Queue Manager page of DMS, click the Kafka queue name and click the Policy Management tab to check the policies of the Kafka queue.
    2. Grant the ProduceMessages permission to the op_svc_apm user. There are two scenarios:
      • Unauthorized

        If none of the policies grant the op_svc_apm user (or all users) the ProduceMessages permission, data cannot be retrieved normally, as shown in the following figure. To solve the problem, click , subscribe logs or threshold alarms again by using the queue, and click OK. AOM then automatically authorizes the queue.

      • Authorization denied

        Deny permissions take precedence over Allow permissions. If both Deny and Allow permissions coexist, Deny permissions prevail while Allow permissions become invalid. If at least one of the policies denies the ProduceMessages permission of the op_svc_apm user (or all users), data cannot be retrieved normally, as shown in the following figure. You can handle the problem using either of the following solutions:

        Solution 1: Delete such policies. Then, on the subscription page of AOM, click , subscribe logs or threshold alarms again by using the queue, and click OK. AOM then automatically authorizes the queue.

        Solution 2: Modify the permissions of such policies. Then, on the subscription page of AOM, click , subscribe logs or threshold alarms again by using the queue, and click OK. AOM then automatically authorizes the queue.

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel