CODEWITHSUNDEEP
ibm-cloudlogdna
lene
lene

Reputation: 11

Region issue for IBM Cloud Activity Tracker with LogDNA

We have different resource group A resource in Tokyo B resource in Tokyo too

we need create one IBM Cloud Activity Tracker with LogDNA for A resource and another one IBM Cloud Activity Tracker with LogDNA for B resource

Can i put IBM Cloud Activity Tracker for A resource in Tokyo and IBM Cloud Activity Tracker for A resource in Dallas？

Because in your guide https://cloud.ibm.com/docs/Activity-Tracker-with-LogDNA?topic=Activity-Tracker-with-LogDNA-launch there is important notice "There is 1 instance per region."

Could you help to confirm this case?

Upvotes: 0

Views: 110

Answers (2)

Vidyasagar Machupalli
Vidyasagar Machupalli

Reputation: 2865

You need to effectively name your environments and work with Event fields and Event types

A basic convention could use a pattern of “department_instance_level.” Instead of “Error Logs” and “Info Logs,” they would be named “dev_app1_info,” “qa_app2_error,” and so on. Not only does this clearly define the contents of each view, but since LogDNA sorts views alphabetically, each view is naturally grouped with similar views. This makes it easy to scan for specific views and search for those containing specific keywords. In this screenshot, searching for “prod” narrows the list to views containing production environment logs.

Check How to use LogDNA Views to Manage Logs Effectively guide to learn the best way to manage your events

Additionally, you are planning to setup multiple environments, check this guide around How to Set Up Multiple Environments in LogDNA

Upvotes: 0

data_henrik
data_henrik

Reputation: 17156

Events are logged in the region where they are generated. Also note that all global events are sent to LogDNA in Frankfurt (Europe).

When working with the logged events, you can distinguish between the services based on the records and their data fields. You could create custom views to separate those events.

Upvotes: 1

Related Questions