457 results found

1. Managing mongoDB containers having multiple DNS names through automation agent

   We got mongoDB running on openshift pods across 2 separate openshift clusters and it runs perfectly fine but we are now facing issue with doing mongoDB restore, and that has led to us now wanting to use automation agent to control the mongod process on the containers.

   The major challenge we are facing is that we run into issues when automation agent runs rs.initiate() and as part of the process tries to gather the hostname of the pod by running hostname -f command. The trouble is we have to deal with separate openshift clusters and have got mongod replica set members split across separate openshift clusters so we use a global DNS name so that the hostnames are resolved at the DNS level and allows for communication to flow through across seperate openshift clusters.

   We want to have a feature which would allow us to choose what hostnames the automation agent should use in order to create the replica set. We also feel, this would be a huge asset for anyone trying to control the mongod containers from the ops manager and would give mongoDB an edge when it comes to running databases on containers.

   We are also happy to provide any assistance in this regard and want this feature to be considered on a high priority as it is a BLOCKER for us.

   We got mongoDB running on openshift pods across 2 separate openshift clusters and it runs perfectly fine but we are now facing issue with doing mongoDB restore, and that has led to us now wanting to use automation agent to control the mongod process on the containers.

   The major challenge we are facing is that we run into issues when automation agent runs rs.initiate() and as part of the process tries to gather the hostname of the pod by running hostname -f command. The trouble is we have to deal with separate openshift clusters and have got mongod replica set… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ops Manager  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Operator automatically provision an Ops Manager programmatic API key

   Operator automatically provision an Ops Manager programmatic API key, The current instructions require human intervention to create an AP

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   under review  ·  0 comments  ·  Enterprise Kubernetes Operator  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Clear default values for New Replica Set and Cluster Component names in UI

   Clear default values for New Replica Set and Cluster Component names in UI

   Replica Set and Cluster Component names cannot be changed after deployment.
   The names are often overlooked while deploying and the defaults accepted configuring the names.
   If the fields were blank but mandatory (maybe with examples below the field) customers would be forced to choose logical names for their deployments.

   | Field | Current Default Value|
   | - | - |
   |Replica Set Id | myReplicaSet |
   | - | - |
   |Cluster Name | myCluster |
   |Shard Name Prefix | myShard |
   |Config Server Replica Set Name | configRS |

   Clear default values for New Replica Set and Cluster Component names in UI

   Replica Set and Cluster Component names cannot be changed after deployment.
   The names are often overlooked while deploying and the defaults accepted configuring the names.
   If the fields were blank but mandatory (maybe with examples below the field) customers would be forced to choose logical names for their deployments.

   | Field | Current Default Value|
   | - | - |
   |Replica Set Id | myReplicaSet |
   | - | - |
   |Cluster Name | myCluster |
   |Shard Name Prefix | myShard |
   |Config Server Replica Set Name… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ops Manager  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Abiity to configure Global Deployment Alerts in Cloud Manager similar to Ops Manager

   What is the problem that needs to be solved? Ability to set alerts at a global level for all projects, similar to functionality currently in Ops Manager

   Why is it a problem? (the pain) There is a basic set of alerting for all clusters that we use; instead of setting up each project with the same alerts, have a global alert level that covers all projects. Ops Manager currently has this functionality

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Cloud Manager  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Ability to define a custom CA PEM file for Webhook configuration on Ops Manager

   Currently, Ops Manager user may require to add the CA for the TLS enabled Webhook Endpoint directly to the Java Trust Store. Adding CA to Java Trust Store also requires to re-apply if Ops Manager Application is upgraded or re-install.

   It would be best to have a feature in Ops Manager so that the user is able to upload the required CA via UI.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ops Manager  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Allow using other port than 8080 (or 8443) when deploy Ops Manager

   The default port is 8080 or 8443 (for https) and cannot be changed

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   under review  ·  0 comments  ·  Enterprise Kubernetes Operator  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Data Size on the header of Overview/Real Time/Metrics/Data/Profiler/Performance Advisor pages

   Data Size on the header of Overview/Real Time/Metrics/Data/Profiler/Performance Advisor pages appears to be incorrect.

   Reasearch indicates that the "Data Size" next to "Status" on the Overview/Real Time/Metrics/Data/Profiler/Performance Advisor pages possibly does not include "local" DB and may have an incorrect divisor.
   It also shows the same possibly incorrect value on each Deployment in the "Processes" page.

   We, DBAs, and our application teams, who have access to the Ops Manager, have been relying on this metric info each time we needed to find the size of a user DB.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Ops Manager  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Feature to add the Certificate Authority file to the Ops Manager Java Trust Store via UI

   Currently, Ops Manager user may require to add the CA for the TLS enabled destination such as SMTP Server, on-prem S3, Webhook Endpoint, etc directly to the Java Trust Store. Adding CA to Java Trust Store also requires to re-apply if Ops Manager Application is upgraded or re-install.

   It would be best to have a feature in Ops Manager so that the user is able to upload the required CA via UI.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Ops Manager  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. Support for Connecting Cloud Manager to MongoDB Docker Containers

   I am not able to find a way to connect cloud manager to on prem docker containers running MongoDB. Maybe i've missed something and this feature already exists?

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Cloud Manager  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Support for cPanel

    Cpanel doesn't have any support for Mongodb

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Use word, not letter to define log levels in Ops Manager

    The following log messages are "info" level messages which can be found in the kubernetes logs from the ops-manager-db pods:

    {"logType":"mongodb","contents":"2020-12-16T02:42:28.557+0000 I  WRITE    [conn7329] update monitoringstatus.config.agentSessions command: { q: { _id: \"mongodb-rs-1.mongodb-rs-svc.mongodb.svc.cluster.local-48cc126fc451d9fa2ffa7569363971f2-5fbedc8dc354771c77dd1932\", s: \"KHNA9JiqXcos5V0d\" }, u: { $set: { s: \"PRIMARY\", p: true } }, multi: false, upsert: false } planSummary: IXSCAN { _id: 1 } numYields:0 queryHash:6C451E2F planCacheKey:38AD5486 ok:0 errMsg:\"E11000 duplicate key error collection: monitoringstatus.config.agentSessions index: cid_1_s_1 dup key: { cid: ObjectId('5fbedc8dc354771c77dd1932'), s: \\\"PRIMARY\\\" }\" errName:DuplicateKey errCode:11000 locks:{ ParallelBatchWriterMode: { acquireCount: { r: 1 } }, ReplicationStateTransition: { acquireCount: { w: 1 } }, Global: { acquireCount: { w: 1 } }, Database: { acquireCount: { w: 1 } }, Collection: { acquireCount: { w: 1 } }, Mutex: { acquireCount: { r: 1 } } } flowControl:{ acquireCount: 1 } storage:{} 200ms"}
    
    {"logType":"mongodb","contents":"2020-12-16T02:42:53.558+0000 I  WRITE    [conn129189] update backupagentstatus.backupAgentSessions command: { q: { groupId: ObjectId('5fbedc8dc354771c77dd1932'), tag: \"unassigned\", $or: [ { sessionKey: \"5fd130ec9621b221acd18451\" }, { heartbeat: { $lt: 1608086273347 } } ] }, u: { $set: { groupId: ObjectId('5fbedc8dc354771c77dd1932'), tag: \"unassigned\", sessionKey: \"5fd130ec9621b221acd18451\", heartbeat: 1608086573347, hostname: \"mongodb-rs-0.mongodb-rs-svc.mongodb.svc.cluster.local\", addr: \"10.200.30.0\" }, $inc: { callsSinceSuccess: 1 } }, multi: false, upsert: true } planSummary: IXSCAN { groupId: 1, tag: 1 } keysInserted:1 numYields:0 queryHash:5BA6C0B5 planCacheKey:AEFF88E2 ok:0 errMsg:\"E11000 duplicate key error collection: backupagentstatus.backupAgentSessions index: groupId_1_tag_1 dup key: { groupId: ObjectId('5fbedc8dc354771c77dd1932'), tag: \\\"unassigned\\\" }\" errName:DuplicateKey errCode:11000 locks:{ ParallelBatchWriterMode: { acquireCount: { r: 1 } }, ReplicationStateTransition: { acquireCount: { w: 1 } }, Global: { acquireCount: { w: 1 } }, Database: { acquireCount: { w: 1 } }, Collection: { acquireCount: { w: 1 } }, Mutex: { acquireCount: { r: 1 } } } flowControl:{ acquireCount: 1 } storage:{} 209ms"}
    

    Despite the fact that the word "error" is in these logs many times, and they have an error code, error name, and error message, this is considered an info level log.

    This is because the letter I is after the date. This makes using regex really hard when trying to setup alerts and monitoring, if I wanted to exclude info level logs.

    It would be great of instead of using a letter like I, W, or E, a word or abbreviation was used such as INFO, WARN or ERROR.

    The following log messages are "info" level messages which can be found in the kubernetes logs from the ops-manager-db pods:

    {"logType":"mongodb","contents":"2020-12-16T02:42:28.557+0000 I  WRITE    [conn7329] update monitoringstatus.config.agentSessions command: { q: { _id: \"mongodb-rs-1.mongodb-rs-svc.mongodb.svc.cluster.local-48cc126fc451d9fa2ffa7569363971f2-5fbedc8dc354771c77dd1932\", s: \"KHNA9JiqXcos5V0d\" }, u: { $set: { s: \"PRIMARY\", p: true } }, multi: false, upsert: false } planSummary: IXSCAN { _id: 1 } numYields:0 queryHash:6C451E2F planCacheKey:38AD5486 ok:0 errMsg:\"E11000 duplicate key error collection: monitoringstatus.config.agentSessions index: cid_1_s_1 dup key: { cid: ObjectId('5fbedc8dc354771c77dd1932'), s: \\\"PRIMARY\\\" }\" errName:DuplicateKey errCode:11000 locks:{ ParallelBatchWriterMode: { acquireCount: { r: 1 } }, ReplicationStateTransition: { acquireCount: { w: 1 } }, Global: { acquireCount: { w:

    … more
    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Rewrite Informational Message "E11000 duplicate key error collection"

    Rewrite the informational AppDB log message so that monitoring tools such as Dynatrace and Splunk does not consider this message as an error message.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. Add ability to merge metrics when host renamed

    If a host is renamed and a new mapping is made with a unique ID, there is no way to merge the metrics to view the, historically.

    Adding the ability to merge metrics from previous hosts (when the user is sure the hosts are equivalent) would allow history to be viewed and maintained.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Ability to control Ops Manager log rotation from an Admin Page in the UI

    The Ops Manager Application Server Log Directory is typically located in /opt/mongodb/mms/logs/.

    Currently, the log rotation of the Ops Manager log files /opt/mongodb/mms/logs/mms0.log, /opt/mongodb/mms/logs/daemon.log and /opt/mongodb/mms/logs/mms0-access.log are configured by default to rotate the log file every day and compress it with a retention of 30 days. After 30 days the compressed files are deleted.

    Please allow the configuration of these log rotation settings through the Ops Manager Web UI.

    Currently, this can only be done manually. The default installation of Ops Manager includes a file in /opt/mongodb/mms/conf called logback.xml. This is the file that the library uses to configure Ops Manager logs and log rotation for /opt/mongodb/mms/logs/mms0.log and /opt/mongodb/mms/logs/daemon.log. By default this is configured with the following settings:

    
<appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
<file>${log_path}.log</file>
<encoder class="com.xgen.svc.mms.util.HeaderPatternLayoutEncoder$Classic">
<pattern>
%d{"yyyy-MM-dd'T'HH:mm:ss.SSSZ"} [%thread] %XF{groupId, "gid:%s "}%XF{jobId, "jobId:%s "}%-5level %logger [%file.%method:%line] - %msg%n
</pattern>
</encoder>
<!-- Rollover the logs once per day, keep 30 days, compressed -->
<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
<fileNamePattern>${log_path}.%d{yyyyMMdd}.log.gz</fileNamePattern>
<maxHistory>30</maxHistory>
</rollingPolicy>
</appender>


    The file /opt/mongodb/mms/conf/logback-access.xml controls rotation of the /opt/mongodb/mms/logs/mms0-access.log. It has the same <!-- Rollover the logs once per day, keep 30 days, compressed --> policy.

    The logs will be compressed and rotated each day and deleted after 30 rolling days. If you modify the maxHistory option to 10, this should delete the files after 10 days. Please note that any upgrade of Ops Manager may overwrite this change with a new configuration file. Additionally, after modifying these values you will need to restart Ops Manager.

    The /opt/mongodb/mms/logs/mms-migration.log, mms0-startup.log and daemon-startup.log log files are not rotated as it contains only some log entries generated during the startup/migration phases of the Ops Manager Application Server processes.

    The Ops Manager Application Server Log Directory is typically located in /opt/mongodb/mms/logs/.

    Currently, the log rotation of the Ops Manager log files /opt/mongodb/mms/logs/mms0.log, /opt/mongodb/mms/logs/daemon.log and /opt/mongodb/mms/logs/mms0-access.log are configured by default to rotate the log file every day and compress it with a retention of 30 days. After 30 days the compressed files are deleted.

    Please allow the configuration of these log rotation settings through the Ops Manager Web UI.

    Currently, this can only be done manually. The default installation of Ops Manager includes a file in /opt/mongodb/mms/conf called logback.xml. This is the file that the library uses… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. bigpanda

    Prefer to get BigPanda integrated with OpsManager for event correlation .
    www.bigpanda.io

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Support ClusterAuthMode X509

    Customer is trying to deploy a RS with X509 internal auth. The missing RS parameter clusterAuthMode: X509 can be set via GUI but not via CLI.

    Customer would appreciate full support for this mode using the CLI.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  MongoDB CLI for Cloud Manager and Ops Manager  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Alerts if MMS Application goes down

    Dear Team,

    We are looking for an option to set alerts if any of the Ops Manager Application goes down in a HA environment. Being with HA configuration, we at least expect this feature to in place - as currently it looks like that OPS Manager is not aware of its own HA configuration.

    Mongo Case: 00723232

    Thanks,
    Tom

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Create a litmus chaos to test mongodb in containers

    To support chaos engineering.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. MongoCLI Wizard Flag

    Currently a user needs to manually insert at least all the required flags to use a mongocli command. We can implement the flag --wizard which guides the user through flags with interactive prompts.
    This flag should be added to all the commands to allow the user to get interactive prompts when required flags are not provided.

    The wizard flag will have the following functionalities:

    • Asking to the user the required flags with interactive prompts
    • Showing a list of optional flags and asking to insert their values if selected
    • In case of describe commands, showing the list of resources available (mongocli atlas cluster describe, list the available clusters)
    • Letting users select a specific value from a list of accepted values
    • If no required flags are given, mongocli will start the wizard mode

    GitHub PR: https://github.com/mongodb/mongocli/pull/511

    Currently a user needs to manually insert at least all the required flags to use a mongocli command. We can implement the flag --wizard which guides the user through flags with interactive prompts.
    This flag should be added to all the commands to allow the user to get interactive prompts when required flags are not provided.

    The wizard flag will have the following functionalities:

    • Asking to the user the required flags with interactive prompts
    • Showing a list of optional flags and asking to insert their values if selected
    • In case of describe commands, showing the list of resources available (mongocli… more

    •  

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. mongoimport should assume json with arrays

    When running something like "mongoimport --host Cluster0-shard-0/cluster0-shard-00-00-MY.mongodb.net:27017,cluster0-shard-00-01-MY.mongodb.net:27017,cluster0-shard-00-02-MY.mongodb.net:27017 --ssl --username MYUSER --password MYPASS --authenticationDatabase admin --db db --collection coll --type json --file D:\downloads\records.json". You get error "2019-09-28T15:40:34.076-0600 Failed: cannot decode array into a D". You have to use the "--jsonArray". Why wouldn't this be the default. Almost all JSON objects have arrays via mass import/export. Worse case, it should give a better error message.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close