• State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 59 subscribers
  • Views 5040 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Foglight traces in SQL error log- how do you stop these?

chubbsm
over 6 years ago

 I tried setting the Deadlock collection for every 60 minutes but still showing as every 15 minutes. What process/collection controls this? Can it be modified Enterprise wide, not every agent?

Parents
  • 0 over 6 years ago
    Hi Chubbsm,

    I recommend that you open a Service Request with our Support team for this. There have been some changes to the trace collection in recent cartridges and it is difficult to provide general suggestions when the specific environment information (including the cartridge version) isn't available.

    We recently encountered an issue similar to what you described where it was determined that another process (external to Foglight) was killing the trace every fifteen minutes and a new trace was being opened using the same trace id.

    Another potential cause we have seen is when two different SQL Server agents monitor the same database instance.

    The script to update all of the agents is not included in the KB article because of the broader change that it makes to all database agents. A Support Engineer assigned to the Service Request can also provide the script for updating all of the agents.

    John
Reply
  • 0 over 6 years ago
    Hi Chubbsm,

    I recommend that you open a Service Request with our Support team for this. There have been some changes to the trace collection in recent cartridges and it is difficult to provide general suggestions when the specific environment information (including the cartridge version) isn't available.

    We recently encountered an issue similar to what you described where it was determined that another process (external to Foglight) was killing the trace every fifteen minutes and a new trace was being opened using the same trace id.

    Another potential cause we have seen is when two different SQL Server agents monitor the same database instance.

    The script to update all of the agents is not included in the KB article because of the broader change that it makes to all database agents. A Support Engineer assigned to the Service Request can also provide the script for updating all of the agents.

    John
Children
No Data